Namespaces in JWT Claims

[agea]

Describe the bug

when using setting the property in this format:

quarkus.oidc.roles.role-claim-path="https://any.namespace/roles"

the slashes in the namespace are interpreted as path separator and if we have a claim like

{
  "https://any.namespace/roles":["admin"]
}

it's impossible to parse (btw this is a common pattern in Auth0 custom properties)

Expected behavior

There should be a way to specify the path AS IS

Actual behavior

We get an error (visible if enabling TRACE logs) like no claim found at path: https:

How to Reproduce?

1. enable oidc authentication
2. annotate a resource with @RolesAllowed("admin")
3. set quarkus.oidc.roles.role-claim-path="https://any.namespace/roles" in application.properties
4. call the annotated resource

Output of uname -a or ver

any

Output of java -version

any

GraalVM version (if different from Java)

No response

Quarkus version or git rev

2.9.2

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

[sberyozkin]

Hmm, I think a similar issue was resolved awhile back.

[quarkus-bot]

/cc @pedroigor

[sberyozkin]

For example, see https://github.com/quarkusio/quarkus/blob/main/extensions/oidc/runtime/src/test/java/io/quarkus/oidc/runtime/OidcUtilsTest.java#L433 and https://github.com/quarkusio/quarkus/blob/main/extensions/oidc/runtime/src/test/resources/tokenCustomPath.json#L17.
It looks like " is lost or may be there is some extra space somewhere, @agea, can you double check please ?