Custom Identity Provider (IdP) FAQs

No. Our custom IdP integrations mean your identity management strategy will scale as your software stack and reliance on enterprise cloud-based solutions grows and changes as well. You can trust that you are always benefitting from our most advanced and secure solutions with no upgrades or add-ons required. 

Please contact your Client Success Manager for more pricing information.

For Azure AD:

• Azure Active Directory: Any edition. Our integration will work with the free, basic, or premium editions.
• CivicPlus does not support the setup of an Azure Active Directory (Azure AD)
• Users must have an Active Directory email with an organizationally unique domain (eg: user@city.com). Non-organizationally unique emails (eg: user@gmail.com) can be used for logging on to CivicPlus Single Sign-On (SSO) but cannot be integrated with Azure AD log-on to CivicPlus SSO.

For Active Directory Federation Service (ADFS) 5.0: 

• ADFS 5.0 is the version that comes with Windows Server 2016. Please view Microsoft Requirements.
• CivicPlus does not support the setup of an ADFS or implementation of any ADFS requirements.
• To ensure ADFS log-out works, you must have the KB4038801 installed because CivicPlus uses frontchannel_logout, which only works after installation of this update, per Microsoft's documentation.
• Users must have an Active Directory email with an organizationally unique domain (eg: user@city.com). Non-organizationally unique emails (eg: user@gmail.com) can be used for log-on to the CivicPlus SSO but cannot be integrated with ADFS log-on to CivicPlus SSO.

• Run the following PowerShell command on your ADFS server:

  Set-AdfsResponseHeaders -RemoveHeaders "x-content-type-options"

For ADFS 4.0:

• ADFS 4.0 is the version that comes with Windows Server 2016. Please view Microsoft Requirements.
• CivicPlus does not support the setup of an ADFS or implementation of any ADFS requirements.
• To ensure ADFS log-out works, you must have the KB4038801 installed because CivicPlus uses frontchannel_logout, which only works after installation of this update, per Microsoft's documentation.
• Users must have an Active Directory email with an organizationally unique domain (eg: user@city.com). Non-organizationally unique emails (eg: user@gmail.com) can be used for log-on to CivicPlus SSO but cannot be integrated with ADFS log-on to CivicPlus SSO.

For Okta:

• Okta Single Sign-On (SSO), with the option to create an OpenID Connect Application
  • View the Okta SSO resource for more information.
• CivicPlus does not support the setup of an Okta account or implementation of any Okta requirements.
• Users must have an email address with an organizationally unique domain (eg: user@city.com). Non-organizationally unique emails (eg: user@gmail.com) can be used for log-on to CivicPlus SSO but cannot be integrated with Okta log-on to CivicPlus SSO.

For ADFS 3.0: 

• ADFS 3.0 is the version that comes with Windows Server 2012. Please view Microsoft's Requirements.
• CivicPlus does not support the setup of an ADFS or implementation of any ADFS requirements.
• Users must have an Active Directory email with an organizationally unique domain (eg: user@city.com). Non-organizationally unique emails (eg: user@gmail.com) can be used for log-on to CivicPlus SSO but cannot be integrated with ADFS log-on to CivicPlus SSO.

Contact Support or your Client Success Manager for more information.