Include ICAT user's investigation and instrument IDs in JWT access token#137
Open
Include ICAT user's investigation and instrument IDs in JWT access token#137
Conversation
1 task
Member
louise-davies
left a comment
louise-davies
left a comment
There was a problem hiding this comment.
I believe that it's working okay with SciGateway - even with autoLogin mode (aka an anon authenticator set up) the behaviour seems to not have changed due to the change in error codes in some circumstances (tested both the 401 errors and 500)
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
2 participants
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.
Description
Updates the app so that it queries ICAT for the user’s Investigations (as an InvestigationUser) AND Instruments (as an InstrumentScientist). It also updates the JWT access token payload so that these, which are need by the Search API component, are included.
Testing Instructions
Agile Board Tracking
closes #136