You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is no fully fledged example containing a JARM-encrypted Authorization Response, which would be helpful to validate implementations. Right now we only have this
The text was updated successfully, but these errors were encountered:
I agree, this would be helpful. Examples that I used for Annex B can be generated using this https://github.com/awoie/annex-b-examples but those are encrypted only, i.e., don't use JWS before encrypting.
giving encrypted JWT examples may not give any concrete benefit to the readers, unless we provide the private key to decrypt them.
the only useful information that might be picked from an encrypted jwt is the header. Anyway, this alone is not so eloquent.
I agree that a representation of the encrypted response is required, while the encrypted payload may be truncated, for editorial and readability reasons, if the private key to decrypt it is not provided
A specification should give a complete working example, if it's needed to provide a public key, that's fine for me.
We could have an encrypted auth response that matches to a previous example of auth request, thus we would only need to add the private key for the auth request example and link to it
There is no fully fledged example containing a JARM-encrypted Authorization Response, which would be helpful to validate implementations. Right now we only have this
The text was updated successfully, but these errors were encountered: