Prerequisites
Last updated
Last updated
Before you start integrating Oten IDP into your application, make sure you have everything you need.
Important: Authorization requirements depend on your client type:
Confidential Clients (Server-side): JAR (JWT-Secured Authorization Request) is REQUIRED
Public Clients (SPAs/Mobile): PKCE is REQUIRED, JAR is FORBIDDEN
Legacy Application Support: If your confidential client application cannot implement JAR due to technical constraints, contact support@oten.dev to discuss alternative solutions.
📖 New to Oten IDP? Start with the Integration Flow Overview to understand the complete process.
Or easily contact support to get your credentials.
For Confidential Clients (Server-side applications):
For Public Clients (SPAs/Mobile apps):
Confidential Clients (Server-side applications):
Public Clients (SPAs/Mobile apps):
For confidential clients, JAR provides enhanced security:
Oten IDP supports only two signing methods for JAR:
Uses your client secret to sign JAR requests.
Pros:
Cons:
Uses Ed25519 key pair for signing JAR requests.
Pros:
Cons:
Note: JWKS endpoint is only required for EdDSA signing. HS256 uses client secret and doesn't need JWKS.
When using HS256 with client secret, you don't need a JWKS endpoint because:
🆘 IMPORTANT: Now, for easy setup, contact support to register your application because the developer portal is not ready yet.
After creating the application, save these important values:
You'll need these Oten endpoints:
Select a JWT library that supports RS256 signing:
Create a .env file (never commit to version control):
Before proceeding, verify:
Ready to start coding? Let's begin with Step 1: Choose OAuth Library (Coming Soon)
📖 Public Client? See the comprehensive PKCE Implementation Guide for SPAs and native mobile applications.
JAR is required for enhanced security
JAR may not be required if PKCE is properly implemented
Contact support to configure public client settings
Request Integrity: Authorization parameters cannot be tampered with
Confidentiality: Sensitive parameters are protected
Authentication: Requests are cryptographically signed
Replay Protection: Using JWT standard claims (jti, exp)
✅ Simple setup - no key generation needed
✅ Uses existing client secret
✅ Good for development and internal apps
❌ Shared secret (less secure)
❌ Client secret must be protected
✅ Very secure - no shared secrets
✅ Industry standard for high security
✅ Recommended for production
❌ More complex setup
❌ Key management required
Oten already knows your client secret
HS256 uses symmetric signing (same secret for sign and verify)
No public key distribution needed
Go to Oten Admin Portal
Log in with your Oten credentials
Navigate to "Applications" section
Click "Create New Application"
Fill in application details:
Application Name: Your app's display name
Description: Brief description of your application
Application Type: Web Application, SPA, or Mobile
Redirect URIs: Where users return after login
JWKS URI: Your JWKS endpoint URL (e.g., https://yourapp.com/.well-known/jwks.json)
Client ID: Public identifier for your application
JWKS URI: Your public key endpoint (must be accessible)
Endpoints: Authorization and token URLs
Public identifier for your application
Safe to include in client-side code
Used in JAR and token requests
Public endpoint hosting your signing keys
Must be HTTPS in production
Must return valid JWKS format
Email: support@oten.live
Documentation: https://oten.gitbook.io/idp-support/
Status Page: status.oten.com (Coming Soon)