SP SETUP PROCEDURES FOR FEXA

Effective date: May 26, 2022

These steps depict the general process gone through between Fexa and Fexa’s customers seeking to set up SSO on their site. Application usage and site allocation is customer specific, and we are unable to provide public test accounts. If testing is required for any reason, a meeting can be set up to allow us to demonstrate our SSO process and answer any outstanding questions.

• SSO setup between Fexa and a Fexa customer is generally a two-step process across two one hour meetings. Additional meeting time is provided as needed to resolve any issues. These meetings allow Fexa to provide superb customer support for our SSO setup process and helps minimize setup frustrations for our customers.
  • The first step of the process is an introductory call to gather information and requirements, including:
    • Introduce ourselves and establish points of contact
    • Explain the two-step process for setting up SSO with Fexa
    • Determine the customers IdP of choice
    • Determine if the customer is planning to use Just-In-Time provisioning or is looking to do authentication only
    • If using JIT provisioning, explain our 2-dimensional Permission requirements, where a SAML assertion will need to include a Role and Permission attribute in order to properly assign a user within Fexa
    • Explain that some users will require a third required attribute depending on their Role and Permission
    • Help users determine if this Role/Permission/Identifier information is readily available from users or if they will need to set it up before the final setup process with Fexa
    • Explain that the Customer Advocate assigned to the customer will be able to help them determine what information is needed and that the Customer Advocate will provide them with a spreadsheet containing this information prior to our second meeting
    • Field any remaining questions a customer may have
  • The second step is a call where we go through the setup process with the customer. Typical flow of these sessions include:
    • Walking the customer through the process of adding Fexa from the Integrated App Catalog of their chosen IdP (Azure, OneLogin, Okta)
    • Directing the customer on what specific information is required to finalize the setup on Fexa. Typically this involved the client providing us with an xml file that contains any certificates or URLS required.
    • Once the customer provides us with an xml file from their IdP, the SSO setup on the Fexa side normally takes about 2 minutes.
    • Once the setup is complete, we walk the customer through adding any additional attributes (if required) and help them set up conditional claims for Role/Permission/Identifier attributes is possible
    • Once all attributes are established, we have the user test a login from the IdP and from Fexa to ensure login is successful
    • If users for other Roles/Permission Groups are available, we will have the customer test with those users as well while we are still on the call in order to actively troubleshoot any issues with the customer.
    • Assuming all testing has been successful we end the call and consider
      the SSO setup a success
  • Beyond this two-step process, we provide continued customer support for any issues that they may find as more users begin to use SSO to log in. Usually, any issues customers experience are cleared up within the first week or two of using SSO
    • If needed, we will offer additional calls to help with troubleshooting and will provide support as needed to insure customers are able to successfully log in with their IdP

Note: Occasionally this process will be handled in a singular meeting for SAML savvy customers who are prepared to finish the process quickly. There have also been cases where customers using authentication only have opted for a single meeting, or email instructions for adding Fexa from their IdP’s Integration App Catalog and an email exchange for the required XML file.