PingOne SSO for SaaS Applications now provides administrators better visibility into their customers’ SSO transactional activity with new summary reports and the ability to filter transactional SSO events by customer tenant or application name.

PingOne for Enterprise eases administration with improved OIDC support. When the default OIDC scopes and claims are insufficient, admins can now define custom scopes and attributes for their apps.

We are pleased to announce PingOne for Customers, an Identity as a Service offering built for developers, that provides API-based identity services for customer-facing apps. It helps large enterprises launch apps faster, replace custom identity services that are difficult to maintain, and facilitate the transition from on-premises deployments to cloud-hosted services.

PingOne for Enterprise eases administration with improved OIDC support. When the default OIDC scopes and claims are insufficient, admins can now define custom scopes and claims (attributes) for their apps.

PingOne for Enterprise (P14E) administrators can now specify optional parameters for the authentication request PingOne sends to an OpenID Provider. Admins can streamline session management and configuration now that the P14E dock shares the same session lifetime as the PingOne SSO session, which can be set to as low as 15 minutes. We also added Turkish language support to the end-user interface.

PingOne for Enterprise introduces significant features to ease administration and improve user experience. The latest release expands the administrative auditing features to now support both partner and PingID use cases, in addition to workforce. We improved administrative ease of use of PingOne as an OIDC relying party by changing the way user attributes are mapped and updating the OIDC application wizard and summary screen. Also, PingOne for Enterprise now provides a more convenient, secure user experience by supporting OIDC Identity Provider single logout (SLO).

The new PingOne GitHub and Lucid Chart Connectors enable enterprises to set up SSO and reduce administrative efforts by offering quick connection templates for provisioning users and groups.

PingOne for Enterprise now supports the OpenID Connect (OIDC) protocol for application integration via code, implicit and hybrid flows. With this integration, OIDC standard-based applications are now treated identically to SAML applications and can be made available on the PingOne dock and selectable in access and authentication policies.

For added security, PingOne for Enterprise adds an option when configuring SAML applications to enable encryption of the SAML response sent from PingOne to the service providers.

From the PingOne admin portal, PingOne for Enterprise administrators now can access and manage their subscriptions for audit streaming, which increases administrator visibility into transactional audit events.

PingOne for Enterprise administrators can now select from two subscription options to receive audit events surrounding end users and their respective authentication events. “Push” subscriptions allow audit events to be continuously streamed to an external service such as Splunk. “Poll” subscriptions allow clients to retrieve event data through an API on an as-needed basis in configurable blocks of records.

If you have an authentication policy in place for your PingOne account, when you add an application to PingOne, you now have the option to require that each time a user accesses the application, they must use multi-factor authentication (MFA).

When you add an application to PingOne for Enterprise and use advanced attribute mapping to map your identity provider attributes to service provider attributes, you'll now find settings for random and hash functions. The hash function takes a literal string or attribute value. The random function generates a random string of a specified length. Both functions optionally hash the string using the selected algorithm (MD5, SHA-1, SHA-256) and encode the string using the selected encoder (hex, base64).

PingOne for Enterprise administrators can now authenticate end users through OpenID Connect identity repositories. In addition, PingOne SSO for SaaS Apps administrators can now manage partner identity repositories, provide access to applications from a private catalog, enable access to a partner PingOne dock and apply MFA policies to sensitive applications.

PingOne for Enterprise's identity bridge to Active Directory, AD Connect 4.0.1, now supports non-string data types sent during single sign-on.

PingOne for Enterprise now supports additional user attributes within the Workplace by FacebookTM provisioner. In order to take advantage of the new provisioner features, you will need to edit the SaaS provisioning connector.

For more information, see the PingFederate Workplace by Facebook Connector Guide 1.7.

For product updates prior to 2018, please use the button below. 

With OAuth client access now supported, PingOne for Enterprise admins can provide security teams with greater visibility into event data without adding additional admins. Dedicated OAuth clients can be created to retrieve subscription events such as actions, resources, clients and authentication results from the PingOne for Enterprise reporting API.