/
TID-W SSO configuration

TID-W SSO configuration



Description of Issue

We use SAML Single Sign On (SSO) for our logins and Hub is not seemingly SSO



Context
  • Okta

  • TID-W

  • TID-C

  • SSO

  • EERP



Cause

Users are used to logging into their workstations, then launching Munis without having to re-enter their credentials



Resolution

Sign into Hub first and then navigate to other Tyler products without logging in again



Additional Information

Some SAML configurations can allow a 'feel' of SSO, but Tyler does not support configuring this











Related content

Non-Supported Identity Provider Federation Request
Non-Supported Identity Provider Federation Request
More like this
Single Munis user unable to log in or unable to see the Tyler Menu
Single Munis user unable to log in or unable to see the Tyler Menu
More like this
TID-W account requirements to log into Munis products
TID-W account requirements to log into Munis products
More like this
TID-W Advanced Tier - End user MFA setup
TID-W Advanced Tier - End user MFA setup
More like this
Request to federate TID-C for single sign on
Request to federate TID-C for single sign on
More like this
Tyler Hub Redirects To Original IDP After Second IDP Is Federated In Okta Tenant
Tyler Hub Redirects To Original IDP After Second IDP Is Federated In Okta Tenant
More like this