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
The current API can create and delete credential metadata via the credential-supported endpoint. Each supported credential type is associated with a supported_cred_id which is used by the controller to issue a credential of that type.
Any updates of the metadata require a new entry (and old entry deleted) which changes the supported_cred_id. This then requires that the controller be updated and redeployed.
The addition of PATCH to the credential-supported endpoint would enable the updating of the metadata without changing the supported_cred_id. For simplicity it could be a wholesale replacement of the JSON configuration.
The text was updated successfully, but these errors were encountered:
The current API can create and delete credential metadata via the credential-supported endpoint. Each supported credential type is associated with a supported_cred_id which is used by the controller to issue a credential of that type.
Any updates of the metadata require a new entry (and old entry deleted) which changes the supported_cred_id. This then requires that the controller be updated and redeployed.
The addition of PATCH to the credential-supported endpoint would enable the updating of the metadata without changing the supported_cred_id. For simplicity it could be a wholesale replacement of the JSON configuration.
The text was updated successfully, but these errors were encountered: