PI64924: OPENID CONNECT RP CANNOT LOCATE KEY IN JWK SET

Fixes are available

APAR status

Closed as program error.

Error description

The OpenID Connect relying party is unable to locate the
signature verification key in a JWK set if there is no kid
parameter in the JWT.  The kid parameter should not be
required if there is only one key in the JWK set.

Local fix

Include a kid in the JWT or use an external keystore

Problem summary

****************************************************************
* USERS AFFECTED:  IBM WebSphere Application Server users of   *
*                  OpenID Connect                              *
****************************************************************
* PROBLEM DESCRIPTION: OpenID Connect RP emits 'key is         *
*                      invalid' when there is no kid in a JWT  *
****************************************************************
* RECOMMENDATION:  Install a fix pack or interim fix that      *
*                  contains this APAR.                         *
****************************************************************
In the OpenID Connect (OIDC) Relying Party (RP) Trust
Association Interceptor (TAI), if a "kid" attribute is not
present in the JSON Web Token (JWT), the following error will
occur:
CWTAI2007E: The OpenID Connect relying party (RP) encountered
a failure during the login. The exception is [Failed to
validate id token, exception thrown during verify [key is
invalid]]. Check the logs for details that lead to this
exception.

Problem conclusion

The OpenID Connect (OIDC) Relying Party (RP) Trust Association
Interceptor (TAI) uses the "kid" attribute in the JSON Web
Token (JWT) to locate the certificate to validate the token's
signature in the JSON Web Key (JWK).  If the kid attribute
does not exist in the JWT, an error will occur.

The OIDC RP is updated so that, if there is only signature
verification key in the data obtained from the request to the
provider_<id>.jwkEndpointUrl, that key will be used to verify
the signature.

If there is more than one key received from the
jwkEndpointUrl, then the kid attribute will still be required
in the JWT.

The fix for this APAR is currently targeted for inclusion in
fix packs 8.0.0.13, 8.5.5.11 and 9.0.0.2.  Please refer to the
Recommended Updates page for delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Keywords: IBMWL3WSS, OIDC

Temporary fix

Comments

APAR Information

APAR number
PI64924
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
850
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-06-27
Closed date
2016-07-26
Last modified date
2016-09-14

APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name
WEBS APP SERV N
Fixed component ID
5724H8800

Applicable component levels

R800 PSY
UP
R850 PSY
UP
R900 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
04 May 2022

Tips

PI64924: OPENID CONNECT RP CANNOT LOCATE KEY IN JWK SET

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Fix information

Fixed component name

Fixed component ID

Applicable component levels

R800 PSY

R850 PSY

R900 PSY

Document Information

Share your feedback

Need support?