Set up sign-in with the company account (SSO)
With an identity provider, your staff sign in with the company account they already have (single sign-on). For this, actaPASS speaks OpenID Connect, which Microsoft Entra ID, Okta or Keycloak support, for example.
There is no picture for this page: no domain is verified on the test environment.
- Click Add. At the top is the redirect URI that your identity provider must accept. Enter it there.
- Enter a Name and optionally a Description.
- OpenID Connect meta data document: the address that usually ends in
/.well-known/openid-configuration. Click Verify: actaPASS fills in OAuth 2.0 authorization endpoint, OAuth 2.0 token endpoint and OAuth 2.0 user info endpoint itself. - Application (Client) ID and, if your provider requires it, Client Secret.
- Scopes, e.g.
openid profile email. - Use PKCE (Proof Key for Code Exchange): leave it on if your provider supports it. Registered as SPA (Single Page Application): switch it on if the app is registered as an SPA with your provider.
- Click Save.
Good to know
Section titled “Good to know”- The Client Secret is needed for confidential clients (e.g. Entra ID platform “Web”). For public clients (platform “SPA”), leave it empty.
- actaPASS no longer shows a saved secret. Leaving the field empty keeps it; Remove secret deletes it when you save.
- Anyone who signs in through the identity provider automatically becomes a member of your tenant.