Skip to content
ReleasesGitHub

Okta overview

Aembit is part of the Okta Integration Network (OIN), the catalog of prebuilt app integrations that Okta maintains. The integration lets administrators and users sign in to your Aembit Tenant: Aembit Tenants serve as isolated, dedicated environments within Aembit that provide complete separation of administrative domains and security configurations.Learn more with Okta as the Single Sign-On (SSO): An authentication scheme that lets users sign in once through a central identity provider, such as Okta, and then reach several applications without signing in to each one separately.Learn more provider. Sign-in works over OpenID Connect (OIDC): An identity layer built on top of OAuth 2.0 that lets applications verify the identity of a user or workload and obtain basic profile information using JSON Web Tokens (JWTs).Learn more(opens in new tab) 1.0 or Security Assertion Markup Language (SAML): An XML-based open standard for exchanging authentication and authorization data between an identity provider and a service provider, commonly used for Single Sign-On (SSO).Learn more(opens in new tab) 2.0.

How the integration differs from a custom Okta application

Section titled “How the integration differs from a custom Okta application”

You add the Aembit integration from the Okta app catalog instead of building a custom application in Okta. In Okta, you enter your Aembit Tenant ID and, for OIDC 1.0, the ID of the Identity Provider you create in your Aembit Tenant. You don’t copy a redirect URL from Aembit into Okta.

To set up the integration, see How to set up Okta SSO with your Aembit Tenant.

To build a custom Okta application for OIDC 1.0 instead, see the Okta tab under Provider-specific examples. For SAML 2.0, see How to create a SAML 2.0 Identity Provider.

See also

Section titled “See also”