My Oracle Support Banner

Unable To Use HS256 To Sign OAUTH Access Token In Oracle Access Manager 11g R2PS3 (OAM 11.1.2.3) / Oracle Access Manager 12c PS3 (OAM 12.2.1.3) (Doc ID 2432365.1)

Last updated on OCTOBER 29, 2019

Applies to:

Oracle Access Manager - Version 11.1.2.3.0 and later
Information in this document applies to any platform.
Oracle is not responsible for instructions/information from 3rd party sites that may be contained in this KM note.

Symptoms

The customer use R2PS3 OAuth and wants to use HS256 to sign the access token instead of the default RS512 cryptoscheme.

This is related to (from OAM Console) Launch Pad > Mobile security > Mobile OAuth Services > DefaultDomain > Device Profiles > OAuthServiceProfile > Attributes > jwt.CryptoScheme > here try to use HS256.

With HS256 the token will be generated successful but can't be validated.

In OAM managed server diagnostic log there is during validation attempt: 

 

 

Changes

Change from RS512 cryptoscheme to HS256.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.