Integrations, you need a secure way to interact with them through the creation of an account.
By creating an account you will receive credentials that give access to the Kerberos Vault’s providers, integrations and APIs. Account credentials are being used by a Kerberos Agent to send recordings, and/or through custom code by API calls to download and/or forward recordings.
Before you can configure a provider, make sure you have installed a Kerberos Vault inside a Kubernetes cluster.
Configuration of an account
Once you have set up your Kerberos Vault instance, and have successfully login to the application, you should see the account navigation item on the left.
When selecting the
+ Add Account button, a modal will open that allows you to configure a specific account. Go a head and select one from the list.
Once you’ve provided all the required fields and enabled the account, you should be able to use it and link your Kerberos Agents to your Kerberos Vault.
There are a couple of interesting configurations you can enable on account level. Let’s have a look and verify what settings are available, and what they are used for.
- Account name: a random name identifying the account.
- Main provider: the default provider the account is linked too.
- Day limit: the expiry date of all recordings stored through this account.
- Integrations: all the integrations which will be executed each time a recording was stored in a storage provider.
By defining a
directory you force an account, and all its producing Kerberos Agents, to store all recordings in a specific subdirectory on the selected storage provider.
By defining the
asteriks (*) value, you will provide more flexibility and deligate the subdirectory to the connected Kerberos Agents. This means that different Kerberos Agents can store in different subdirectories, although they are connected to the same
These credentials are shared with Kerberos Agents, Kerberos Vaults (chained/forwarding) and/or Kerberos Hub. It’s the authentication information needed to push recordings or retrieve recordings from Kerberos Vault.
When connecting Kerberos Vault to Kerberos Hub through the integration, an event is forwarded to the Kerberos Hub pipeline. By enabling or disabling the cloud analysis you will enable or disable any cloud computing done on the Kerberos Hub.
This is required if you only want to store recordings and avoid any analysis in the cloud, and thus reduce bandwidth from Kerberos Vault to the Kerberos Hub microservices.
When connecting Kerberos Vault to Kerberos Hub through the integration, an event is forwarded to the Kerberos Hub pipeline. By enabling or disabling the edge analysis you will enable or disable edge computing in Kerberos Vault.
This is useful when you want to compute specific analysis at the edge and forward the relevant results to the Kerberos Hub pipeline. This avoids bandwidth consumption but increases computing power at the edge.