RocketChat / RocketChat/Rocket.Chat
CAS Single Logout integration
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
CAS has a functionality for SSO (Single Sign Out) that currently does not support Rocket Chat.
When you leave the CAS session, it sends a post to all services related to that user with the corresponding service ticket so that the application can close the session related to the ticket.
Server Setup Information:
Rocket.Chat Version: 0.58.2
NodeJS Version: 4.8.4 - x64
Platform: linux
Process Port: 3000
ReplicaSet OpLog: Disabled
Commit Hash: 988103d449
Commit Branch: HEAD
Expected behavior:
Rocket Chat have to handle the post from CAS and destroy the user session asociated to the service ticket received.
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 locating Rocket.Chat's existing CAS SSO integration and session-handling entry points. Review how CAS sends the service ticket and how Rocket.Chat associates tickets with sessions. Done means a CAS single-logout request can identify and destroy the corresponding user session, with verification for the expected request flow.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100