RocketChat / RocketChat/Rocket.Chat
When using the account option "Manually Approve New Users" the registration workflow for local users and SSO users is not consistent
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
When using the account option "Manually Approve New Users" the registration workflow for local users and SSO users is not consistent. A locally registered user will be redirected to the registration success page and will be informed by e-mail about his registration. In contrast, a user who registers via an authentication service does not receive either an email or an information page.
Server Setup Information:
- Version of Rocket.Chat Server: 0.59.3
- Operating System: linux
- Deployment Method(snap/docker/tar/etc): etc
- Number of Running Instances: 2
- DB Replicaset Oplog: Enabled
- Node Version: 4.5.0 - x64
Steps to Reproduce:
- Enable "Manually Approve New Users"
- Enable "Registration with Authentication Services"
- Register with authentication services (--> no info about the required activation)
- Register a local user (--> info is displayed and email is sent)
Expected behavior:
For both scenarios (local and authentication service) the user should receive an E-Mail and should get a direct information on the login screen
Actual behavior:
- Register with authentication services --> no info about the required activation
- Register a local user --> info is displayed and email is sent
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
No files, tests, or entry points are identified in the issue. Start by reproducing both local and authentication-service registration flows with “Manually Approve New Users” enabled, then trace their differing post-registration behavior. Done means both flows show the activation information on the login screen and send the user an email.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100