-
Notifications
You must be signed in to change notification settings - Fork 131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Integrate Keycloak in int and scr env #2609
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #2609 +/- ##
==========================================
+ Coverage 57.57% 57.62% +0.05%
==========================================
Files 92 91 -1
Lines 2786 2773 -13
Branches 711 656 -55
==========================================
- Hits 1604 1598 -6
- Misses 1066 1174 +108
+ Partials 116 1 -115
|
portal: 'https://ephem.outsrights.cc/', | ||
}, | ||
int: { | ||
url: ['console.int.openshiftusgov.com'], |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it not be better to allow these URLs to be configured when building the assets via env variables and avoid exposing URLs like these on GitHub?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bastilian we configure the SSOUrl for our environments in the frontend operator and the values are not public. However, the specific environment of this PR is not yet using the frontend operator. It's in the process of migration. The same applies to the qaprodauht. Until qaprodauth is discontinued and all envs are using the FEO, we need these values still.
@@ -134,7 +136,7 @@ export const doOffline = (key: string, val: string, configSsoUrl?: string) => { | |||
scopes.push(partnerScope); | |||
} | |||
|
|||
if (ssoScopes) { | |||
if (ssoScopes && !itLessKeycloakEnv) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a double-check. The offline token is not supposed to have all SSO scopes of the current session?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are no scopes in fedramp and this step is not needed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, there is just a small conflict due to the pf migrations.
Updates to use nav with chrome-service for itless
No description provided.