New — Iris AI drafts your firewall, routing & rate-limit rules. Explore AI features →
Changelog
AccountSecurity

Company sign-in with Okta, Entra ID, Auth0 and Keycloak completes

Members whose company signs in through its own OpenID Connect provider (Okta, Microsoft Entra ID, Auth0, Keycloak and others) now complete the sign-in.

If your company set up single sign-on with its own identity provider (provider type OIDC), signing in stopped at the provider or on the way back to ngris. Google and GitHub sign-in were not affected.

Now the sign-in completes. Your provider sends you back to your setup's own redirect URL, and you land in your account.

What changed

  • Sign-in completes with Okta, Microsoft Entra ID, Auth0, Keycloak and any other OpenID Connect provider.
  • A redirect URL for each setup. Each OIDC setup has its own redirect URL, shown on the Single Sign-On page with a Copy button. A provider's answer is accepted only at its own setup's address.
  • An unverified email is refused. If your provider says the email is not verified, the sign-in stops.
  • The openid and email scopes are always asked for, even if your setup lists other scopes. ngris needs them to confirm who is signing in.

Get started

  1. Under Account → Single Sign-On, check that your provider has type OIDC and that your domain is verified.
  2. Copy the setup's redirect URL from the SSO page into your identity provider's app. It must match exactly.
  3. Read the docs: Single sign-on.

Read the docs

Ask an AI to summarise this page
Deploy
App hosting Edge functions Domains & certificates
Connect
Secure tunnels API gateway Multi-region edge
Protect
Bot protection & challenge WAF & firewall Edge login
Observe & AI
Monitoring Inspector & replay Iris AI MCP server AI Gateway
Developers
Developer tools Docs ngrok policy converter Blog Changelog
Compare
Ngris vs ngrok Ngris vs Cloudflare Tunnel Ngris vs Vercel Ngris vs Netlify Expose localhost guide
More
Solutions Pricing Enterprise Sign in Get Started Free