Changelog
The following is the change history for the PingOne Verify Integration Kit.
PingOne Verify Integration Kit 1.1 – July 2021
Added support for changes to PingOne Verify, including:
-
The adapter now gets the user’s
verifyEnabledStateattribute when getting the verification result -
Updated the list of core contract attributes to support changes to the structure of the
verifiedUserDataattribute -
Added support for change to the flow behavior when the
verifyDocumentflag is off -
Updated the core contract to support changes in PingOne Verify:
Change description Version 1.0 Version 1.1 Attribute name change
verificationStatustransactionStatusAttribute name change
dateOfBirthbirthDateAttribute name change/merge
addressLine1addressStreetAttribute name change/merge
addressLine2Attribute name change
cityaddressCityAttribute name change
stateaddressStateAttribute name change
postalCodeaddressZipAttribute name change
documentIdidNumberNew attribute
idType
|
For upgrade instructions, see Deploying the integration files. |
PingOne Verify Integration Kit 1.0 – January 2021
-
Initial release.
-
Added the ability to direct users to an identity verification app as part of a sign-on or registration flow.
-
Added the ability to control which message pages (templates) are shown to the user.
-
Added the ability to customize template messages using a language pack file.
-
Added the ability to test the connection to PingOne Verify.
-
Added a setting to automatically provision new users to PingOne.
-
Added settings to control how the adapter handles sign-on and registration attempts when errors occur.
-
Added support for the platform connection to PingOne introduced in PingFederate 10.2.
-
Added support for the PingFederate authentication API
-
Added support for the JavaScript Widget for the PingFederate Authentication API.
-
Added settings for API connection and request timeouts.
-
Added settings to override the PingFederate system-default proxy settings.