SSO Configuration
Configure Single Sign-On for Silkline with Azure AD (OIDC), Google Workspace, or Okta Workforce as your identity provider
Overview
Silkline authenticates users through its own identity service at auth.silkline.ai. Your identity provider (IdP) connects to that service as an upstream OpenID Connect provider: users click Sign in in Silkline, Silkline hands them to your IdP, and your IdP returns them to Silkline once they have authenticated.
The setup page provides the values specific to your Silkline organization:
A redirect URI (also called a callback URL or sign-in redirect URI) that you register in your IdP. It is specific to your organization.
Verified email domains that identify which accounts the connection covers.
Silkline URLs
Application
https://app.silkline.ai
https://dev-app-gov.silkline.ai
Authentication host
https://auth.silkline.ai
https://dev-auth-gov.silkline.ai
Issuer
https://auth.silkline.ai/realms/silkline
https://dev-auth-gov.silkline.ai/realms/silkline
Redirect URI (per org)
https://auth.silkline.ai/realms/silkline/broker/<org-id>/endpoint
https://dev-auth-gov.silkline.ai/realms/silkline/broker/<org-id>/endpoint
Set up SSO
An organization admin generates a setup link in Settings → Single sign-on and shares it securely with the IdP administrator. The IdP administrator opens the link, follows the provider's instructions, and enters the issuer and client credentials directly on the setup page. The connection is provisioned when setup completes; test a real user sign-in to verify it.
Guides
Domain scoping
An SSO connection applies to the email domains registered for your organization (for example your-company.com). Silkline verifies each domain before a connection can be created, so sign-ins from addresses outside those domains are not routed to your IdP. Contact support@silkline.ai to add or change your domains.
Troubleshooting by identity provider
Microsoft Entra ID (Azure AD): setup validation, AADSTS codes, tenant/cloud, consent, and email claims.
Okta Workforce: app assignments, issuer/server selection, client credentials, and sign-on policy.
Google Workspace: OAuth client and redirect errors, Workspace access policy, account selection, and verification.
Other providers (generic OpenID Connect): issuer discovery and endpoint requirements.
Shared SSO troubleshooting: setup links, domain and account checks, browser sessions, verification, and support evidence.
Last updated
Was this helpful?