Integrating SWIRL with Enterprise Sources - Part 2: Authenticators

Enterprise sources need enterprise sign-in. Part 2 shows how SWIRL plugs into your identity provider, end to end. First the IdP side, demonstrated in Keycloak (the same flow works for Microsoft Entra ID, Okta, or any OpenID Connect provider): register SWIRL as a client with the standard authorization code flow, and set the callback URL where users return after sign-in. Then the SWIRL side: an Authenticator is a configuration row, just like a SearchProvider. Enter the issuer's endpoints, client ID, callback path, and the JWKS URI that verifies each token - or paste your IdP's JSON and let SWIRL pre-fill the form. The result: sign-in flows through your identity provider, and per-user tokens are passed to the sources that need them. Permission-aware, end to end. 0:00 The IdP side: registering SWIRL as a client in Keycloak 0:17 Client ID, standard flow, and the callback URL 0:37 The SWIRL side: creating an Authenticator Keycloak guide: https://docs.swirlaiconnect.com/Keycloak-Guide.html Try SWIRL: https://swirlaiconnect.com Try the SWIRL skill in Claude Cowork: claude plugin marketplace add swirlai/swirl-claude-plugin #EnterpriseSearch #SSO #OIDC #Keycloak #AI