PingFederate Deprecation Notice for Agility SSO

Overview

At Digital.ai we are committed to providing you the best and most secure user experience possible. As part of this commitment, we are making changes to how user authentication is performed. We will deprecate and remove all support for the PingFederate enterprise federation server for user authentication and single sign-on (SSO) on October 31, 2024.

Agility On-Demand customers leveraging single-sign-on authentication will be required to migrate to Digital.ai (DAI) Identity (within the DAI Platform) by or before October 31, 2024. For more information, see our FAQs section below.

If you have any questions that are not addressed here, contact us at support@digital.ai so that we can assist you further.

FAQs

1. Does this impact Digital.ai products or services other than Agility On-Demand (“Agility Hosted”)?
   • No, this deprecation of PingFederate does not currently impact any other products or services.
2. Does this impact other authentication methods (e.g., Agility Authentication, Windows Integrated Authentication, On-Premise Single Sign-On Authentication, Integration Authentication via the Agility API)?
   • No, only On-Demand (“Agility Hosted”) Single Sign-On Authentication will be impacted by this change.
3. What benefits can I obtain using Digital.ai Identity as an identity broker?
   • DAI Identity allows users to seamlessly log into multiple Digital.ai applications and resources (e.g., Community, Documentation, and Support) with a single username and password credential.
   • Support for Single Log Out (SLO) to simultaneously log out of all Digital.ai products, services, and resources.
   • Support for OpenID Connect (OIDC) for SSO implementation in addition to Security Assertion Markup Language (SAML) as currently provided.
   • Control of managing and maintaining your own SSO solution for DAI products and services, including updates to your Identity Provider information and changes, SSO signing certificate renewal, etc. within the DAI Platform and without the need to involve DAI Support.
   • Control of Access Token lifetime and Client session settings within each Digital.ai application configuration of the DAI Platform.
4. What will happen if I don’t perform the required action to migrate to Digital.ai Identity as an identity broker before October 31, 2024?
   • Access to your current Digital.ai product and service subscriptions will be impacted if you don’t perform this required action.
5. How do I learn more about Digital.ai Identity and how to migrate to Digital.ai Identity as an identity broker?
   • Review the Digital.ai Platform Getting Started documentation page which includes a link to the Digital.ai Account Administrator Handbook for information about performing this update.