Skip to content
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

redirect_uri and client_id for x509_san with DC API #437

Open
TimoGlastra opened this issue Feb 24, 2025 · 0 comments
Open

redirect_uri and client_id for x509_san with DC API #437

TimoGlastra opened this issue Feb 24, 2025 · 0 comments

Comments

@TimoGlastra
Copy link
Member

When using DC API with x509_san_dns, should the requirements around redirect_uri/response_uri just be dropped since there is no redirect_uri/response?

If the Wallet can establish trust in the Client Identifier authenticated through the certificate, e.g. because the Client Identifier is contained in a list of trusted Client Identifiers, it may allow the client to freely choose the redirect_uri value. If not, the FQDN of the redirect_uri value MUST match the Client Identifier without the prefix x509_san_dns:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant