You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 #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:
The text was updated successfully, but these errors were encountered:
First you are using Mongo 4.4.5 and technically we do not support this at the minute. It probably isn't the cause but if you use unsupported versions we can't necessarily assist you.
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 #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:
Client Setup Information
Additional context
Relevant logs:
The text was updated successfully, but these errors were encountered: