Skip to content
Sudomimus

Take an application live

View as Markdown

Every new application starts as a Draft. A draft can be configured from the With portal, but it cannot start sign-ins or issue sessions.

Prepare the application

Section titled “Prepare the application”

Before going live, complete the readiness checklist on the application page:

  1. Add at least one authentication rule for the sign-in methods you support.
  2. Add at least one realize rule for the people who may sign in.
  3. Add at least one return rule for how the result reaches your application.
  4. Save the client-auth private key and any OIDC secret your backend needs.
  5. Review the application name, sign-in appearance, claim policy, and callback URLs.

The template picker can create a starting set of rules for common web, desktop, game, and OIDC integrations. Review the generated rules before saving them; a template is only a starting point.

Go live

Section titled “Go live”

When the checklist is complete, an organization owner can choose Go live. This changes the application from DRAFT to ACTIVE.

Going live is a separate confirmation. Saving rules does not activate the application automatically. Activation can be blocked if the organization or sector is disabled, or if the organization has reached its application limit.

Disable an application

Section titled “Disable an application”

Use Disable application when you are retiring an integration or responding to a security incident. For self-service organizations, the person disabling it must be the organization’s sole owner.

After disablement:

  • new sign-ins and token refreshes stop;
  • live UserInfo and introspection checks stop accepting the old sessions;
  • an access token may still pass offline signature and expiry checks until its exp;
  • the application no longer counts toward the organization’s active application limit.

Coordinate the change with your application. Clear its local sessions and stop accepting the old integration before treating retirement as complete.

Bring it back

Section titled “Bring it back”

An owner can reactivate a disabled application. Its existing configuration remains available, but activation is checked against the current organization, sector, and quota state.

Applications are not deleted and do not return to Draft. If you are replacing an integration permanently, create a new application with a new applicationAnchor.

Section titled “Related”