RocketChat / RocketChat/Rocket.Chat
Ability to configure login URL for when Meteor/login token expires?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Hi, we're authenticating users via "SSO" with our platform. So we basically set the appropriate RC Meteor local storage when the user signs into the platform, and hence they are signed into RC without logging in. Using this solution, things work pretty seamlessly.
However, suppose a user leaves an RC tab open and their Meteor token expires. They are brought to the RC login UI to sign in again. Is there a way to customize this login URL so that they will be brought to the sign-in page for our platform instead, and then we'd redirect them back to the URL they came from? E.g. this would require us to be able to configure a "login redirect URL" such as https://blah.com/login?return-url=https://blah.com/chat.
Thanks!
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 tracing the Meteor token-expiry flow that sends users to the Rocket.Chat login UI and identify where the login URL is selected. Done means administrators can configure a platform sign-in URL that preserves the original destination and users are redirected there when their token expires.
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
- 25/100