This adds support for configuring NimbusJwtClientAuthenticationParametersConverter to any AbstractWebClientReactiveOAuth2AccessTokenResponseClient as an additional parameters converter, which in turns adds reactive support for jwt client authentication.
Closes gh-10146
Check for multiple access tokens on the ServerHttpRequest rather than get get first. If multiples are found throw a OAuth2AuthenticationException.
Closes gh-5708
The JDKs 9 and 10 are no longer supported by Oracle and the
CAs are not up to date, so removing from the build.
18:13:02 * What went wrong:
18:13:02 Execution failed for task ':buildSrc:compileJava'.
18:13:02 > Could not resolve all files for configuration ':buildSrc:compileClasspath'.
18:13:02 > Could not resolve com.thaiopensource:trang:20091111.
18:13:02 Required by:
18:13:02 project :buildSrc
18:13:02 > Could not resolve com.thaiopensource:trang:20091111.
18:13:02 > Could not get resource 'https://repo.maven.apache.org/maven2/com/thaiopensource/trang/20091111/trang-20091111.pom'.
18:13:02 > Could not GET 'https://repo.maven.apache.org/maven2/com/thaiopensource/trang/20091111/trang-20091111.pom'.
18:13:02 > sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
18:13:02 > Could not resolve net.sourceforge.saxon:saxon:9.1.0.8.
18:13:02 Required by:
18:13:02 project :buildSrc
18:13:02 > Could not resolve net.sourceforge.saxon:saxon:9.1.0.8.
18:13:02 > Could not get resource 'https://repo.maven.apache.org/maven2/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8.pom'.
18:13:02 > Could not GET 'https://repo.maven.apache.org/maven2/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8.pom'.
18:13:02 > sun.security.validator.ValidatorException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to request
When the cert-content is not valid, the assert output message is not correct.
Because it outputs too many dashes .The const X509- and PKCS8-PEM_HEADER already includes the dashes.
I took the output message via copy and paste, but it was still not valid ;-(
Only the output is affected, the checks itself is correct.