mozilla-iam / mozilla-iam/auth0-deploy

Auth0 Rule - Move error reporting from SSO dashboard to NLX

Open
#186 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
6
Forks
21
Avg merge
17h 49m
Merged PRs (30d)
5

Description

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.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with rules/Global-Function-Declarations.js, especially the code linked for sending errors to the SSO dashboard, and rules/force-users-login-most-secure-method.js where an error is generated. Review mozilla-iam/auth0-custom-lock#99 for the NLX parameter and standard. Done means Auth0 rule errors are conveyed to NLX rather than sent to the SSO dashboard.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
authentication
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.