RocketChat / RocketChat/Rocket.Chat
CAS button disappear on restart rocketchat.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
We use kubernetes solution to deploy rocketchat. When new pods start the CAS configuration not update ( cf screenshot ) . To find it again we must go to admin panel and update cas configuration ( For instance change text or size panel ).
we've find tihs issue https://github.com/RocketChat/Rocket.Chat/pull/17808 but our version is highter ( 3.10.3 ).
Before restart rocketchat:

After restart:

Steps to reproduce:
Configure CAs configuration
Make sure that work
Restart rocketchat instance.
Expected behavior:
CAS button must appear on login page.
Actual behavior:
CAS button not appear on login page.
Server Setup Information:
- Version of Rocket.Chat Server: 3.10.3
- Operating System:
- Deployment Method: kubernetes
- Number of Running Instances: 1 or many ( kubernetes autoscaling )
- DB Replicaset Oplog:
- NodeJS Version: v12.18.4
- MongoDB Version: 4.4.5
Client Setup Information
- Desktop App or Browser Version:
- Operating System:
Additional context
Relevant logs:
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 file or test is named. First reproduce the issue by configuring CAS, restarting the Rocket.Chat instance in Kubernetes, and checking whether the CAS settings persist and the button appears on the login page. Done means the CAS button remains available after a pod restart without manually updating the configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, mongodb, node.js
- Domain
- authentication, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100