[Openid-specs-fapi] Issue #157: FAPI part 2 - public clients and mTLS (openid/fapi)

Torsten Lodderstedt issues-reply at bitbucket.org
Sat Aug 4 17:00:18 UTC 2018

Previous message (by thread): [Openid-specs-fapi] Issue #156: FAPI part 2 - request_uri mandatory or optional? (openid/fapi)
Next message (by thread): [Openid-specs-fapi] Issue #158: FAPI part 2 - request object for public clients (signing key?) (openid/fapi)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

New issue 157: FAPI part 2 - public clients and mTLS
https://bitbucket.org/openid/fapi/issues/157/fapi-part-2-public-clients-and-mtls

Torsten Lodderstedt:

§5.2.3,#1 only mentions OATB as holder of key mechanism

mTLS supports certificate-bound access tokens for pubic client and should therefore be mentioned as well

Previous message (by thread): [Openid-specs-fapi] Issue #156: FAPI part 2 - request_uri mandatory or optional? (openid/fapi)
Next message (by thread): [Openid-specs-fapi] Issue #158: FAPI part 2 - request object for public clients (signing key?) (openid/fapi)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the Openid-specs-fapi mailing list