[
https://issues.apache.org/jira/browse/NIFI-11469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann resolved NIFI-11469.
-------------------------------------
Fix Version/s: 2.0.0
1.22.0
Resolution: Fixed
> OpenID Connect StandardClientRegistrationProvider scopes should be
> configurable
> -------------------------------------------------------------------------------
>
> Key: NIFI-11469
> URL: https://issues.apache.org/jira/browse/NIFI-11469
> Project: Apache NiFi
> Issue Type: Bug
> Components: Configuration, Security
> Affects Versions: 1.21.0
> Reporter: Sander Bylemans
> Assignee: David Handermann
> Priority: Critical
> Fix For: 2.0.0, 1.22.0
>
>
> We're integrating our NiFi instance with OpenID Connect. We didn't have an
> issue on version 1.19.1.
> When we get redirected from /nifi-api/oauth2/authorization/consumer, the link
> includes all supported scopes found at the
> nifi.security.user.oidc.discovery.url. In our case, there are a lot and this
> causes an HTTP 414 (uri too long). Generally not a good idea to do this,
> because the list can be very long.
> Scopes of the client registration should be configurable, currently it is
> only possible to add scopes. We should be able to fully configure them.
> Classified as bug because situation is not workable.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
