Sovrain
  1. Documentation
  2. Identity provider

Explanation

Access, groups and roles

Why access to applications in Sovrain goes through groups only, what the built-in groups mean, and why a role is a label for the application rather than a permission.

Sovrain answers one question for every sign-in: may this person use this application? It answers it with a single mechanism, groups. This page explains that choice, the three groups every organization starts with, what a role is and is not, and what Sovrain deliberately leaves out.

Access goes through groups only

An application in Sovrain has a list of groups that may use it. A person can sign in to the application if they belong to at least one of those groups, and to no application otherwise. There is no way to give one person access directly, and an application with no groups is closed to everyone.

This can feel indirect when you want to let in a single person, but it pays off as soon as an organization grows. Access follows what people do rather than who they are: when Bob joins Engineering, he gets every application Engineering uses; when he leaves the team, he loses them all in one change. An admin who wants to know who can use an application looks at a handful of groups instead of a long list of exceptions. And when someone leaves, the answer to “what did they have access to?” is the list of their groups.

The same groups serve other purposes too: they decide who must use two-step sign-in, whom provisioning sends to an application, and which accounts can never be shared through delegation. One structure, maintained once, drives all of them.

The three built-in groups

Every organization starts with three groups that Sovrain manages itself and that cannot be renamed or deleted.

All contains every member of the organization, always. Nobody can be added to it or removed from it by hand. Giving All access to an application is the way to say “everyone in the company”, and it keeps working for people who join later.

Admins and Owners are where admin rights come from. A member of either group can open the admin pages and change almost everything: people, groups, applications and policies. Owners have a few extra powers, such as importing a backup over the whole organization and resetting another admin’s sign-in. Any admin can add people to Owners, though, so the difference guards against mistakes rather than drawing a security boundary. There are no finer-grained admin roles, so making someone an admin is a real grant of trust. Make someone an admin covers the practical side, and Security model discusses what admins can and cannot do.

Next to these, an admin can mark any custom group as a default group, so that new members join it automatically.

A role is a label for the application

When an admin gives a group access to an application, they can add a role, such as editor or viewer. Sovrain sends the role to the application at sign-in: as the role claim in OpenID Connect, when the application asks for the groups scope, and as the role attribute in SAML. A person who reaches the application through several groups gets every role those groups carry.

The role is free text, and Sovrain attaches no meaning to it. It grants nothing inside Sovrain and Sovrain does not check what the application does with it. The point is to let each application keep its own permission model while taking the decision of who has which permission out of the application and into the place where people and groups are managed. The application still has to read the role and act on it; Read groups and roles in your app shows how, and Send roles to apps shows the admin side.

In OpenID Connect, the application can also receive a groups claim; both it and the roles come with the groups scope. The claim contains only the groups that give access to that particular application, not every group the person belongs to. An application learns what it needs to make its decision and nothing about the rest of the organization’s structure. SAML assertions carry roles but no group list.

What Sovrain does not do

Some identity providers offer more elaborate access models. Sovrain deliberately keeps to the simple one, and it helps to know what is missing before you plan around it.

No nested groups. A group cannot contain another group. If Engineering should include Backend and Frontend, the members have to be in Engineering themselves. Nesting saves typing, but it also makes the answer to “who has access?” depend on following chains, which is where access mistakes hide.

No conditional rules. Access does not depend on the network address, the device, the country or the time of day. Membership is the whole rule. The one extra condition Sovrain can add is a second step: an application, a group or the whole organization can require two-step sign-in, as described in Two-step sign-in.

No deny rules. A group can only open access. There is no group that takes access away from people who would otherwise have it, so to keep someone out of an application, you make sure none of their groups has access to it.

If an application needs finer distinctions than this, roles are the intended way: Sovrain decides who gets in and with which label, and the application decides what each label may do.