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

Configure Destination Endpoint:
Use only letters, numbers, hyphens, or underscores with no spaces for Endpoint Name
Unique Endpoint Name : Description :
Credentials Forwarding:
JWT Token RS256 signed with account Private Key (verified with the Public Key). e.g. www.example.com/myApp?JWT=mysignedJWT
Complete connection string including endpoint URI and credentials e.g.myexampleAPIGateway.com/myapp?query=myquery&secret=mysecret
SecretID/secretValue and endpoint URI e.g. www.example.com/myApp?userID=encryptedID&password=encryptedPassword

       SecretID Name: SecretID Value:
Secret Value Name:     Secret Value :
         Endpoint URL:
Use the Secrets option for passing credentials in the form of an identifier e.g. UserID and Password, ClientID and Secret Value, TokenID and Token
Forward Endpoint: Verviam will forward an unencrypted request as e.g. www.example.com/myApp?userID=myID&password=myPassword. An encrypted request as e.g. www.example.com/myApp?userID=encryptedID&password=encryptedPassword. The encrypted parameters must be decrypted at the endpoint.

Connection URI:
Optional Parameters:
Use the Connection URI for the destination endpoint connection string. Add optional parameters to complete connection as appropriate
Verviam forwards an unencrypted request to an endpoint as e.g. https://www.example.com/connectionURI?query=myquerystring&userID=myuser&pwd=mypass.
Verviam forwards an encrypted request as e.g. https://www.example.com/connectionURI?params=myEncryptedOptionalParameters.
Encrypted parameters must be decrypted at the endpoint server. See Verviam User Guide

Scope Item: Scope Item Value:

Token Payload:
Endpoint URL: Token expiry (minutes) :
Add JWS Token Payload (max 5 items). Override token default expiry time of one hour as required. Payload Items can be any custom scopes understood by your application, as well as OAuth 2.0 OpenID Connect required elements. Forward endpoint: Verviam will forward a signed JWT request as e.g. https://myServiceEndpointURI?JWT=JWTToken

Credentials Encryption Option:
Forward my secretID/secret, connection parameters and endpoint tags encrypted with my secret Key, protected by my RSA public/private keypair.
Forward unencrypted to my application/system. My network connection is secure, and does not require encrypted message content.

Identity Data Option:
Store encrypted personal identity data for this End User/Endpoint

      User ID :
First Name : Last Name :
           Role : Company :
         Email :             Town :
      Country : PostCode :

Endpoint Tags Option:
Store tags with this End User/Endpoint

Tag Name: Tag Value:

Attribute Tags:

Add/Update User Endpoint

View/Rotate Secret Keys

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.

See Verviam Configuration Guide for more information on how to use the keys

- Keep keys in a safe place. They are only accessible from this page.

The RSA PublicPrivate Keypair: modulusLength: 2048,
publicKeyEncoding: {type: 'pkcs8', format: 'pem' },
privateKeyEncoding: {type: 'pkcs8', format: 'pem'}.

Account Secret Key:

Copy Encrypted Secret Key

Copy Public Key

Copy Private Key

Rotate Keypair