Fix SSO ID issue with certain admin accounts - #4580
Merged
Merged
Conversation
If you added an admin attendee to an existing account, the system would fail to tie their admin account to their existing SSO ID, meaning there was no way for them to activate their admin account. We now make sure to copy the SSO ID from the existing account to an admin account, unless that account already has one.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
If you added an admin attendee to an existing account, the system would fail to tie their admin account to their existing SSO ID, meaning there was no way for them to activate their admin account. We now make sure to copy the SSO ID from the existing account to an admin account, unless that account already has one. We also now display the SSO ID for admin and attendee accounts, which would have made debugging this issue easier.