Set up the Identity Provider

Cloudgate's Identity Provider manages the people who sign in to your apps. Configure the sign-in experience, allowed redirects, and registration behavior before connecting a client application.

Configure identity settings#

Open Web Apps → Identity Provider. Review the tenant's token, redirect, and registration settings. Use the exact callback URLs required by your application's supported login flow, including the local development callback when needed.

Identity settings are shared tenant services. Check existing apps before changing registration or redirect configuration for a new app.

Create a test account and role#

Use App Users to create or manage a dedicated test account, and App Roles to review its grants. Start with the permissions the app actually requires.

Account users under Settings → Users administer Cloudgate itself. They are not interchangeable with app users; a linked account can connect the experiences without making their permission systems identical.

Connect the application#

Use the app template or installed SDK's supported identity setup. Configure the tenant, API environment, callback, and post-login destination. Let the supported session flow manage token handling and refresh rather than inventing a second login mechanism in the app.

Protect workflow entry#

Add an IdP Authorize node before private business operations. Choose its output and optional role/permission requirements. Use its result for record ownership checks and queries.

Remember that gateway API-key requirements are a separate layer. A valid app-user token does not automatically satisfy a required gateway key.

Verify the whole journey#

Test registration if enabled, login, callback navigation, refresh, sign-out, and an expired or invalid session. Call a protected workflow with no token and with a user lacking permission. Confirm that neither can reach the private operation.

Use fixture users: sandbox and production workflows share the tenant's app identities. Continue with authentication patterns and users and roles.