IDP integration

Who is this guide for?

This guide helps customers create an integration application on the Oten Developer Portal.

It is designed for:

• Organizations that already have a system and users

• Admins or product owners (not necessarily developers)

• Customers who want to enable “Login with Oten” for their system

By following this guide, you will understand:

• Why an integration application is needed

• Where to start if you are new

• How this application is used now and in the future

Oten provides two separate environments to support IDP integration:

• Sandbox – used for integration, testing, and configuration validation

• Production – used for live operation with real users

Partners should start the integration in the sandbox environment. Once the integration has been successfully tested and verified, you can proceed to production for real-world usage.

👉 To learn more about the differences between these environments, see: Environments: sandbox & production

Why create an integration application?

Creating an Application allows your system to connect securely with Oten Identity.

Today, the application is used to:

• Enable Login with Oten for your system

• Manage authentication securely

• Control who can access your application

In the future, the same application can be extended to:

• Manage user roles and permissions (authorization)

• Enable social login and enterprise SSO

• Be published to the Oten Marketplace (if you choose)

• Integrate with other applications in the Oten ecosystem

👉 Think of an Application as a bridge between your system and Oten — you create it once, and it grows with your needs.

New to Oten? Start here

If this is your first time integrating with Oten, start from https://oten.com .

Entry point

1. Go to http://oten.com

2. From the landing page:

   • Select Products → Single Sign-On, or

   • Click Start Integration in the Integration section

3. You will see an introduction page explaining:

   • What Oten Identity is

   • What problems it solves

   • How it helps your organization

4. Click Start Integration

5. Sign in with your Oten account

6. You will be redirected to the Oten Developer ortal

From here, Oten will guide you step by step.

✔ No technical knowledge is required to begin ✔ Clear instructions and ready-to-use settings are provided

What will happen during onboarding?

During the onboarding flow, Oten will guide you to:

• Register your application in Oten

• Generate a Client ID and Client secret

• Configure allowed redirect and logout URLs

• Access SDK and integration guidance

• Test the login flow end to end

⚠️ You do not need to create an application in advance. The Integration Application is created during onboarding.

Before you start

Required

• A valid Oten account

• Access to a Workspace

• Basic information about your application:

  • Application name

  • Redirect and logout URLs

  • Application type (SPA, Web, Native)

Optional (recommended)

• Basic understanding of OAuth 2.0 / OpenID Connect

• Access to your application source code

• Ability to configure environment variables

Step-by-step: Create an integration application

Step 1: Access Developer portal

Access and signing in, the Getting Started onboarding screen will be displayed. All you need is within 1 click to Start Integration button.

Step 2: Review the quick guide and begin

A welcome dialog will appear to provide an overview of the integration journey, helping you understand how to select the right application type for your needs.

1. Take a moment to briefly review the quick guide on the screen.

2. Click the Got it button to start creating your application.

Step 3: Create the integration application

Create your app by:

1. Enter:

   • App name

   • App description (if needed)

2. Click Create app

Your Integration application is now created when you see a successful toast.

Step 4: Create a client

Next, you will create a client for your application.

You will be asked to select a Client type.

Client type selection guide

Use the following guidance to choose the appropriate client type based on how your application is built:

Notes

• Select Single page application if authentication is handled entirely in the browser.

• Select Regular web application if your backend server manages authentication and sessions.

• Select Native application for applications installed on user devices.