We (at Nuts Foundation, https://github.com/nuts-foundation/) consider it a reasonably good method for credential issuers that can't or do not wish to pin themselves on using a specific DLT (e.g., did:ion or any other DLT or product-specific DID method): it can be resolved with any HTTP client. That said, for high-profile issuers (e.g. governing bodies) it might not provide enough security.
Another case we came up with is cloud wallets (e.g. personal wallet or an employer-bound wallet extending IDP services). The private key could live in a personal device (authenticator app, personal hardware security device) or in the cloud wallet.
We (at Nuts Foundation, https://github.com/nuts-foundation/) consider it a reasonably good method for credential issuers that can't or do not wish to pin themselves on using a specific DLT (e.g.,
did:ionor any other DLT or product-specific DID method): it can be resolved with any HTTP client. That said, for high-profile issuers (e.g. governing bodies) it might not provide enough security.Another case we came up with is cloud wallets (e.g. personal wallet or an employer-bound wallet extending IDP services). The private key could live in a personal device (authenticator app, personal hardware security device) or in the cloud wallet.