Skip to main content
With standard SSO, you generate and use a single URL to create an embed user and session. Omni embed URLs are signed with a secret key used only by your organization. When an Omni server receives the request, it verifies the signature using that secret. If the signature checks out, the request is honored. Two signing formats are supported for standard SSO: Both formats are accepted at /embed/login, so existing integrations will continue to work. Use v1 for new integrations, and plan to migrate existing ones.
Because embed URLs are signed using your Omni organization’s embed secret, it is crucial that your embed URLs are generated server-side rather than client-side. From a security perspective, this protects your embed secret from being exposed to attackers.Also note that the Omni TypeScript SDK utilizes Node’s crypto module, which is only available in Node environments. Attempting to use the Omni TypeScript SDK functions in a client-side context will likely lead to the SDK functions generating improperly signed embed URLs.