SSO with Okta

This guide connects Plenix to Okta, so your team can click Sign in with Okta on the Plenix login page.

You need to be an administrator in Plenix and an Okta Super Admin or Application Admin.

Option A: OpenID Connect (recommended)

A1. Copy the redirect URI from Plenix

In Settings → SSO, copy the Redirect URI (web platform).

A2. Create the app in Okta

1. In the Okta Admin Console, open Applications → Applications and click Create App Integration.
2. Choose OIDC - OpenID Connect, then Web Application, and click Next.
3. App integration name: Plenix.
4. Grant type: leave Authorization Code ticked.
5. Sign-in redirect URIs: remove the example and paste the Plenix Redirect URI.
6. Sign-out redirect URIs: leave empty.
7. Assignments: choose Limit access to selected groups and pick the groups, or Allow everyone in your organization to access.
8. Click Save.

A3. Copy the details

On the app's General tab, copy the Client ID and the Client secret.

Your Issuer URL is your Okta address, for example https://acme.okta.com. If your organisation uses a custom authorisation server, use its issuer instead (for example https://acme.okta.com/oauth2/default). You can find it under Security → API → Authorization Servers.

A4. Connect it in Plenix

1. Settings → SSO → Connect identity provider.
2. Protocol: OpenID Connect. Button label: Okta.
3. Issuer URL, Client ID and Client secret from step A3.
4. Set Allowed email domains and choose whether to auto-provision new users.
5. Switch on Enable single sign-on and click Save.
6. Test in a private browser window at https://<your-workspace>.plenix.cloud/tenant-login.

Option B: SAML

1. In Okta, open Applications → Applications → Create App Integration, choose SAML 2.0 and click Next.
2. App name: Plenix. Click Next.
3. On Configure SAML:
   • Single sign-on URL: the Plenix Assertion Consumer Service (Reply) URL. Leave Use this for Recipient URL and Destination URL ticked.
   • Audience URI (SP Entity ID): the Plenix Entity ID.
   • Name ID format: EmailAddress.
   • Application username: Email.
   • Under Attribute Statements (optional), add givenName → user.firstName and surname → user.lastName.
4. Click Next, choose This is an internal app that we have created, and click Finish.
5. On the Sign On tab, copy the Metadata URL.
6. On the Assignments tab, assign the people or groups who should have access.
7. In Plenix: Settings → SSO → Connect identity provider, choose SAML 2.0, set the Button label to Okta, paste the IdP metadata URL, set domains and provisioning, switch on Enable single sign-on and Save.
8. Test in a private browser window.

Where to go next

• The full setup guide → Single Sign-On (SSO): Complete Setup Guide
• SSO with Microsoft Entra ID (Azure AD)
• SSO with Google Workspace
• SSO with Okta
• Rolling Out SSO and Fixing Sign-In Problems
• See where this fits in the bigger picture → Integrations Overview — What You Can Connect