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
Currently, when an error message needs to be conveyed to the user due to an Auth0 rule, that message is sent in a jwt to the sso dashboard to be rendered.
It's confusing to the user to go to an RP, try to login and then be sent to a site that they weren't on before (sso dashboard) and potentially haven't gone to before to see an error message about another site (their RP or the NLX)
Solution
Instead of sending the error to SSO dashboard, send it to NLX. NLX will define a parameter and standard in mozilla-iam/auth0-custom-lock#99 through which to convey the error.
The text was updated successfully, but these errors were encountered:
Background
Currently, when an error message needs to be conveyed to the user due to an Auth0 rule, that message is sent in a jwt to the sso dashboard to be rendered.
Problem
The navigation flow of sending a user from NLX to the sso dashboard and having to use the back button to get back to the RP isn't ideal. This is currently tracked in SSO dashboard mozilla-iam/sso-dashboard#205 and mozilla/parsys#253 as "improve error page wayfinding"
It's confusing to the user to go to an RP, try to login and then be sent to a site that they weren't on before (sso dashboard) and potentially haven't gone to before to see an error message about another site (their RP or the NLX)
Solution
Instead of sending the error to SSO dashboard, send it to NLX. NLX will define a parameter and standard in mozilla-iam/auth0-custom-lock#99 through which to convey the error.
The text was updated successfully, but these errors were encountered: