Configuration

Configure Kerberos Hub to your own needs.

Once you have installed the Kerberos Hub Helm chart, and you confirm to have all microservices properly running you should be able to access the Kerberos Hub login screen and sign in through the default username and password which was defined during the installation step.

Kerberos Hub login screen after installation.

Kerberos Hub login screen after installation.

Accounts

Once you have executed the post installation you should now have a user with the role owner. The owner role is the highest privileged role and gives access to all features, functions, Kerberos Agents and related recordings of the specific user. An owner has an overview of all connected Kerberos Agents, and can create sites, groups, alerts, channels, etc. The owner can also delegate specific Kerberos Agents, sites or groups to sub accounts.

Sub accounts

Sub accounts are created to delegate access to other users, and have a limited scope or access to the different Kerberos Agents and there related recordings and livestreams.

An example of sub account would be a site owner, a store owner, etc. Who only needs access to the livestreams or cameras from the specific site or store.

On top of that a sub account can have a specific role such as guest or editor. This role will limit the access to specific function and features. On top of that a sub account can have a specific role such as guest or editor. This role will limit the access to specific function and features.

You can create a new sub account by navigation to the accounts page and clicking on the (+ Add Account) button at the left top.

Give another user limited access to Kerberos Hub by creating a sub account.

Give another user limited access to Kerberos Hub by creating a sub account.

Sites

While scaling and installing more and more Kerberos Agents, it might become tedious to manage and structure them properly. Due to this reason the concept of sites was created. A site is a logical grouping of a number of Kerberos Agents that are physically installed at the same location.

By creating sites and assigning Kerberos Agents to a specific site, it is easier to monitor specific video streams and there related recordings/events.

Next to that sites also gives an additional advantage in terms of authorization and access control. As described in the accounts paragraph, a sub account can be granted access to only a limited number of sites, and therefore will only be able to view the Kerberos Agents at a specific location.

You can create a new site, by navigating to the sites page and clicking the (+ Add Site) button at the left top.

Structure your Kerberos Agents by using sites, and introduce Access Control for sub accounts.

Structure your Kerberos Agents by using sites, and introduce Access Control for sub accounts.

Groups

Groups are similar to sites, the only difference is that it is more abstract than a site. A group can be for example “Cash desks”, “Entrance gates”, “All stores of Belgium”, “EMEA sites”, etc. A group can be either a collection of sites, what we call then a site group, or it can contain a number of cameras from one or more sites, what we call a group.

Similar to sites, groups can also be used to give access to specific Kerberos Agents, and introduces a next level of flexibility and access controls. As illustrated before you could have some responsible for all “entrance gates” of all buildings within a specific country. By giving a sub account access to this group, he or she will only see the entrance gates of the different sites and not the other Kerberos Agents belonging to the related sites.

You can create a new group, by navigating to the groups page and clicking the (+ Add Group) button at the left top.

Structure your Kerberos Agents by using groups, another level of flexibility.

Structure your Kerberos Agents by using groups, another level of flexibility.

Cameras

On the cameras page you will have an overview of all the cameras, Kerberos Agents, your (sub) account has access too. This means that if your account only has access to a couple of sites or groups, the cameras page will only show the Kerberos Agents that belong to the relating groups and sites.

Structure your Kerberos Agents by using groups, another level of flexibility.

Structure your Kerberos Agents by using groups, another level of flexibility.

By clicking on the (+ Add Camera) button, you will see a modal explaining you how to connect a Kerberos Agents to Kerberos Hub, and the different deployments which are available.

Assign a Kerberos Agent

As explained in the modal, there are different possibilities to set up and run a Kerberos Agent.

Nevertheless, how you deployed a Kerberos Agent, to connect the Kerberos Agent to Kerberos Hub, you will require the account credentials from your Kerberos Hub account to be shared with your Kerberos Agents. By sharing those credentials you are linking your Kerberos Agents to the relevant Kerberos Hub account.

By navigating to the profile page, and selecting your plan you will find the required credentials for your Kerberos Agents.

Please note that when you are using the Kerberos Hub Saas offering you will need both an access and secret key. If you are using Kerberos Hub self-hosted you will only need an access key.

Get your credentials to link your Kerberos Agents.

Get your credentials to link your Kerberos Agents.

Integrations

You got your accounts setup, sites and groups created and last but not least some Kerberos Agents connected to your Kerberos Hub.

Now it is time to configure some integrations using alerts and channels. The idea of integrations is that you can send messages to other third-party solutions on your own APIs, when an important/interesting event occurred.

Get your credentials to link your Kerberos Agents.

Get your credentials to link your Kerberos Agents.

What’s next

Want to learn more how Kerberos Hub is working under the hood? Then have a look at the Kerberos Hub pipeline page where we introduce the microservice architecture.

Edit this page on GitHub