Sign-in
Okta with DigiOS.
People sign in with Okta, and the users and groups in your directory decide who gets in.
What moves each way
Okta
- Sign-in: Into DigiOS
- Users: Into DigiOS
- Groups: Into DigiOS
- Deactivation: Into DigiOS
DigiOS
| What | Direction | Documents and data | When |
|---|---|---|---|
| Sign-in | In | A SAML assertion or an OpenID Connect token that says who the person is | Each time a person signs in |
| Users | In | Names, work emails and whether each person is active | When Okta pushes a change |
| Groups | In | Group membership, mapped to the roles you choose in DigiOS | When Okta pushes a change |
| Deactivation | In | A person removed in Okta is switched off in DigiOS | When Okta pushes the change |
How DigiOS works with Okta
You add DigiOS to Okta as a SAML 2.0 or OpenID Connect app, and your people sign in with their Okta account. Okta can also provision users and groups into DigiOS over SCIM 2.0, so a person added or removed in Okta is added or removed here.
- Where it stands
- Designed1 Nov 2026
- About Okta
- Okta is an identity provider that companies use to manage who signs in to which applications.
- Your account
- You keep your Okta directory. DigiOS is added to it as an app, and your administrator decides who gets in.
- If a document is rejected
- A person your directory doesn't allow is not let in, and sees the directory's message.
Questions about Okta
SAML or OpenID Connect?
Either. We support both and set up the one you choose.
Can we require a second factor?
Yes. Okta's own sign-in rules apply, and DigiOS can also ask for a second factor of its own.
What happens when someone leaves?
With SCIM, the person is switched off in DigiOS when you deactivate them in Okta. Without it, an admin switches them off.
Ask about Okta.
Tell us what you run and what you want Okta to do. A person answers in writing.