Federate SenseCrypt IdP with Okta
Register SenseCrypt IdP as an external identity provider in Okta and route one group through it first.
SenseCrypt IdP federates into the identity platform you already run, or serves your applications directly, over OpenID Connect or SAML 2.0. Your directory, policies and application sessions stay where they are; only the moment of proof changes.
All technical resources6 of 6 entries
Register SenseCrypt IdP as an external identity provider in Okta and route one group through it first.
Identify the Entra scenario first: workforce federation, B2B direct federation or an External ID customer tenant. The route, protocol and policy behavior differ.
Salesforce keeps every access decision inside the org; SenseCrypt IdP becomes the identity provider on its single sign-on settings.
Ping stays the federation hub; SenseCrypt IdP joins upstream as an external identity provider, one connection at a time.
SenseCrypt IdP as the OpenID Connect provider for your own application, or behind a platform such as Auth0 that accepts external OIDC providers.
Your application stays the service provider; SenseCrypt IdP signs the assertion after a face check.