You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
The text was updated successfully, but these errors were encountered:
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?
The text was updated successfully, but these errors were encountered: