-
Notifications
You must be signed in to change notification settings - Fork 8
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
Bug: if the uid contains a capital letter the eduID account "breaks" #671
Comments
Note that case should not matter when comparing uid's (see: https://www.rfc-editor.org/rfc/rfc4519.html#section-2.39) Folding uid's you receive to lowercase before you do any other processing with them is a good practice IMO. Note that uid's may contain unicode (according to the standard) when doing this. We may consider being more restrictive in the uid's we accept, e.g. ASCII only. |
Engineblock suggereert dat het probleem een kapotte subjectid is. Dit is de error die correspondeert met de EB-foutmelding (niet met het SAML-bericht):
|
Update: the affected account was deleted, and the user made a new one. For now the question remains open:
|
|
Via the Service desk a problem occurred. A user said he his "eduID was broken". But it actually is.
The reason the uid is of the form "iAchternaam". It also seems to happen if the uid looks like: "A". However, in the documentation there is no requirement that the uid has to be lowercase: https://servicedesk.surf.nl/wiki/display/IAM/Attributes+in+SURFconext#AttributesinSURFconext-uiduid
To reproduce:
Make an account on test. Then change in the database:
db.users.updateOne({email:"[email protected]"},{$set: {uid:’iAchternaam'}});
Get an error.
Logs:
SAML
The text was updated successfully, but these errors were encountered: