01 / Preparation

Register an application

Define the application's purpose, audience, and deployment URLs. An administrator then registers the application and grants the required permissions. Application registration and the private package registry do not currently offer anonymous self-service access.

1. 1

   Prepare application details

   Provide the application name, owner, tenant, intended users, and the roles and resources it needs to access.

2. 2

   Confirm the client type and URLs

   Choose Web BFF, Web SPA, or a native application. Provide allowed origins, exact callback URLs, and post-logout return URLs. Register local development and deployed clients separately.

3. 3

   Obtain configuration and confirm policies

   Ask your administrator for the client ID, application permissions, and integration test arrangements. Confirm the login template, session policies, and step-up authentication requirements.

1// Replace example values. This checklist is not a ready-to-submit API request.2{3  "application_name": "Your application name",4  "owner": "Application owner",5  "client_type": "Web SPA",6  "origin": "https://app.example.com",7  "redirect_uri": "https://app.example.com/auth/callback",8  "post_logout_redirect_uri": "https://app.example.com/"9}

Replace example domains with your actual URLs. Callback URLs must exactly match the registration; do not use wildcards.