Open
Conversation
Duslerke
approved these changes
Apr 7, 2026
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.
Link to JIRA ticket
SSI-866
Describe this PR
What is the problem we're trying to solve
Currently the MMH dev site is pointing to staging cautionary alerts API. MMH dev has been updated to use the new Cognito auth MFE, so the API calls are failing because the current staging authorizer can't handle the new Cognito tokens.
This is causing issues in e2e tests as well as for users trying to use the MMH dev site.
What changes have we introduced
Update the staging authorizer to the new one that supports Cognito tokens.
Checklist
Follow up actions after merging PR
N/A