-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat!: added attestation-based client authentication #138
feat!: added attestation-based client authentication #138
Conversation
Co-authored-by: Giuseppe De Marco <[email protected]>
Co-authored-by: Giuseppe De Marco <[email protected]>
I would take in this PR also the alignment on the WIA issuance |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes please, @fmarino-ipzs can you also align the WIA part?
According to today's discussion we find the there is a Google service that allows you to unify both Android and iOS claims and this service releases a JWT signed by Google which certifies the quality of the running app unfortunately this signed JWT doesn't have any crypto key binding to be proved with oauth client-attestation based authentication, therefore we confirm RFC7523 as at this moment is |
Title
Attestation-based Client Authentication adoption for PAR and Token Endpoint
Content
This PR adds the support for the OAuth 2.0 Attestation-Based Client Authentication
Review