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
We currently have an above requirement and I have a feedback asking if this requirement is necessary when proof of possession of the key material is done by signing the request using the DID you control, and the nonce protection is not necessary?
I know we discussed that this does not work when the issuance of multiple credentials to multiple key materials is requested, but the feedback is that in majority of the cases credentials will be issued to the single key material.
I wonder proof types other than providing a DID can work with a signed request. For example can you sign a request using LinkedData Proof and pass the key material in a DID or a sub_jwk, or is it totally impossible?
The text was updated successfully, but these errors were encountered:
We currently have an above requirement and I have a feedback asking if this requirement is necessary when proof of possession of the key material is done by signing the request using the DID you control, and the nonce protection is not necessary?
Can you please, when the nonce protection of the signed request is not necessary?
We currently have an above requirement and I have a feedback asking if this requirement is necessary when proof of possession of the key material is done by signing the request using the DID you control, and the nonce protection is not necessary?
I know we discussed that this does not work when the issuance of multiple credentials to multiple key materials is requested, but the feedback is that in majority of the cases credentials will be issued to the single key material.
I wonder proof types other than providing a DID can work with a signed request. For example can you sign a request using LinkedData Proof and pass the key material in a DID or a sub_jwk, or is it totally impossible?
The text was updated successfully, but these errors were encountered: