-
Notifications
You must be signed in to change notification settings - Fork 10k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CAS 2.0 Support #4497
CAS 2.0 Support #4497
Conversation
Custom attributes not working!.
Any guess how to fix..? |
Hey there, Only the following internal attributes are beeing sourced from external attributes:
You have however tried sourcing "mail" instead of "email" - try the following syntax: Keep in mind that CAS attributes do only work with a CAS 2.0 enabled server. |
@CoreCache |
You are welcome, just please be cautios about your conclusions next time, Thanks! :)
|
@RocketChat/core
Closes #2325 #2326 #2963
CAS 2.0 Support
The CAS 2.0 protocol allows that the CAS SSO server transmits user attributes towards a CAS client, the RocketChat instance. RocketChat user attributes such as name, email and rooms (to join on default) can be sourced/generated from the external attributes. This is done by defining a JSON attribute map where the values may container external attribute placeholders which will be interpolated and assigned to internal user attributes.
Adds the following Settings to the CAS configuration:
Always sync User data
Always synchronize external CAS User data into available attributes upon login. Note: Attributes are always synced upon account creation anyway.)
Attribute map
Use this JSON input to build internal attributes (key) from external attributes (value). External attribute names enclosed with '%' will interpolated in value strings.
Example,
{"email":"%email%", "name":"%firstname%, %lastname%"}
The attribute map is always interpolated. In CAS 1.0 only the
username
attribute is available. Available internal attributes are: username, name, email, rooms; rooms is a comma separated list of rooms to join upon user creation e.g: {"rooms": "%team%,%department%"} would join CAS users on creation to their team and department channel.