> For the complete documentation index, see [llms.txt](https://oten.gitbook.io/identity-support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://oten.gitbook.io/identity-support/integration/integration-document/idp-integration/environments-sandbox-and-production.md).

# Environments: sandbox & production

To support a safe and structured integration journey, Oten provides two separate environments for Identity Provider (IDP) integration: **Sandbox** and **Production**.

Each environment serves a distinct purpose in your integration lifecycle.

#### Sandbox environment (for integration & testing)

The sandbox environment is designed for development, integration, and testing.

This is where partners should start.

In the sandbox environment, you can:

* Create and configure an integration application
* Test **Login with Oten** flows end-to-end
* Simulate user authentication without impacting real users
* Safely experiment with configuration changes

**Key characteristics:**

* Isolated from production systems
* Uses test data and test users
* No impact on live customers or business operations
* Intended for trial, validation, and troubleshooting

> We strongly recommend completing all integration and testing in the sandbox environment before moving to production.

#### Production environment (for live usage)

The production environment is used for live, real-world integration after your setup has been fully validated in sandbox.

You should use production when:

* Your integration has been tested and verified in sandbox
* You are ready to serve real users
* Your system needs to authenticate against Oten’s live identity services

In the production environment:

* Authentication requests affect real users
* Configuration changes have live impact
* Stability, security, and correctness are critical

**Important notes:**

* Production credentials and settings are separate from sandbox
* Only verified and completed integrations should be promoted to production
* Any misconfiguration may affect real user access

#### Recommended integration flow

1. **Start in Sandbox**
   * [Go to sandbox](https://developer-portal.sbx.oten.dev/) - Developer portal
   * Create an integration application
   * Complete configuration and testing
   * Validate login, logout, and permission flows
2. **Move to Production**
   * [Go to production](https://developer.oten.com/) - Developer portal
   * Recreate or promote your configuration for production
   * Switch to production endpoints and credentials
   * Go live with real users

This separation ensures a safe, predictable, and enterprise-ready integration experience for all Oten partners.