IdP is an acronym for "identity provider." Identity providers are services that manage identities. Organizations that use SuccessPro typically have an existing IdP in place to log in one time to access many systems. In most cases, these are hosted in the cloud and work with SSO providers to authenticate users. 
Microsoft Azure Active Directory
Oracle Identity Management
Okta Identity Management
Zoho Vaul.
OneLogin
LogMeIn Pro
All of these implement SAML SSO protocol exactly the same. SuccessPro can work with any of these and others as long as the protocol is followed. 
SAML stands for Security Assertion Markup Language. SAML version 2 is the version of the standard for exchanging authentication and authorization identities between security domains. It uses an XML-based protocol. 
Client - Complete the SSO Getting Started Questionnaire 
Client - Populate all TSIDs for users in sPro (click here to learn more)
Client - Automate provision & hierarchy (see here to learn more)
ActiFi - Submit JIRA request to enable SSO endpoint
ActiFi - Provide Client xml files from dev & prod which contain location, attributes, & public cert.
Client - Via email, provide ActiFi system location URL(s), public certs, & attributes to share.
- Typically this will be xml format that looks similar to ActiFi’s. 
ActiFi - Configure SuccessPro relay state identify & service provider defaults via admin configuration screen. 
Client - (if applicable) If SSO login button on sPro screen will be needed, the client is to provide SP-Initiated IDP Login URL. 
Client/ActiFi - Test the SSO & mutually sign off before completing this process. 
ActiFi will typically implement as fast as client-side tech teams. ActiFi development operates in two-week sprints. Assuming the automated provisioning & hierarchy process is already in place, the SSO process can take 2-3 weeks, on average. 
Yes, but it's not recommended. Errors can often occur due to missing users, conflicting stale user data in either system, etc. As a result, the SSO will not function properly and the advisor experience may suffer.  The number of issues that may arise will be a function of the number of users. For example, 50 home office users require less manual maintenance than 10,000 financial advisors to maintain content groups, etc. Please consult with ActiFi Support if considering SSO setup without automated provisioning & hierarchy
TSID (Tenant Specific Identifier)
URLs (for system locations)
Public Certificates that represent trusted identity of each system. 
TSID (required), First Name (optional), Last Name (optional), Email (optional)
No. The SSO process requires TSID to be populated and matched between systems. Without that data point, the SSO will not function. 
This will be located in the metadata xml file after the request is initiated. 
he User action begins in the tenant’s system.
User action begins in SuccessPro?
Yes, ActiFi clients have the option to utilize one or both flows depending on requirements.
SuccessPro may be 1, 2, or 3 in the sample visual below. A user logs in one time to access many applications without being required to log in again and again. 
Yes. Contact support to configure the following settings in your instance of SuccessPro:
Check the boxes in tenant config next to "Enable tenant config: enableManualSSOLogin" and "ssoSPEnabled." Insert the url in the identity provider SSO in ssoIDPLoginUrl. Next to the config in the Auth Section, deselect the checkbox for "manual login: tenant config."