@dan.woda I’ve started implementing social login and have added a rule that just checks if the user exists in our DB. I’ve added logs and can see that the rule gets hit correctly - if a user is trying to sign up but they already exist it goes to the callback returning an error, but when that happens auth0 redirects to the callbackURL (with the error embedded in the url) instead of staying on the hosted page and displaying it. Do the rules not communicate back to the hosted pages if something goes wrong in them? For this rule in specific we want the errors to be displayed in the hosted pages, is there an extra step that’s missing in how we handle the errors?
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Link social provider during another login session | 2 | 3225 | December 18, 2019 | |
| Log Social Logins in Custom DB | 1 | 2081 | May 22, 2024 | |
| Social Connections on custom UI | 7 | 4099 | August 30, 2019 | |
| Custom social connections - Lock not available? | 2 | 3438 | December 25, 2018 | |
| Social Login with Multitenant | 2 | 5125 | January 21, 2019 |