Configure production sign-in

Your published Production app signs its people in through OwlMeans sign-in. If you export the project and run it on your own infrastructure, the copy can keep using the same sign-in. The Authentication tab of the production dialog gives you the settings to copy. Independent production sign-in is included in Pro.

1. Publish the app first. The settings appear once the production site is live.
2. In the project, choose Publish to open the “Production environment” dialog, then open the Authentication tab.
3. Copy the Issuer URL and the OIDC Client ID with their copy buttons.
4. Choose Reveal secret to show the Client Secret, and copy it. Treat it like a password and store it only in your hosting configuration.
5. Under Standalone redirect URLs, enter one full callback URL per line for each self-hosted deployment, for example https://app.yourdomain.com/dispatcher. Choose Save redirect URLs.
6. Publish again. The saved URLs are applied on the next Publish.
7. Add the issuer, client ID and secret to your self-hosted app’s configuration, and sign in once to check that it works. The generated backend reads them as OIDC_ISSUER_URL, OIDC_CLIENT and OIDC_SECRET, and needs all three.

Redirect URLs must match exactly, with no wildcards. A generated app signs in through its /dispatcher page, so register that page on every host you use.

If your plan does not include it, the tab says “A standalone sign-in is not included in your current plan.” See plans and included features for what each plan covers.

The production site itself needs no extra step. People sign in as described in How your app’s users sign in. Manage Production people in Choose Preview or Production users. Back to the section overview.

Application example

Category: Project and task management. Example: Task Grove, a task board for a small team. A company that self-hosts Task Grove registers its own address and keeps signing its team in with the same codes.