You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Sander Bylemans (Jira)" <ji...@apache.org> on 2023/04/19 15:17:00 UTC

[jira] [Created] (NIFI-11469) OpenID Connect StandardClientRegistrationProvider scopes should be configurable

Sander Bylemans created NIFI-11469:
--------------------------------------

             Summary: 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


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)