Login Security

Every person who works in Xurrent signs in either with a Xurrent password or through your organization's identity provider using single sign-on. On top of that sign-in, Xurrent adds its own multi-factor authentication, session timeouts, and lockout rules. This page is the map of those controls: what each one does, who configures it, and where the detailed procedures live.

Why it matters

Sign-in is the boundary of the account. Everything the role model governs, who can see which records and change which fields, depends on the right person being on the other side of that boundary. The controls below are the ones that establish it.

What the controls are

Password sign-in. The default. Xurrent enforces its own password rules and lockout thresholds.

Single sign-on. SAML and OIDC connectors let people sign in through your identity provider. This is also where identifier matching and just-in-time provisioning are configured, which determine how an incoming sign-in maps to an existing person record.

Multi-factor authentication. Applied on top of either sign-in method.

Session timeouts and lockout rules. How long a session survives inactivity, and what happens after repeated failed attempts.

Who configures it

The security settings are owned by the Account Owner in the Settings console. The SSO, JIT, and SCIM protocol details are documented on the developer portal.

Related

See Single Sign-On for the SAML and OIDC walkthrough, SCIM User for automated provisioning, and Logging In for password sign-in.