Add support for OIDC authentication #104
Merged
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
harry-anderson
force-pushed
the
oidc
branch
2 times, most recently
from
dc97b21 to
ec10b5f
Compare
harry-anderson
force-pushed
the
oidc
branch
2 times, most recently
from
f8b45b0 to
4a179cb
Compare
jkongie
reviewed
Jun 11, 2025
jkongie
reviewed
Jun 11, 2025
jkongie
reviewed
Jun 11, 2025
|
Thanks for the review @jkongie I have made the following changes based on your suggestions:
|
|
jmank88
approved these changes
Jun 30, 2025
eutopian
approved these changes
Jun 30, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 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
Add support for OIDC based authentication, log user in on successful redirect from OIDC provider.
This is the front end changes for smartcontractkit/chainlink#14406
This PR adds logic to the SignIn page to detect for query params 'code' and 'state' if these params are found, the front end application call the backend to exchange to code for a valid user session. If successful, sign the user in.
Steps to Test
yarn && yarn setupyarn startChecklist
If this PR creates changes to the operator-ui itself, rather than tests, pipeline changes, etc. Then please create a changeset so that a new release is created, and the changelog is updated. See: https://github.com/changesets/changesets/blob/main/docs/adding-a-changeset.md#what-is-a-changeset