Update auth to use LifeScience AAI instead of Elixir AAI #643
Conversation
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
This is because of Elixir AAI has been migrated to LifeScience AAI, a corresponding update to the database has been made in our production system already: UPDATE users.users SET identity=substring(identity, 1, 40) || '@lifescience-ri.eu' WHERE identity_type='elixir;
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.
Describe the pull request:
Pull request long description:
Elixir AAI has been migrated to LifeScience AAI, so we need to update some endpoints in the code.
Changes made:
Updated variables that specify the URLs to the AAI
Related issues:
Additional information:
The database need to be updated as well, the following SQL statement should do the trick:
Release note:
Update auth to use LifeScience AAI instead of Elixir AAI.