Simple Secure Identity Management
Cloud IDaaS for Internet End Users, Applications and Devices
Configure End Users. Signed JWT tokens protect your request from origin to endpoint via the Verviam API Gateway.
Configure end users and endpoint REST APIs.
Credentials can be forwarded encrypted, unencrypted, or as a signed JWT token, using the account secret key. Endpoint services are authenticated at the Verviam API Gateway before being forwarded to destination URIs. See the
- End users can be e.g. user ID, device ID, client ID, signed JWT.
- Secrets can be e.g. Password, Client Secret, JWS Token with OpenID Scopes
- Policy based tags provide access protected resources (ABAC).
Configure End Users. Configure end users and endpoint REST API URI to access protected resources. End users can be people, devices or applications. Signed JWT tokens protect your request from your origin to your endpoint URI via the Verviam API Gateway. Credentials are forwarded encrypted, unencrypted, or as a signed JWT token, using account Public/Private Key Pair. See Configuration Guide.    Add services in the table below.
|Save Logs as CSV|
It is advisable to rotate keys regularly as a strong security measure. This operation cannot be undone!
You must copy all account REST APIs again as the encryption values of your services will be updated.
The new keys may require updated decryption configuration on your system, to decode your endpoint encrypted parameters.
Verviam Configuration Guide for more information on how to use the keys
The RSA PublicPrivate Keypair: modulusLength: 2048,
Copy Encrypted Secret Key
Copy Public Key
Copy Private Key
|     Rotate Keypair        ||              |