Skip to content

feat: CORE-6770 Add support OAuth2 to Gateway#184

Open
okapusty-virtru wants to merge 21 commits intomainfrom
oauth2
Open

feat: CORE-6770 Add support OAuth2 to Gateway#184
okapusty-virtru wants to merge 21 commits intomainfrom
oauth2

Conversation

@okapusty-virtru
Copy link

Proposed Changes

*Add OAuth2 secrets and CronJob for token refresh

Checklist

  • I have bumped the necessary versions
  • I have (re-)packaged the updated charts helm package $CHART_NAME -u
  • I have updated the repo index helm repo index .
  • I have added or updated documentation / readme (if appropriate)
  • I have verified that my changes have not introduced new lint errors

Testing Instructions

@okapusty-virtru okapusty-virtru changed the title feat(gateway): BACK-2190 Add support OAuth2 to Gateway feat: BACK-2190 Add support OAuth2 to Gateway Feb 28, 2025
Copy link
Contributor

@mkleene mkleene left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is great! Awesome that this is working. The only big change that I think we should make is that these objects should only appear if they have enabled oauth2, say by setting a value like oauth2.enabled. Otherwise we don't want the secret, the rolebinding, or the token refresher to even exist. That should be pretty simple using conditional templates.

Copy link
Contributor

@mkleene mkleene left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks really good! Just a couple of minor things. Maybe even call the files xoauth2-*?

mkleene
mkleene previously approved these changes Mar 28, 2025
Copy link
Contributor

@mkleene mkleene left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We just need to add what you have done here to the other modes

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good but I think that we need to slap these on all of the other workloads

xoauth2:
clientSecret: <xoauth2-client-secret>
refreshToken: <xoauth2-refresh-token>
accessToken: <xoauth2-access-token
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
accessToken: <xoauth2-access-token
accessToken: <xoauth2-access-token>

oauth2:
xoauth2:
enabled: false
clientId: <xoauth2-client-id>
Copy link
Contributor

@mkleene mkleene Mar 28, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
clientId: <xoauth2-client-id>
clientId: <xoauth2-client-id>
domains: <the domains that xoauth2 is configured for>
user: <the user that xoauth2 is configured for>

@okapusty-virtru okapusty-virtru requested a review from mkleene April 10, 2025 18:53
# Conflicts:
#	gateway/README.md
#	gateway/values.yaml
@okapusty-virtru okapusty-virtru changed the title feat: BACK-2190 Add support OAuth2 to Gateway feat: CORE-6770 Add support OAuth2 to Gateway Jul 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants