Upcoming Change to Greenway Authorization Server ID Token sub Claim
As part of our preparations for the upcoming SMART 2.0 enhancements, we are implementing an update to the ID token structure that may impact how user identifiers are handled in your application.
If you are using a sub claim of the id_token, we recently discovered an issue in the ID token where the sub (subject) claim was mapped to the user's email address instead of the UUID. As a temporary workaround until the sub claim is properly mapped, if you require the user’s unique identifier, please use the UUID claim instead of the sub claim. Once the fix is applied, you can switch back to the sub claim if desired.
Action Required:
- If you are not using sub claim of the id_token, no action is required.
- Any application's codebase using the sub claim of the id_token needs to do the following actions:
- If you are using sub claim as the user’s unique identifier:
- Switch to using UUID claim immediately for that purpose.
- Update any data or applications referencing the current sub claim (email address) to use UUID instead.
- If you are using sub claim for the user’s email address:
- Switch to using email claim immediately for that purpose.
- If you are using sub claim as the user’s unique identifier:
Updated about 10 hours ago