In this mode, the Universal Registrar does not itself have access to the secrets used by DID operations. In other words, the Wallet Service is not used. Instead, the Universal Registrar will ask the client to perform cryptographic operations such as generating keys and signing payloads.
See https://identity.foundation/did-registration/#client-managed-secret-mode for more information about client-managed secret mode.
This can be enabled by adding clientSecretMode: true to the options input field.
See the following pages for examples of client-managed secret mode as it applies to specific DID methods:
| DID Method | Client-managed secret mode |
|---|---|
did:indy |
did:indy - Create did:indy - Update did:indy - Deactivate |
did:ion |
did:ion - Create did:ion - Update - work in progress did:ion - Deactivate - work in progress |
did:cheqd |
did:cheqd - Create did:cheqd - Update - work in progress did:cheqd - Deactivate - work in progress |
did:ebsi |
did:ebsi - Create did:ebsi - Update - work in progress did:ebsi - Deactivate - work in progress |
did:key |
did:key - Create did:key - Update - not supported did:key - Deactivate - not supported |
did:jwk |
did:jwk - Create did:jwk - Update - not supported did:jwk - Deactivate - not supported |
did:ethr |
did:ethr - Create did:ethr - Update did:ethr - Deactivate - work in progress |
did:pkh |
did:pkh - Create did:pkh - Update - work in progress did:pkh - Deactivate - work in progress |