Ping SDKs

New name for the ForgeRock SDKs

What is the new name of the SDKs?

The new name for the ForgeRock SDKs is the Ping SDKs.

Why is the name being changed?

The SDKs are being optimized to support diverse use cases across the entire Ping portfolio. With a unified, modular architecture the Ping SDKs empower developers to seamlessly integrate any service, feature, or functionality into their apps, enabling quick and efficient access to the full range of Ping capabilities.

ForgeRock SDKs now known as the Ping SDKs
Figure 1. ForgeRock SDKs now known as the Ping SDKs

This furthers the commitment of a combined product offering, so you can continue to create the solutions you need. This means continued support for PingOne Advanced Identity Cloud, PingAM, as well as enabling other solutions such as PingOne DaVinci.

What other changes should I be aware of?

The existing ForgeRock Login Widget and ForgeRock Authenticator Module continue to provide support for PingOne Advanced Identity Cloud and PingAM exclusively; however, to align with the new naming conventions as well as to keep the server it supports intuitive, the names are slightly changing:

  • The ForgeRock Login Widget is now the Ping (ForgeRock) Login Widget.

  • The ForgeRock Authenticator Module is now the Ping (ForgeRock) Authenticator module.

The ForgeRock Token Vault is now Token Vault as you can use it with the Ping SDK for JavaScript for any server type, as long as the server is OAuth 2.0/OIDC compliant. This means that the Token Vault, when used in conjunction with the Ping SDK for JavaScript, supports and can be used with PingOne, PingOne Advanced Identity Cloud, or PingAM.