Interface to encapsulate the combined functionality of user DID association with subject credential requests.
Note: userDidAssociation is optional because will not always be necessary. However is needed for the initial credential requests in order for the customer's user to get an associated DID.
Opted to include as part of the credential requests to eliminate the possibility for a user did / credential request race condition.
Note: credentialRequestsInfo is optional becuase this type can be used strictly for userDidAssocation, despite its name. We opted to keep this functionality under the SubjectCredentialRequet
flow for simplicity of customers implementation. They only have to implement one endpoint in this manner than can perform in either manner.
Interface to encapsulate the combined functionality of user DID association with subject credential requests.
Note: userDidAssociation is optional because will not always be necessary. However is needed for the initial credential requests in order for the customer's user to get an associated DID. Opted to include as part of the credential requests to eliminate the possibility for a user did / credential request race condition.
Note: credentialRequestsInfo is optional becuase this type can be used strictly for userDidAssocation, despite its name. We opted to keep this functionality under the SubjectCredentialRequet flow for simplicity of customers implementation. They only have to implement one endpoint in this manner than can perform in either manner.