...
Success!
Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JPAR-207 They fixed it. We either move to 3.3.2 or 3.4.0. The latter breaks backward compatibility with reporting-api < 3.1.0 - not sure we care, so should use 3.4.0.
Pushed the changes I was working on to the oidc-common dev branch to support JWT signature validation using the new trust engine.Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JCOMOIDC-41 Works for resolving and validating the RSA signature on the id_token that comes back from the OIDC certification simple client test.
Added several misc. classes. Added an OP metadata credential resolver to extract ‘trusted’ keys from the jwks_uri.
Will need a resolver to acquire the client_secret for MAC validation - which I almost already have in the RP for resolving the client_authentication.
Maybe a resolver for PKIX style validation of the public key used using the x5c headers.
Rod
Closed multiple outstanding Jira cases
Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key OSJ-342 Plan is to release a Plugin/Module ASAP, deprecate JPA version immediately and remove Hibernate in V5
Need to loop back around on missing keys (
,Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JPAR-200 Jira Legacy server System JIRA serverId f52c7d31-6eab-3f0e-93c3-231b5754d506 key JPAR-201
...