Enabling SSO for Octopai with Entra ID (Former Azure Active Directory)

Supported Protocol: JWT over OAuth 2.0

OAuth 2.0 and OIDC for Single Sign-On (SSO)

OAuth 2.0, serving as an authorization framework, allows third-party services to exchange web resources on behalf of users, utilizing access tokens over HTTP. When paired with OIDC, it introduces an authentication layer, verifying user identity before any authorization or data exchange, enhancing the security model.

Key benefits include:

Delegated Access: The synergy of OAuth 2.0 and OIDC is ideal for scenarios requiring Octopai's systems to access metadata on behalf of users securely, without directly handling user credentials.
Scalability and Flexibility: This combination supports a wide array of applications, meeting diverse client requirements from desktop and mobile apps to server-side and client-side applications.
Enhanced Security and Azure AD Compatibility: Integration with Azure AD ensures a reliable and secure ecosystem, crucial for enterprise environments.

Implementing OAuth 2.0 with OIDC enriches our SSO capabilities, streamlining authentication across services with a single set of credentials. This demonstrates the protocols' reliability and security, endorsed by critical sectors like banking, manufacturing, and healthcare.

For those upholding the highest data security and governance standards, our alignment with OAuth 2.0 and OIDC, facilitated by Azure Active Directory, signifies a proactive, security-first approach. It ensures our platform interactions adhere to stringent security protocols, evolving with digital threat landscapes and regulatory demands.

Octopai's adoption of OAuth 2.0, enhanced by OIDC for authentication, underscores our commitment to security and meeting the complex needs of our diverse clientele. We are dedicated to continuous improvement, aligning with industry-best practices to deliver the most secure, efficient, and compliant data lineage solutions available.

How to set up SSO authentication for Octopai using Entra ID (Former Azure Active Directory)

Sign in to the Azure portal.
If you have more than 1 tenant choose your Azure AD tenant by clicking on your account in the top right corner of the page, followed by clicking on the Switch Directory navigation and then select the appropriate tenant.
Click on Azure Active Directory In the left-hand navigation pane.
Click on App Registrations and click on New application registration.
Fill The redirect URI (Same as Your Octopai application Url)
For Web Applications, provide the Sign-On URL, which is the base URL of your app, where users can sign in https://app.octopai.cloud/customer_Login/Home/SignIn
Redirect URL: https://app.octopai.cloud/customer_login/Register/index

Once you've completed registration, Azure AD will assign your application a unique client identifier (Application (Client) ID). We need this value in the next sections, so copy it from the application page. And send it to Octopai

Please send us:

Your Tenant Name or ID
Your Application (Client) ID
The Redirect URI you set (https://<yourname>.octopai.com/)

Please note: After you submit your settings information, the configuration will be finalized by Octopai Support team.
Only once this is done, the SSO will be ready to use.