Choosing SailPoint Tenant Sign-In Methods
Key Takeaways
Site User Name & Password uses the user’s site credentials after registration under the documented invitation model.
Directory Connection uses pass-through authentication against a supported, configured source for the identity profile.
SAML sign-in uses tenant service-provider settings and an external IdP’s metadata, certificate and subject mapping.
Verify sign-in method and recovery for the intended user type in the applicable tenant. Platform privileges are a separate control.
Locate the configured verifier
Start with the user and the intended sign-in route. An identity profile links authoritative data to an identity and has sign-in settings. Tenant SAML federation additionally uses a tenant service-provider configuration. The user level and applicable record scope determine allowed platform actions after authentication. Identify where the user’s credentials are checked so a sign-in fault does not become a proposed access-model change.
| Requirement | Documented path in SailPoint |
|---|---|
| Use the username and password created during site registration | Site User Name & Password in the identity profile |
| Verify a network password against a selected supported source | Directory Connection, also called pass-through authentication (PTA) |
| Require a mobile authenticator for the profile’s supported native sign-in | Multifactor Authentication sign-in option and user registration for the authenticator |
| Use a company SAML IdP to sign into the tenant | Remote identity provider and hosted service-provider settings |
| Recover controlled administration if the usual identity provider or network is unavailable | Set up and test the documented emergency administrator path under authorized procedures |
For the local registration path, confirm invitation configuration and the address the profile uses. Users sign in with the username and password they created during registration. When an external method is configured, follow the applicable external procedure and prerequisite instead. Test the worker’s account and authentication configuration before changing reporting or managed application grants.
Work a pass-through case
Suppose an organization wants employees on a supported Active Directory (AD) source to use their network password. Configure Directory Connection on the employee identity profile, then select the supported authentication source. SailPoint requires aggregation before configuring the authentication source. Confirm the user’s correlated account on the selected source. An identity without an account on the specified authentication source can have an Authentication Source Mismatch. Use the user’s identity details and source inventory to resolve it. In the documented multiple-account case, SailPoint uses the first account it encountered on that source for authentication. That path is separate from the access-profile filter used to choose accounts during automated provisioning.
Test a valid sign-in and an expected rejection in a sandbox with an appropriate test identity. Check the connector and authentication path for the selected source if multiple identities are affected. Review lockout and password behavior together with the source settings. The product documentation advises coordination with Support before changing a production authentication source. A source change can affect more than one sign-in route.
Work a SAML and authenticator case
For Security Assertion Markup Language (SAML) single sign-on, SailPoint acts as the service provider. Confirm the remote identity provider’s entity identifier, appropriate login endpoint and binding, signing certificate, expected subject and tenant user mapping. If you select a custom identity attribute for the platform’s mapping, verify that the attribute is configured as searchable. Check that the user’s actual mapped value corresponds to the IdP’s configured subject before changing the certificate. Provide the tenant’s service-provider settings to the appropriate corporate IdP application. Test the correctly mapped user and a controlled mismatch before enabling a live change. If sign-in at the corporate IdP succeeds but tenant sign-in fails, check identity mapping and trust validation separately. A directly authenticated network password and an IdP assertion travel through different verification paths.
When profile-based Multifactor Authentication is enabled, users register a mobile authenticator and enter its verification code on subsequent sign-ins on that path. SailPoint also documents a separate time-based one-time password (TOTP) registration flow for elevated users who sign in through an external IdP. Elevated users who sign in through an IdP can be asked to register a device as part of setup. After registration, ordinary sign-ins via the IdP do not prompt for that registered SailPoint device in the documented flow. The device is used for direct sign-in when bypassing the IdP, including the emergency path. The IdP’s own policies still govern its authentication checks. Verify which path the user actually took before interpreting a missing prompt or resetting multifactor authentication (MFA).
Document a known allowed test user, account mapping and verified administrative fallback before rolling out changes. Use the actual evidence for sign-in, distinct from role and permission tests. Test that the fallback sign-in remains usable for the intended authorized administrators before relying on it.
See SailPoint’s identity mismatch guidance, identity profile sign-in settings, pass-through authentication, SAML configuration, MFA setup, and emergency access administration.
An employee identity profile uses Directory Connection to an AD source. A new identity lacks an account on that authentication source and gets Authentication Source Mismatch. Which check addresses the leading issue?
Verify the account exists and is properly associated on the selected authentication source, then test network credential sign-in
Enable a broader access-profile selection rule on an unrelated source
Move the employee to a certificate review campaign
Issue a bearer access token to the browser as their password
An elevated user already registered the required SailPoint TOTP device. Which documented path prompts for that device after enrollment?
Every sign-in through the external IdP, regardless of its own configuration
Only the granting of an external payroll entitlement
Only the issuance of a new API client ID
Direct SailPoint sign-in that bypasses the IdP, such as the emergency sign-in path
Sections you finish are checked off in the contents.