[CXF-8686] JWT role claim incorrectly parsed if not tokenized as string

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.4.6, 3.5.1
• Fix Version/s: 3.5.2, 4.0.0
• Component/s: JAX-RS Security
• Estimated Complexity: Unknown
• Assignee: Colm O hEigeartaigh
• Reporter: Oliver Wulff
• Created: 05/Apr/22 07:01
• Updated: 18/Sep/23 18:48
• Resolved: 07/Apr/22 09:10

Description

The JwtTokenSecurityContext class expects a tokenized string for the role claim. If the JWT contains an array of strings to represent the roles the role claim is incorrectly parsed.

The following line shows that it always first tokenize the array:

https://github.com/apache/cxf/blob/master/rt/rs/security/jose-parent/jose-jaxrs/src/main/java/org/apache/cxf/rs/security/jose/jaxrs/JwtTokenSecurityContext.java#L48

Here is a snippet of the sample JWT:

 

{{{}}
  "sub": "myid",
  "jti": "f42150ef-2743-4ca0-ae06-a23b307edaca",
  "iss": "STS INT",
  "roles": [
    "READ",
    "UPDATE"
  ],
  "iat": 1649079679,
  "nbf": 1649079679,
  "exp": 1649086879,
  "aud": [
    "urn:mycompany:application:foo"
  ]
}

 

I propose to improve this logic thus both roles in tokenized string as well as a propery array list are properly parsed.

 

Here a snippet of the debugger. The above example ends-up with two roles "[READ" and " UPDATE]".

 

Issue Links

• links to: GitHub Pull Request #934