Closed sherakama closed 6 years ago
So does this only happen when the user's canonical SUNetID is different from their email address? That would 'splain a lot.
Also, if that's the case, I cannot test this. But I know someone who can...
No, this has to do with the response from the SAML request. In the response that I had previously used the key for the email address was email
but in the new set up it is simply mail
. The validation code was not able to do an accurate match as the key was missing. Having a different email from sunet shouldn't affect this but is worth testing to be sure.
OK, I'll have to look closer to see why it was getting a duplicate user error for the active $user
, not the user being added.
In order to have the 'auto register' functionality working we use hook_user_insert() which, on any user creation, checks to see if it needs to be a SAML user. This code was not able to identify that the current user was not the new user as the key in the SAML attributes array was different.
Code Climate has analyzed commit a2dac0f8 and detected 1 issue on this pull request.
Here's the issue category breakdown:
Category | Count |
---|---|
Bug Risk | 1 |
View more on Code Climate.
READY FOR REVIEW
Summary
Needed By (Date)
Urgency
Steps to Test
Associated Issues and/or People
See Also