Orchestration SDKs

Compatibility

Supported server versions

The OIDC module is compatible with the following servers:

PingOne

Current version.

PingOne Advanced Identity Cloud

Current version.

PingAM

Currently supported versions.

For information on supported PingAM versions, visit the Ping Identity End of Life (EOL) Software Tracker.

PingFederate

Currently supported versions.

For information on supported PingFederate versions, visit the Ping Identity End of Life (EOL) Software Tracker.

OIDC-spec compliant servers

The OIDC module works with any server that fully implements the relevant OpenID Connect and OAuth 2.0 specifications.

Required specifications
Specification Requirement Notes

OpenID Connect Discovery 1.0 / RFC 8414

Expose a discovery document at /.well-known/openid-configuration, or at a URL the developer configures.

The Orchestration SDKs resolve all endpoint URLs from the discovery document.

OIDC Core 1.0 / RFC 6749

Authorization endpoint, token endpoint, and UserInfo endpoint.

The authorization endpoint must support response_type=code.

The token endpoint must accept public clients that does not use a client secret, and the client_id is in the form body only.

RFC 7636 - PKCE

Must accept code_challenge_method=S256.

PKCE is used by the Orchestration SDKs whenever possible.

RFC 7009 - Token Revocation

Token revocation endpoint advertised in the discovery document.

The Orchestration SDKs revoke tokens on sign-out.

Local token storage is cleared regardless of the server response.

RP-Initiated Logout 1.0

End session endpoint advertised in the discovery document.

The Orchestration SDKs require end_session_endpoint to be present in the discovery document.

Supported operating systems and browsers

Select a platform below to view the supported operating systems and browsers.

  • Android

  • iOS

  • JavaScript / Login Widget

The OIDC module for Android supports the following versions of the Android operating system:

Supported Android versions and original release dates
Release API Levels Released

Android 16

36

August, 2025

Android 15

35

September, 2024

Android 14

34

October, 2023

Android 13

33

March, 2022

Android 12

31, 32

October, 2021

Android 11

30

September, 2020

Android 10

29

September, 2019

We have updated how we determine which Android versions form our support policy for the OIDC module for Android.

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 10 and later versions.

Supported browsers on Android

  • Chrome - Two most recent major versions.

The OIDC module for iOS supports the following versions of the iOS operating system:

Supported iOS versions and original release dates
Release Released

iOS 26

September, 2025

iOS 18

September, 2024

iOS 17

September, 2023

iOS 16

September, 2022

We have updated how we determine which iOS versions form our support policy for the OIDC module for iOS.

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 OIDC module for JavaScript, and the Advanced Identity Cloud/PingAM 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.

JavaScript Compatibility with WebViews

A WebView allows you to embed a web browser into your native Android or iOS application to display HTML pages, and run JavaScript apps.

For example, the Android system WebView is based on the Google Chrome engine, and the iOS WebView is based on the Safari browser engine.

However, it is important to note that WebViews do not implement the full feature set of their respective browsers. For example, some of the browser-provided APIs that the Orchestration SDK for JavaScript requires are not available in a WebView, such as the WebAuthn APIs.

In addition, there are concerns that a WebView does not provide the same level of security as their full browser counterparts.

As the SDK requires full, spec-compliant, browser-supplied APIs for full functionality we do not support usage within a WebView.

We also do not support or test usage with any wrappers around WebViews.

Whilst you might be able to implement simple use-cases using the Orchestration SDK for JavaScript within a WebView, we recommend that you use an alternative such as opening a full browser, or using an in-app instance of a full browser such as Custom Tabs for Android or SFSafariViewController for iOS.