[Federation] Explicitly type JWTs returned from the resolve endpoint

[Vladimir Dzhuvinov]

This is the only OIDC Federation 1.0 related token that remains untyped.

Proposal: application/trust-chain+jwt

(as “typ” JWT header becomes trust-chain+jwt)

[Giuseppe De Marco]

nice hint, however the resolve response is not a trust chain but a jwt that may contain optionally a trust chain.

application/federation-resolve+jwt seems more familiar to me

‌

[Vladimir Dzhuvinov]

Another possible variant: application/entity-resolve-response+jwt.

So that it aligns with application/entity-statement+jwt.

[Giuseppe De Marco]

Well, if we agree it would be time for a PR

I’m ok with application/resolve-response+jwt

[Giuseppe De Marco]

considering that application/entity-statement+jwt doesn’t specify if it’s intended for request or response, we know that the http request to the fetch endpoint doesn’t have this information I’m wondering to have the same approach also in the response mime type

so, I’m also considering application/entity-resolve+jwt

‌

[Michael Jones]

On the 2-Sep-22 Federation Editor’s call, we agreed to define and use “application/resolve-response+jwt“.

[Giuseppe De Marco]

Done here
https://bitbucket.org/openid/connect/pull-requests/300/chore-federation-resolve-endpoint-response

[Michael Jones]

Fixed by https://bitbucket.org/openid/connect/pull-requests/300