We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When PAR is used in OID4VP, does client_assertion_type parameter replace client_id_scheme parameter?
If PAR is followed as defined, the natural behavior would be to also include client_id_scheme in the object.
The text was updated successfully, but these errors were encountered:
I have same question if PAR is used in OpenID4VP in combination with OAuth 2.0 Attestation-Based Client Authentication @Sakurann @tlodderstedt can you comment on this?
Sorry, something went wrong.
this has been resolved by #263, since client_id_scheme parameter is now removed and client id scheme is part of client_id
No branches or pull requests
Imported from AB/Connect bitbucket: https://bitbucket.org/openid/connect/issues/1925
Original Reporter: KristinaYasuda
When PAR is used in OID4VP, does client_assertion_type parameter replace client_id_scheme parameter?
If PAR is followed as defined, the natural behavior would be to also include client_id_scheme in the object.
The text was updated successfully, but these errors were encountered: