izumo27 opened a new pull request, #25052: URL: https://github.com/apache/pulsar/pull/25052
### Motivation The client’s OAuth2 authentication plugin can be used for OIDC. So, the authorization server metadata path is fixed to `/.well-known/openid-configuration`. However, RFC 8414 defines `/.well-known/oauth-authorization-server` as the default, and some users may want to configure a different path. https://datatracker.ietf.org/doc/html/rfc8414#section-3 This PR makes the authorization server metadata path configurable. ### Modifications - Added the `wellKnownMetadataPath` parameter to make the authorization server metadata path configurable. - Added the `AuthenticationOAuth2StandardAuthzServer` class and the `clientCredentialsWithStandardAuthzServerBuilder` builder, which preconfigure the standard path `/.well-known/openid-configuration` as defined in RFC 8414. ### Verifying this change - [x] Make sure that the change passes the CI checks. This change added tests and can be verified as follows: - Added tests for configurable authorization server metadata path ### Does this pull request potentially affect one of the following parts: - [ ] Dependencies (add or upgrade a dependency) - [ ] The public API - [ ] The schema - [ ] The default values of configurations - [ ] The threading model - [ ] The binary protocol - [ ] The REST endpoints - [ ] The admin CLI options - [ ] The metrics - [ ] Anything that affects deployment ### Documentation - [ ] `doc` <!-- Your PR contains doc changes. --> - [x] `doc-required` <!-- Your PR changes impact docs and you will update later --> - [ ] `doc-not-needed` <!-- Your PR changes do not impact docs --> - [ ] `doc-complete` <!-- Docs have been already added --> ### Matching PR in forked repository PR in forked repository: https://github.com/izumo27/pulsar/pull/6 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
