JWT/OWSM -- SecurityContext Not Populated (Doc ID 2601220.1)

Last updated on OCTOBER 07, 2022

Applies to:

Symptoms

When trying to call a REST service which is secured via an OWSM "JSON Web Token" (JWT) policy, the JWT passed along with the request is successfully verified against said policy.
However, the Subject/SecurityContext is *NOT* populated correctly.

There is no error but the results are wrong

As an example of a test run, the return is not correct:

user: null # Not OK -- expected: <USER>
<role1>: false # Not OK -- expected: true
<role2>: false # Not OK -- expected: true
<role3>: false # OK
<role4>: false # OK

Cause

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