How do I set up single sign-on for document management?
Configure the supported identity-provider integration for your FormKiQ deployment and map identities to the required site permissions. FormKiQ's commercial authentication capabilities support SSO and custom JWT authorizers, with provider-specific tutorials. Authentication establishes identity; group and site authorization still need configuration. Test the actual access token, audience, role mapping, session behavior, and logout path.
Choose the provider-specific setup
Use the documented Entra ID, Okta, Google Workspace, or Cognito integration for the selected protocol and deployment. Configure callback URLs, claims, group/role mappings, and the API authorizer together. SAML federation into Cognito and an external custom JWT authorizer are different architectures.
For the Cognito JWT endpoint, use the AccessToken as documented. Do not substitute an ID token or assume a token for another app client has the correct audience. Review the current audience configuration and Entra role-mapping notes in the authentication reference.
Validate the user's effective access
Test a new user, an ordinary reader, a user with multiple sites, and a user removed from a permitted group. Inspect the token claims actually received by the backend. Confirm that expired tokens and unauthorized audiences are rejected.
Document refresh/session lifetimes and the operational effect of group changes or sign-out on already issued tokens. Keep an approved administrative recovery path so a federation configuration error does not lock out all operators.
Edition and configuration
SSO and custom JWT authorizer capabilities are included from Essentials with configuration. Identity-provider licenses, Cognito settings, protocol support, and selected app-client behavior are separate requirements.