Appearance
Client-managed Secret Mode
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 DIF: Client-managed Secret Mode for more information.
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 | Page | Note |
|---|---|---|
did:indy | Create | - |
| Update | - | |
| Deactivate | - | |
did:ion | Create | - |
| Update | 🚧 Work in progress | |
| Deactivate | 🚧 Work in progress | |
did:cheqd | Create | - |
| Update | 🚧 Work in progress | |
| Deactivate | 🚧 Work in progress | |
did:ebsi | Create | - |
| Update | 🚧 Work in progress | |
| Deactivate | 🚧 Work in progress | |
did:key | Create | - |
| Update | ❌ Not supported | |
| Deactivate | ❌ Not supported | |
did:jwk | Create | - |
| Update | ❌ Not supported | |
| Deactivate | ❌ Not supported | |
did:ethr | Create | - |
| Update | - | |
| Deactivate | 🚧 Work in progress | |
did:pkh | Create | - |
| Update | 🚧 Work in progress | |
| Deactivate | 🚧 Work in progress |