-
Notifications
You must be signed in to change notification settings - Fork 7.9k
hide scopes from scopes_supported in discovery endpoint #10409
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
hide scopes from scopes_supported in discovery endpoint #10409
Conversation
dabaff3 to
b5922c3
Compare
|
I have updated to latest main. |
|
The linting in the admin UI complains, please check the logs. I'm switching this PR to "draft" in the meantime. Please switch it back to "ready-for-review" when you want to have it reviewed again. Unfortunately the Admin UI tests are currently unstable, see #30492 - if those tests fail again, it might be worth waiting for that issue to be closed first and then rebase, or asking a maintainer to re-run the tests. |
b5922c3 to
840ef55
Compare
|
@cgeorgilakis: would you mind refreshing your PR, should you have the time to do so? If not, I'm willing to have a try, so that we can have hopefully have this feature added to Keycloak. |
Unfortunatelly no this period. Feel free to rebase it and proceed with PR. |
d1c2971 to
0002987
Compare
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.
Unreported flaky test detected, please review
Unreported flaky test detectedIf the flaky tests below are affected by the changes, please review and update the changes accordingly. Otherwise, a maintainer should report the flaky tests prior to merging the PR. org.keycloak.testsuite.federation.ldap.LDAPProvidersIntegrationTest#updateLDAPUsernameTest |
0b59579 to
307bd7e
Compare
@ahus1 @dalbani I have rebased my PR, making all needed changes. It is ready for review. |
Unreported flaky test detectedIf the flaky tests below are affected by the changes, please review and update the changes accordingly. Otherwise, a maintainer should report the flaky tests prior to merging the PR. org.keycloak.testsuite.federation.ldap.LDAPProvidersIntegrationTest#updateLDAPUsernameTest |
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.
Unreported flaky test detected, please review
ahus1
left a comment
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.
Thank you for the updated PR. See below for two changes I ask for before this PR can be merged.
| <DefaultSwitchControl | ||
| name={convertAttributeNameToForm<ClientScopeDefaultOptionalType>( | ||
| "attributes.hide.from.openid.provider.metadata", | ||
| )} | ||
| label={t("hideFromOpenIdProviderMetadata")} | ||
| labelIcon={t("hideFromOpenIdProviderMetadataHelp")} | ||
| stringify | ||
| /> |
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.
I see that this is visible also for SAML scope. IMHO this should only be visible for OIDC scopes given its name. If there be an equivalent setting for SAML, it should be renamed to something generic.
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.
I check if it is not SAML. As I have understood, there is also OID4VC_PROTOCOL scopes now.
| hideFromOpenIdProviderMetadata=Hide from OpenID Provider Metadata | ||
| hideFromOpenIdProviderMetadataHelp=If on, this client scope will be hidden from OpenID Provider Metadata. |
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 is an existing option in the same dialog with the "Include in token scope", and this new option is inverting it by stating "Hide from..."
Please rework this new option to also be name "Include in ...". When doing this, this needs to be inverted to be true by default both in the back end and in the front end.
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.
The main problem with this logic is the migration process from older version.
As I understand, this will need a migration method for making all scopes include.in.openid.provider.metadata to true .
Do we want it? That's why I named it hide.from.openid.provider.metadata.
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.
@cgeorgilakis - thank you for reaching out. I agree a migration method would not be ideal. Instead of a migration, I would suggest to have a default of "true" both in the backend and the frontend. WDYT?
ff5e779 to
7d0a2c6
Compare
Closes keycloak#10388 Signed-off-by: cgeorgilakis-grnet <[email protected]>
7d0a2c6 to
f6f3f66
Compare
|
@ahus1 I have made the requested changes. |
Signed-off-by: Alexander Schwartz <[email protected]>
|
@cgeorgilakis - thank you, looks great. Some small changes here: eosc-kc#1028 As I wasn't allowed push the changes directly (no permission), so I created a PR on top of this PR. Please merge my PR, and then this PR is ready to be merged. Best, |
closes #10388