[OPENIG-1713] private_key_jwt must support a KeyStore Created: 22/Mar/17  Updated: 24/Oct/17  Resolved: 07/Apr/17

Status: Closed
Project: Identity Gateway
Component/s: OAuth 2.0
Affects Version/s: 5.5.0
Fix Version/s: 5.5.0

Type: Improvement Priority: Major
Reporter: Violette Roche Montane Assignee: Violette Roche Montane
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
depends on COMMONS-159 Move BaseOpenIdResolver#createSigning... Resolved
depends on OPENIG-1412 RFE: Support private_key_jwt for clie... Closed
is required by OPENIG-1694 Doc: Support private_key_jwt for clie... Closed
is required by OPENIG-1730 Doc: support for private_key_jwt2 Closed
is required by OPENIG-1738 Doc: KeyStore attribute for private_k... Closed
Sprint: OpenIG Sprint 101, OpenIG Sprint 102


With OPENIG-1412, the private_key_jwt authentication is supported but a jwk must be provided.
The ClientRegistration must use a KeyManager KeyStore to perform private_key_jwt authentication.

Comment by Violette Roche Montane [ 30/Mar/17 ]

As I experienced it, a KeyStore would be more adapted. The issue will be updated to support KeyStore instead of KeyManager in the private_key_jwt configuration.

Comment by Violette Roche Montane [ 30/Mar/17 ]

The JWK format will be no longer supported in the configuration.

Comment by Jean-Charles Deville [ 24/Oct/17 ]

Closed after 5.5.0-release

Generated at Thu Jan 28 14:36:07 UTC 2021 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.