Secure Credential Sharing
ID Wispera provides zero-knowledge credential sharing using AES-256-GCM encryption. Sharing creates a payload (encrypted passport data) and a key (256-bit decryption key). The server never sees the key.The encryption key is derived client-side and is never transmitted to or stored on the
server. Only the encrypted payload is persisted.
Share Scopes
| Scope | Credential Value Included | Description |
|---|---|---|
full | Yes | Complete passport including the raw credential value |
read-only | Yes (flagged immutable) | Recipient can view but should not export the value |
metadata-only | No | Passport metadata only, credential value is stripped |
Creating a Share Link
CLI
Resolving a Share Link
Share Types
Full Share
Includes the complete passport with credential value. Use for transferring credentials to trusted parties.Read-Only Share
Includes the credential value but signals that it should not be exported or copied.Metadata-Only Share
Strips the credential value entirely. Useful for sharing information about a credential without exposing the secret.One-Time Share
Expires after a single view. Defaults to a 60-minute time window.Share URL Helpers
For web-based sharing, the key can be placed in the URL fragment (after#), which browsers
never send to the server.
Inspecting and Validating Shares
Security Considerations
- The encryption key is never stored on the server. All encryption and decryption happen client-side.
- URL fragments are not sent to servers. The
#keyportion of a share URL stays in the browser. - Audit trail records all share events. Every creation, view, and expiry is logged.
- Use
metadata-onlyfor visibility without exposure. Share context about a credential without revealing the secret. - Combine expiry and view limits. Layer multiple constraints for the strongest protection.