We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
AAF sign in leaves the Last Name field empty. It maps the User's title and full name onto the "First Name" field in the xnat local account.
e.g. XNAT AAF user details becomes
Last Name being a required field, leads to unexpected behaviour in a number of forms, especially user admin pages.
The text was updated successfully, but these errors were encountered:
Looks this can be resolved with property settings in $XNAT_HOME/config/auth/openid-provider.properties
The sample AAF properties file currently has: openid.aaf.familyNameProperty=deliberately_unknown_property openid.aaf.givenNameProperty=name
Given and family names are correctly set after changing these to: openid.aaf.familyNameProperty=family_name openid.aaf.givenNameProperty=given_name
If no concerns, the sample AAF properties file could be updated to match..
Sorry, something went wrong.
No branches or pull requests
AAF sign in leaves the Last Name field empty.
It maps the User's title and full name onto the "First Name" field in the xnat local account.
e.g. XNAT AAF user details becomes
Last Name being a required field, leads to unexpected behaviour in a number of forms, especially user admin pages.
The text was updated successfully, but these errors were encountered: