Discovered when using JWT tokens. In org.apache.cxf.rs.security.jose.jws.JwsJwtCompactConsumer there is a line of code that reads:
If the method "getDecodedJwsPayload()" returns a JSON string like:
then the "fromJson" method returns an incorrect Map.
The problem occurs in org.apache.cxf.jaxrs.json.basic.JsonMapObjectReaderWriter (defined in cxf-rt-rs-json-basic-3.1.10.jar) in the readJsonObjectAsSettable method. Specifically, line 188 reads:
which will cause the wrong comma index to be found for the JSON key "roles" in my example above (apparently commaIndex is used to find the "next json key" position in the json string).
I'm also thinking that it's possible that line 166 could be a problem as well, if a JSON value would ever contain an (escaped) quote character.
This JSON parsing seems fragile... I wonder why a "standard" JSON library wasn't used (perhaps just to not add an additional dependency?)
Proper parsing of commas in JSON values is important for JWT purposes as the constructor of org.apache.cxf.rs.security.jose.jaxrs.JwtTokenSecurityContext expects role claims to be comma-separated.