New OIDC client

The slug below auto-syncs from the name. You can override it manually.

Active org didn't load — using the raw slug without a prefix.

Optional — defaults to custom. Drives the right provisioning form (WordPress / Perfex use the source-app REST API; everything else creates the user directly in WolfieAuth) and the right integration snippets. Can be changed later.

Deployment label — distinguishes a staging copy from production on the apps list. You can stand up a separate client for staging (with its own redirect URIs) next to a production version. Defaults to production. Non-prod envs append a suffix to the clientId: -staging, -dev, -preview — so copies of the same app don't collide. Production leaves the clientId unsuffixed.

Type the bare hostname (e.g. crm.wolfiecloud.com) — no protocol needed; the form forces https:// automatically (except for localhost / .local / .test hosts, which use http://). The Redirect URIs field below fills itself from the domain + app type combo. Changing the app type re-derives them; once you edit the textarea manually, auto-sync stops.

URLs WolfieAuth is allowed to redirect to with the auth code after a successful login. Your app must pass exactly one of these as redirect_uri on the /authorize request — otherwise OIDC refuses (open-redirect protection). One callback per line. Convention: WordPress uses /wp-admin/admin-ajax.php?action=wolfieauth_callback, Perfex uses /wolfieauth_client/callback, SPAs use /callback, everything else uses /auth/callback.