Compatibility
Supported versions
The Ping SDKs support the following server versions:
-
PingOne
-
PingOne Advanced Identity Cloud
-
PingAM 6.5, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5 and later
-
PingFederate
Supported operating systems and browsers
Select a platform below to view the supported operating systems and browsers.
-
Android
-
iOS
-
JavaScript / Login Widget
The Ping SDK for Android supports the following versions of the Android operating system:
-
Android 6.0 (Marshmallow)
-
Android 7.0 / 7.1 (Nougat)
-
Android 8.0.0 / 8.1.0 (Oreo)
-
Android 9 (Pie)
-
Android 10
-
Android 11
-
Android 12
-
Android 13
-
Android 14
-
Android 15
We are updating how we determine which Android versions form our support policy for the Ping SDK for Android.
From March 1st, 2025, the support policy is as follows:
-
Every public major release of Android within the last 6 years.
For example, this would mean support for Android 9 (API level 28) and later versions.
-
Supported browsers on Android
-
Chrome - Two most recent major versions.
The Ping SDK for iOS supports the following versions of the iOS operating system:
-
iOS 12
-
iOS 13
-
iOS 14
-
iOS 15
-
iOS 16
-
iOS 17
-
iOS 18
We are updating how we determine which iOS versions form our support policy for the Ping SDK for iOS.
From March 1st, 2025, the support policy is as follows:
-
Every public major release of iOS within the last 3 years.
For example, this would mean support for iOS 16 and later versions.
-
Supported browsers on iOS
-
Safari - Two most recent major versions.
The Ping SDK for JavaScript, and the Ping (ForgeRock) Login Widget support the desktop and mobile browsers listed below.
Minimum supported Desktop browser versions
-
Chrome 83
-
Firefox 77
-
Safari 13
-
Microsoft Edge 83 (Chromium)
Supported Mobile browsers
-
iOS (Safari) - Two most recent major versions of the operating system.
-
Android (Chrome) - Two most recent major versions of the operating system.
Supported authentication journey callbacks
Callback name | Callback description | Android | iOS | JavaScript |
---|---|---|---|---|
|
Collects a generated token from the client to verify the integrity of the app |
✅ SDK 4.3 |
✅ SDK 4.3 |
❌ |
SDK 2.1 |
Collects true or false. |
✅ |
✅ |
✅ |
|
Collects single user input from available choices, retrieves selected choice from user interaction. |
✅ |
✅ |
✅ |
|
Retrieve a selected option from a list of options. |
✅ |
✅ |
✅ |
SDK 2.0 |
Prompts the user to consent to share their profile data. |
✅ |
❌ |
❌ |
|
Cryptographically bind a mobile device to a user account. |
✅ SDK 4.0 |
✅ SDK 4.0 |
❌ |
SDK 2.0 |
Collects meta and/or location data about the authenticating device. |
✅ |
✅ |
✅ |
|
Verify ownership of a bound device by signing a challenge. |
✅ SDK 4.0 |
✅ SDK 4.0 |
❌ |
|
Returns form values that are not visually rendered to the end user. |
✅ |
✅ |
✅ |
|
Collects knowledge-based answers. For example, the name of your first pet. |
✅ |
✅ |
✅ |
|
Injects key-value metadata into the authentication process. For example, the WebAuthn nodes use this callback to return the data the SDK requires to perform authentication and registration. |
✅ |
✅ |
✅ |
|
Collects a username. |
✅ |
✅ |
✅ |
SDK 2.1 |
Collects a number. |
✅ |
✅ |
✅ |
|
Collects a password or one-time pass code. |
✅ |
✅ |
✅ |
SDK 4.4 |
Collects captured contextual data from the client to perform risk evaluations. |
✅ |
✅ |
✅ |
SDK 4.4 |
Instructs the client to start capturing contextual data for risk evaluations |
✅ |
✅ |
✅ |
|
Instructs the client to wait for the given period and resubmit the request. |
✅ |
✅ |
✅ |
|
Provides data required to use a CAPTCHA in your apps. |
✅ (2) |
✅ |
✅ |
|
Provides data required to use reCAPTCHA Enterprise in your apps. |
✅ (2) SDK 4.6 |
✅ SDK 4.6 |
✅ SDK 4.6 |
|
Redirects the user’s browser or user-agent. |
❌ |
❌ |
✅ |
SDK 2.0 |
Collects the values of attributes for use elsewhere in a tree. |
✅ |
✅ |
✅ |
SDK 2.1 |
Pause and resume authentication, sometimes known as "magic links". |
✅ |
✅ |
✅ |
|
Collects text input from the end user. For example, a nickname for their account. |
✅ SDK 4.4 |
✅ SDK 4.4 |
✅ SDK 3.4 |
|
Provides a message to be displayed to a user with a given message type. |
✅ |
✅ |
✅ |
SDK 2.0 |
Collects a user’s acceptance of the configured Terms & Conditions. |
✅ |
✅ |
✅ |
SDK 2.0 |
Collects a password value with optional password policy validation. |
✅ |
✅ |
✅ |
SDK 2.0 |
Collects a username value with optional username policy validation. |
✅ |
✅ |
✅ |
(1) The WebAuthn Authentication node and the WebAuthn Registration node both use a MetaDataCallback
when the Return challenge as JavaScript is NOT enabled.
You must not enable this option when handling WebAuthn journeys with the Ping SDK for Android and iOS.
The Ping SDK for JavaScript handles either the MetaDataCallback
or the JavaScript-based payload.
(2) Requires the presence of Google Play Services.
Supported DaVinci fields and collectors
The DaVinci client currently only supports the UI-related HTTP Connector - Custom HTML capability. |
Field | Collector | Description | Android | iOS | JavaScript |
---|---|---|---|---|---|
Text field |
|
Collects a single text string. |
✅ 1.0.0 |
✅ 1.0.0 |
✅ 1.0.0 |
Password field |
|
Collects a single text string that cannot be read from the screen. |
✅ 1.0.0 |
✅ 1.0.0 |
✅ 1.0.0 |
Submit Button |
|
Sends the collected data to PingOne to continue the DaVinci flow. |
✅ 1.0.0 |
✅ 1.0.0 |
✅ 1.0.0 |
Flow Button |
|
Triggers an alternative flow without sending the data collected so far to PingOne. |
✅ 1.0.0 |
✅ 1.0.0 |
✅ 1.0.0 |