Table of Contents

June, 2017

Table 1: Enhancements
PingOne universal certificateA new PingOne universal certificate is now available. You need to update to the new PingOne universal certificate if you're using either PingFederate or a Third-Party SAML provider as your identity bridge and your configuration requires either:
  • Signed AuthN requests.
  • SAML single logout (SLO), either IdP-initiated or SP-initiated.
NoteYou don't need to update the PingOne universal certificate if you're using an identity repository other than PingFederate or Third-Party SAML.
See Update the PingOne universal certificate for more instructions.
PingOne encryption certificateWe now include the PingOne encryption certificate in the PingOne metadata available when you're configuring a PingFederate or Third-Party SAML identity bridge. We've also added the option to separately download the PingOne encryption certificate if you intend to manually configure the IdP settings (rather than using the PingOne metadata).
Custom entity IDsWhen configuring a PingFederate or Third-Party SAML identity bridge, you can now select to enable account-specific entity IDs and specify a custom entity ID for your account. We'll validate the ID to ensure that it's unique across all PingOne accounts.
Table 2: Resolved issues
Ticket IDIssue
SSD-4485Fixed an issue where selecting to use the PingOne universal certificate for a Third-Party SAML identity bridge configuration, then changing to use the PingOne directory as the identity repository, caused the Renewal Certificate to be selected for use rather than the PingOne universal certificate.
SSD-4450Fixed an issue that resulted in configuration updates not being used during SSO.
SSD-4298Fixed an issue where the Upload link was being displayed on top of the company logo icon when registering for a new account.
SSD-3721Fixed an issue on the My Devices page where pressing the Enter key did not correspond to clicking the Save button.

Tags Capability > Single Sign On; Product > PingOne

Your Rating: