With PingFederate, we have released to our download site version 7.1. This release has some exciting new features, as well as, enhancements to some existing ones that I think you will like.
The first key feature in PingFederate 7.1 is a significant enhancement to our user provisioning solution with outbound provisioning via our PingOne cloud service. We have extended support for the System for Cross-Domain Identity Management (SCIM) to work in conjunction with specific versions of PingOne.
The outbound provisioning service has been enhanced to support the provisioning of users and groups through PingOne to a host of service provider applications. This deployment model greatly simplifies the PingFederate setup by eliminating the need to install and configure SaaS application-specific provisioning drivers.
In addition, we have enhanced our user provisioning offering with an identity store SDK for inbound provisioning and a new plug-in type. The new SDK and plug-in type, called an Identity Store Provisioner, enables customers to target additional user stores, beyond Active Directory. This means IT departments, service providers and SaaS companies can leverage PingFederate to enable SCIM-based provisioning from and to any type of identity store, such as LDAP directories and databases.
Another exciting new feature is RADIUS authentication support. PingFederate now allows integration with any authentication system that supports the RADIUS protocol, which extends PingFederate's support to virtually any strong authentication vendor and device. The new features are aimed at supporting administrators and end-users with mobile devices as these users work with both one-step and two-step challenge/response authentication methods, and support a wide range of third-party strong authentication solutions.
In addition, authentication to the PingFederate administration console has been extended to support RADIUS authentication. So, now, administrative access can be managed through existing authentication-management systems that support the RADIUS protocol.
The last highlighted feature greatly improves administration of your growing connection configurations. PingFederate now allows you to use an adapter configuration, as well as certain plug-in configurations, as a "parent" instance, which can then be used as a template for creating "child" instances. Following creation of a child instance, you can modify the inherited configuration as needed. This feature provides easier management of adapter settings in cases where only small changes to an existing plug-in configuration need to be made for a particular use case.
Lastly, we continue to actively maintain PingFederate as we work with existing and new customers by providing 80+ enhancements and fixes to ensure the high-quality and performance you have come to expect. Nevertheless, our view of the future is always made clearer by feedback from our many customers and identity experts we work with. We appreciate the feedback and hope you keep it coming.