RocketChat / RocketChat/Rocket.Chat
First time login hang using OAuth SSO Provider
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
Logging in for the first time as SSO user causes a hang with just the 3 dot animation until webpage refresh where the page will load correctly each time after.
Very similar behavior to what was described here: https://github.com/RocketChat/Rocket.Chat/issues/18652
Steps to reproduce:
Azure SSO configured with OAuth2.
First time login with SSO user.
Expected behavior:
First time login to be a success.
Actual behavior:
Server Setup Information:
- Version of Rocket.Chat Server: 5.2.0
- Operating System: Ubuntu 20.04
- Deployment Method: Manual Installation
- Number of Running Instances: 1
- DB Replicaset Oplog: Not sure what this is
- NodeJS Version: 14.18.3
- MongoDB Version: 5.0.13
Client Setup Information
- Desktop App or Browser Version: Chrome 106.0.5249.119
- Operating System: Windows 11
Additional context
Relevant logs:
Only error in the server is:
{"level":50,"time":"2022-10-17T19:27:31.958Z","pid":9726,"hostname":"Rocket","name":"System","msg":"Exception while invoking method autoTranslate.getSupportedLanguages 'Auto-Translate is disabled [error-autotranslate-disabled]'"}
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
Start by reproducing the first-time Azure OAuth2 SSO login on Rocket.Chat 5.2.0, then trace the login flow using the reported browser behavior and server logs. Done means a new SSO user reaches the application without the three-dot hang or requiring a page refresh.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, typescript
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100