You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fixing the theme to show correctly in the provider list was easy-ish, however when trying to authenticate with this provider, Lock tries to use a connection name of "oauth2" (i.e. the strategy name) instead of the name of the custom connection. The issue seems to be centered on A0SocialLoginViewController:118:
This seems inherently wrong because you're using the strategy name as a connection name when they should not depend at all on each other.
How should I handle this? It appears there would also be an issue with supporting multiple connections with the oauth2 strategy, as only one option would be presented to the user.
The text was updated successfully, but these errors were encountered:
I have configured a custom oauth2 connection as described in https://auth0.com/docs/connections/social/oauth2.
Fixing the theme to show correctly in the provider list was easy-ish, however when trying to authenticate with this provider, Lock tries to use a connection name of "oauth2" (i.e. the strategy name) instead of the name of the custom connection. The issue seems to be centered on A0SocialLoginViewController:118:
This seems inherently wrong because you're using the strategy name as a connection name when they should not depend at all on each other.
How should I handle this? It appears there would also be an issue with supporting multiple connections with the oauth2 strategy, as only one option would be presented to the user.
The text was updated successfully, but these errors were encountered: