← Support

Supporting SSO

What is SSO?

Single sign-on (SSO) is a third-party (internal or external) integration that auto authenticates users into a service outside of Banno using a common identifier as outlined in the vendor’s API Specifications. These are currently configured in Banno People using the SSO configuration tool by both Operations and the IS Custom Dev/Tech team. All Banno third-party SSO requests require a contract.

A popular and well-known example of SSO occurs when a user signs in to Google’s Gmail. After signing in, the user gains immediate access to applications such as YouTube and Hangouts without needing to enter their login credentials again.

Install & support

The Operations team owns the install and support of the following internal SSO:

  • iPay
  • SymApp
  • Geezeo
  • Cash Management (Netteller)
  • ESI
  • Open Anywhere
  • Payments for JHA FSCC
  • Xperience

If the FI requests a link be added and it is similar to one of the SSOs above, and the link type is not currently being used, like an unauthenticated link to a different account opening service, then it should be sent to Tier 2. If it is NOT related, then it should be sent to IS Custom Dev/Tech (ID: IS_ITCUSTM), or should be added to the FI’s general information if we do not have a link type that would appropriately map to what they are requesting. If we DO have a link type for what they are requesting, but that link type is supported by IS Custom, send it on over to them! If the case is discussing new development of a feature or SSO, please change the case type to a CWR.

Request for SSOs installed by Tier 2

If a FI requests install of internal SSO on the list above, transfer the case to Banno Tier 2 Support. Cases should not be sent to the IS team for support or install.

  • If the case is a request for install, please make sure it’s in the Case Type of Implementation and the Subject of the case is renamed to indicate it’s a request for install of an SSO with a Case Status of Open - Transfer.
    • Ex. SSO Request: Open Anywhere

Troubleshoot external SSO

If the FI has issues with a previously installed SSO that isn’t supported by Operations, the case will be transferred to the Provider Group: IS Custom Dev/Tech team (ID: IS_ITCUSTM) to troubleshoot with the customer/vendor. In the transfer, please include an internal note specifying that this is a support request and write the name of the SSO they’re requiring assistance on.

If the issue is with one of the SSO’s listed out above, the case would stay with our Tier 1 support team and a Jira would be opened for the Prism team to review further.

If we get an urgent case after hours (AH) for an issue with an SSO you can transfer the case to the Provider Group: IS Custom Dev/Tech team (ID: IS_ITCUSTM) and they will handle from there. This queue is monitored and they are working with the Call Center to build out further process for After Hours procedures.