Simple Secure Agent Workflow

Verv A2A


A signed Verv IAM JWT (JSON Web Token) is issued for each endpoint, to be validated prior to request forwarding, secured by PKI rotated keypair.

Secure Agent Workflow Orchestration
Connect services. Configure workflows. Execute securely.

Verv A2A

$15 USD per month
  • Independent Verv A2A account
  • Secure service integration
  • Automated agent workflows
  • Scheduled and on-demand execution

Verv A2A Partner

$100 USD per month
  • Complimentary Partner account
  • 10 independent customer accounts
  • Resale and distribution opportunities
  • Configure accounts for your customers
Sign in to your account

       
 
Enter 6 digit PIN:     Enter password:  
  Your account requires VPN Sign in. Enter Account ID to verify Verviam VPN connection.
Turn off VPN requirement
To ensure security of authentication, permitted maximum elapsed time since connection to VPN is 4 hours.
Connect business services securely.
<
Verv Safe Configure REST services, authentication, encrypted credentials and response controls. Verv Safe Build ordered, multi-step workflows with approvals, conditional routing and secure execution. Verv Safe Execute workflows securely, monitor outcomes and retrieve transaction and risk assessment reports.


     

Verviam Download Logs as CSV

Business Workflow Configuration
Config Configure Business Workflows:
Build Workflows:



REST Service Configuration â„šī¸ show/hide
Configure Secure REST Services and Workflows

Connect business services using secure REST endpoints. Configure authentication, encrypted credentials, request and response tags, and multi-step workflows.

Choose encrypted credential forwarding, signed JWT authentication, or unencrypted forwarding where appropriate.

For technical details, see the Verv IAM Configuration Guide

Config Configure REST Service:
Use only letters, numbers, hyphens, or underscores with no spaces for Endpoint Name. Please input carefully, as the name and description cannot be changed after the Endpoint is created.

 Description :
Connection & Credentials Forwarding
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



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: Verv IAM 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.
          

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

   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: Verv IAM 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 Configuration
Identity Data Option:
  Store encrypted identity data for this End User/Endpoint       X

 
    
        
     
      
Endpoint Tags Option:
  Store tags with this End User/Endpoint (maximum 25 tags)        X


       OK Add Tag
OK

Response Tags Option:
  Define response tags for this End User/Endpoint (maximum 25 tags)        X


       OK  Add Tag
OK

Verviam

Require Verv IAM VPN to sign in to the account:

  Verv IAM VPN is required to access the account.
  Verv IAM VPN is NOT required to access the account.


**Important**: This updates the Verv IAM VPN configuration. Note when a VPN sign in is required, a VPN client must be installed and configured before you can sign into the account. You cannot configure your VPN unless you have first set up your VPN Client.
Your VPN username is e.g. VerviamAccountID@verviam.directory.com e.g. VP123456789@verviam.directory.com


    copy Copy VPN Password    

Instructions for configuration of VPN to sign in to your Verv IAM Account

Download your VPN configuration file. Configure your VPN Client to use this file to log on to the VPN. Download and install an OpenVPN Client for your device operating system. We recommend AWS OpenVPN Client 3.0.0 or later

VPN Configuration Guide:
    1. Your VPN username is your AccountID@verviam.directory.com e.g. VP1234567890@verviam.directory.com. Copy and save your password.
                VP1234567890@verviam.directory.com
                YourVPNPassword
    2. Download and install AWS OpenVPN Client for your device operating system
    3. Download and save your VerviamVPN.ovpn configuration file. This is the configuration file required by your VPN Client.
    4. Change the Verv IAM VPN config file with the line auth-user-pass "c:\\my-config-directory\\login.txt". Note Windows requires double backslash.
    5. Download and save your VPN client certificate e.g. "c:\\my-config-directory\\client1.domain.tld.crt".
    6. Change the Verv IAM VPN config file with the line --cert. Note Windows requires a double backslash.
    7. Download and save your VPN client key e.g. "c:\\my-config-directory\\client1.domain.tld.key".
    8. Change the Verv IAM VPN config line --key. Note that Windows requires a double backslash.
    9. Configure your downloaded VPN client to use your saved Verv IAM VPN configuration file - VerviamVPN.ovpn
    10. Connect to the VPN. You must be signed into the VPN before you can sign in to the Configure Users, Account Profile and Portal pages.