Welcome!
What did you expect to see?
I would find it useful to have an endpoint such as */jwt which will read a header for a JWT token, decode it, and display its claims and validation information in the response. This functionality is particularly useful when implementing OIDC middleware with whoami as the backend.
If there is interest in this feature being contributed to this repository we can discuss what the implementation looks like regarding header configuration and routing. If there is no interest for this feature upstream, I am also happy to implement this in a fork.
Welcome!
What did you expect to see?
I would find it useful to have an endpoint such as
*/jwtwhich will read a header for a JWT token, decode it, and display its claims and validation information in the response. This functionality is particularly useful when implementing OIDC middleware withwhoamias the backend.If there is interest in this feature being contributed to this repository we can discuss what the implementation looks like regarding header configuration and routing. If there is no interest for this feature upstream, I am also happy to implement this in a fork.