Pull identity information from the AttributeResolver during registration
Completed
Description fields
Basics
Logistics
Basics
Logistics
Description
Currently the user.id (which is the userHandle in the response from an authenticator) is generated randomly for each new registration (although once per username which is taken from the subject context). This is stored against the registration and was a stopgap to get registrations working. This information should ideally come from the attribute resolver.
This applies similarly to the display name, which is not currently used.
Currently the user.id (which is the userHandle in the response from an authenticator) is generated randomly for each new registration (although once per username which is taken from the subject context). This is stored against the registration and was a stopgap to get registrations working. This information should ideally come from the attribute resolver.
This applies similarly to the display name, which is not currently used.