MerginMaps / MerginMaps/mobile
No info is shifted to the user if the SSO login fails
Open
Nobody has claimed this yet.
auth
bug
ui/ux
- Dominant language
- C++
- Stars
- 388
- Forks
- 87
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 20
Description
If SSO authentication fails on provider side, no info is provided to the user with the reason why this happens. Only the SSO login dialog is still visible in the app with spinner. E.g. user try to login to closed account or the authentication fails due to invalid credentials
Steps:
- open app and sign in with SSO
- enter username, e.g. something098@example.com
- after sign in close the account
- sign it again with the same email something098@example.com
Actual results:
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure using the listed SSO steps, including signing in with an account that has been closed, and inspect the SSO login dialog and its spinner behavior. Done means provider-side authentication failures show the reason to the user and the dialog no longer remains stuck loading.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, cpp, ios
- Domain
- authentication, mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100