Open
Conversation
github-actions
bot
added
FY26 Sprint 19
ChengShi-1
moved this from Ready for Review ⏩
to In Progress 💻
in IQSS Dataverse Project
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.
What this PR does / why we need it:
Like the description in the issue, to avoid confusion of users when they sign in, we need to add a note/alert on the Harvard SPA login page to clarify that some of the available login options are not supported.
Which issue(s) this PR closes:
Special notes for your reviewer:
the note may should be refined to better clarify the sign in situation, open to any suggestion
Suggestions on how to test this:
See how to build keycloak in this doc
Then, go to spa => sign in, the note and styled log in page should be shown
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
Is there a release notes or changelog update needed for this change?:
Additional documentation: