Unit 2.2: Identity, RBAC, and Federation
Introduction
Access control on IONOS CLOUD is a design of groups and grants, not a policy document. Unit 1.3 named this the group-and-grant substitution. This unit works out what it means in practice: which accounts sit outside the model, which grants carry more power than their names suggest, and what an external identity provider does and does not take off your hands.
The decisions here shape every later build. A VDC from Unit 2.1 is only as governed as the groups that can reach it. The unit ends by building FinCorp's first operations group and an automation identity in the DCD.
1. The Access Model
1.1 Three Account Types and Two Kinds of Rights
Identity and Access Management (IAM) knows three account types. The Contract Owner is created automatically, exists once per contract and cannot be revoked from its role. An Administrator has the same privileges except changing the payment method, and the role can be revoked. A User is the basic account type and receives only what you give it. Contract Owner and Administrator accounts are exempt from group management because they have access to all contracted resources.
Users receive two different kinds of rights, both through groups:
- Privileges are grants for actions, such as Create Data Center, Create Snapshots, Reserve IP Blocks, Create Internet Access, Use Object Storage, Create Backup Units, Create Kubernetes Clusters and Access Activity Log. Privileges are associated with actions that either create additional costs for the account or give access to services with sensitive data.
- Resource grants give access to resources that already exist. Multi-user management controls access to VDCs, snapshots, images, IP blocks, backup units and Kubernetes clusters, at three levels: Read, Edit and Sharing.
A User can be a member of several groups. When new services are added to the platform, they are not granted to users by default; the owner or an administrator must grant them explicitly.
1.2 How the Grant Levels Behave
The following table summarises the three resource authorizations.
| Grant | What it allows | Design note |
|---|---|---|
| Read | The resource and its objects are visible, and their attributes can be displayed; nothing can be changed or added | Implicit as soon as a group is assigned to the resource. A read-only user can see configuration such as a VM's IP address |
| Edit | Attributes can be displayed and changed; the resource and its objects can be deleted | Covers all elements inside the resource, including delete |
| Sharing | Authorizations for access to the resource can be changed | A user can share only with groups they belong to, and only with the permissions they hold |
As shown above, there is no partial Edit. IONOS CLOUD does not offer granular access management to individual devices within an infrastructure setup, and write permissions cannot exclude delete operations. The practical unit of least privilege is therefore the VDC: if a team may change the application tier but not the data tier, those tiers need separate VDCs (Unit 2.1).
1.3 Least Privilege by Granting Less
Least privilege on this model is a matter of what you grant. Resources created by the Contract Owner are not visible to users by default, and users cannot see or interact with them without being part of a group that has access. IONOS CLOUD recommends three practices: assess which users must have administrative privileges, grant users the minimum access their job needs, and review permissions as roles change.
Two traps deserve explicit controls:
- Ownership outlives privilege. When a user has the privilege to create a resource, such as a VDC, the user becomes its owner, and still has access to it even after the privilege is revoked. Keep creation privileges out of production groups and let administrators create production resources.
- Sensitive copies. Images, snapshots and backups contain confidential data and are explicitly shareable resources. A user with access to a backup can restore the data on a new instance. Grant them per individual user and per sensitivity of the data.
For the most sensitive VDCs and snapshots, add 2-Factor Authentication as a resource restriction. Only users authorized with 2-factor authentication can then access those resources, even if they belong to an authorized group. Administrators and contract owners can force 2-Factor Authentication for sub-user accounts in the User Manager, which uses one-time passwords pursuant to RFC 6238 TOTP. The Contract Owner can also set it as mandatory for Administrator and User accounts.
1.4 Password Policy
Only Contract Owners define the password policy for the sub-users in a contract, and a contract has one password policy. You cannot set a minimum length below 5 characters, and the description is limited to 1024 characters. Plan the policy before onboarding, because it applies to new users. If you delete the policy, the IONOS CLOUD standard applies again.
2. Federation: Authentication, Not Provisioning
2.1 What IAM Federation Does
IAM Federation lets users log in to the DCD with their organization credentials through an external identity provider (IDP), with single sign-on. IONOS CLOUD accepts SAML 2.0 or OpenID Connect (OIDC) identity providers. Its current scope is authentication only; the mapping of federation for access is planned for future iterations.
The onboarding runs through the API. Your organization requests domain ownership, publishes a TXT record with the returned token, and triggers verification; depending on the domain provider, verification can take from a few seconds to up to a week. You then create the identity provider. Calling the federation API requires the Access and manage Identity and Access Management resources privilege.
2.2 What It Leaves to You
Three properties shape the operating model:
- No just-in-time provisioning. User accounts must be pre-created in IONOS CLOUD. Only users with an existing account can link their organization account; new users without an IONOS CLOUD account cannot link.
- No group mapping. Group membership and grants remain in the User Manager; the IDP does not assign them.
- Linking does not remove the native login. After unlinking, a user can log in with their IONOS CLOUD account credentials only. The IONOS CLOUD user exists independently of the link.
The result is a manual joiner, mover and leaver runbook that your identity team owns:
| Event | IDP side | IONOS CLOUD side |
|---|---|---|
| Joiner | Create the identity in the organization domain | Create the user with the same email domain, add it to groups, force 2-Factor Authentication if required; the user links the account |
| Mover | Update attributes | Remove the old group memberships, add the new ones, review resources the user created |
| Leaver | Disable the identity | Delete the IONOS CLOUD user, and delete its API tokens or let them expire; review resources it owns |
Use the activity log (Unit 2.3) as the evidence for each step: it records user logins and resource changes. IONOS CLOUD recommends reviewing user accounts, permissions and activity logs periodically.
3. API Tokens and Automation Identities
The Token Manager generates authentication tokens for the APIs and SDKs. Any user can use it, and it is mandatory for 2FA-enabled and forced accounts. A token belongs to the user who generated it and acts with that user's access: a sub-user token with restricted permissions returns empty results or errors for resources outside its scope. You therefore scope a token by scoping its user.
Token mechanics drive rotation design. Each token has a time to live (TTL) chosen at generation: 1 Hour, 4 Hours, 1 Day, 7 Days, 30 Days, 60 Days, 90 Days, 180 Days or 365 Days. The token value is displayed only once, with an option to download it as a text file. A user can hold up to 100 tokens, which lets you overlap a new token with the old one during rotation. Deleting a token deactivates it immediately, even before it expires.
The pattern for automation is a dedicated User account per pipeline or tool, in its own group, with Edit only on the VDCs it deploys to and no creation privileges it does not need. Personal credentials, and above all Administrator credentials, stay out of automation. If you protect a VDC with 2-Factor Authentication, every account that must reach it, including the automation user, needs it, and those accounts authenticate to the API with tokens from the Token Manager.
FinCorp's design follows these rules. Its production contract has two named Administrators. Engineers federate through the corporate OIDC provider, but each one is pre-created by the identity team. The group fc-prod-platform-ops holds Edit on fc-prod-fra-core and no creation privileges. A separate user, svc-fc-prod-deploy, in the group fc-prod-deploy, holds Edit on the same VDC and authenticates with a 30-day token that the pipeline rotates.
DCD Implementation Walkthrough
You will create FinCorp's operations group, grant it access to the VDC from Unit 2.1, add a member, and issue a token for the automation user. The posture is default-deny: the group receives only the grants listed here.
Prerequisites: an Administrator or Contract Owner account; the VDC fc-prod-fra-core; the member user and the automation user svc-fc-prod-deploy created under Users > Create with a unique email and a password that meets the contract's password policy.
Build goal: Create a group, scope a resource grant, add a member; issue and scope an API token.
Steps (in the Data Center Designer):
- Go to Menu > Management > Users & Groups.
- In the Groups tab, select Create, enter the Group Name
fc-prod-platform-ops, and select Create. - Open the group's Privileges tab and leave every checkbox cleared. Changes on this tab take effect immediately, without saving, so a stray click is a live grant.
- Open Resources of Group, select Grant Access, and choose
fc-prod-fra-core. This enables Read for the group. - On the same entry, select Edit so that the group can manage the VDC. Leave Share cleared.
- Open the Members tab and add the engineer from the Add User drop-down list.
- In the Users tab, select the engineer, open Meta Data, select Force 2-Factor Auth, and select Save.
- Repeat steps 2 to 6 for the group
fc-prod-deploywith the membersvc-fc-prod-deploy. - Sign in as
svc-fc-prod-deploy, go to Menu > Management > Token Manager, and select Generate Token with a TTL of 30 Days. - Copy or download the token value into the pipeline's secret store before you close the window. It is not shown again.
Common mistakes:
- Granting Create Data Center to an operations group. Every VDC its members create stays theirs after the privilege is removed.
- Treating Edit as "change, not delete". Edit includes deleting the resource and everything in it.
- Assuming the IDP removes access. Federation is authentication only; delete the IONOS CLOUD user and its tokens in the leaver step.
- Generating automation tokens from a personal or Administrator account. The token carries all of that account's access.
- Choosing a 365-day TTL for convenience. Pick the shortest TTL your rotation can sustain; up to 100 tokens per user allow overlap.
Summary
Access on IONOS CLOUD is composed from account types, group privileges and per-resource grants. Read is implicit, Edit includes delete, and permissions stop at the resource, so least privilege comes from small groups, separate VDCs and few administrators. Federation removes passwords from the login but not the lifecycle work: users must pre-exist, and groups stay in the User Manager. Automation runs as dedicated users whose short-lived tokens inherit exactly their grants.
Key Points:
- Contract Owner and Administrators reach every resource; keep the Administrator list short.
- Grants are Read, Edit and Sharing per resource; Edit covers all elements inside the resource and includes delete.
- A user who creates a resource owns it and keeps access after losing the privilege.
- IAM Federation (SAML 2.0 or OIDC) is authentication only: no just-in-time provisioning, no group mapping.
- Tokens act as their user; scope the user, choose a short TTL, and delete tokens in the leaver step.
Important Terminology:
- Privilege: a group right to perform an action, typically one that creates cost or reaches sensitive data.
- Resource grant: Read, Edit or Sharing access for a group on an existing resource.
- Automation user: a dedicated User account, with its own group and tokens, used only by one pipeline or tool.