[IMPROVE] SAML login process refactoring#12891
[IMPROVE] SAML login process refactoring#12891sampaiodiego merged 157 commits intoRocketChat:developfrom kukkjanos:develop
Conversation
- the eppn is primary identifier match parameter (if not exist then email is a secondary) - update eppn to user profile - support the eduPersonPrincipalName (eppn) usually required saml parameter - support the displayName optional saml parameter - support two new saml settings - overwrite user fullname if need (use idp attribute [cn,username or displayName]) - overwrite user mail address if need (use idp attribute)
- the eppn is primary identifier match parameter (if not exist then email is a secondary) - update eppn to user profile - support the eduPersonPrincipalName (eppn) usually required saml parameter - support the displayName optional saml parameter - support two new saml settings - overwrite user fullname if need (use idp attribute [cn,username or displayName]) - overwrite user mail address if need (use idp attribute)
|
+1 |
|
This is a very useful feature, strongly recommended. |
|
+1 |
1 similar comment
|
+1 |
rukverc
left a comment
There was a problem hiding this comment.
Contains necessary changes, seems legit code.
|
a) This change destroy SAML with Microsoft ADFS. The login works, but the user maps always to the User Rocket.Cat. May 29 16:43:40 x06-rocketchat rocketchat[17255]: { actionName: 'authorize', |
|
Does it need a different authnContext value to work? What value would that be? |
|
request += '<samlp:RequestedAuthnContext xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol" Comparison="exact">' + '<saml:AuthnContextClassRef xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion">urn:federation:authentication:windows</saml:AuthnContextClassRef></samlp:RequestedAuthnContext>\n' + '</samlp:AuthnRequest>'; |
This change also breaks SAML with OneLogin IdP; same symptoms as reported here, but OneLogin does support the hard-coded authnContext of |
|
You mean login working but with the wrong user? That was fixed by #14686 and included on the 1.1.1 hotfix release. |
Confirmed fixed. Thanks! |
|
The problem #14686 is fixed, THX. For AuthContext, I would suggest that you make an array to specify multiple AuthContext. This way you can support multiple variants. |
FIX NEW DIRECTORY
Closes #ISSUE_NUMBER