-
Notifications
You must be signed in to change notification settings - Fork 556
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[v10] Propagate signup errors from rules to lock widget #580
Comments
Can you provide any more details like what error you see? how the rule returns the error or is it the a custom db script? |
It's a rule returning an error using the callback. It worked great on v9. The error message displayed in the lock dialog. What other details would be helpful? On Aug 24, 2016, 11:37 AM -0600, Hernan Zalazar notifications@github.com, wrote:
|
Having the same problem. I throw a Both the |
Closing this one. It works for rules if the error is Errors raised in the custom db scripts, in this case signup, are not handled yet by Lock but it's in our backlog. |
I throw an UnauthorizedError, and it gets displayed, but only in popup mode, not in redirect mode. |
@hzalaz Did you see this latest comment? Sounds like it should be reopened. |
Yes, but is more related to #639 since for redirect lock is not displayed when you are redirected back to your site, Lock does not store any auth result by itself, so you have to either show an error page of your choosing or open Lock with a flash message. |
Lock Version: v10.0
See https://auth0.com/forum/t/propagate-signup-errors-from-rules-to-lock-widget-v10/3108
The text was updated successfully, but these errors were encountered: