Skip to main content

Identity management

Your customers sign in to OSIE to reach the services you offer — a portal, billing, support — and their identity has to end up connected to projects and resources in OpenStack. Identity management is how that connection is made.

OSIE includes a complete, built-in identity service: user registration, login pages, credentials, two-factor authentication, passkeys, and an OpenID Connect authorization server. No external identity infrastructure is required, and where you already have one, any part of the sign-in can be delegated to it. On top of that service, users are organized into realms — one sign-in boundary per customer, or one shared boundary for self-service sign-ups, or both at once.

Where to start​

New to OSIE? Read Identity and access model first. It follows one user from signing in to running a server, and shows what exists in OSIE and what exists in OpenStack at each step, and how access to each project is bounded. From there, Roles and permissions covers who may do what, in the portal and from the OpenStack CLI.

Both pages cover the model. The pages below cover what is configured at deployment time, in Helm values and on the OpenStack side.

Configuring it in the dashboard​

Realms, identity providers and OpenStack access are day-to-day configuration, and live in the Administrator's manual: