Below are the standards that Ping Identity is actively contributing to, participating in, and following.
OpenID for Verifiable Credential Issuance (OpenID4 VCI)
Defines an API for the issuance of a Verifiable Credential in W3C and ISO formats. This format uses OAuth 2.0, meaning existing apps deployed using OAuth 2.0 and OpenID Connect OPs can be extended to become credential issuers.
OpenID for Verifiable Presentations (OpenID4VP)
Defines a transport protocol on top of OAuth 2.0 for users to present digital credentials from their wallet to a verifier. Enables the verifier to request a specific type of credential. This allows secure direct presentation of the credential.
W3C Verifiable Credentials with JSON Web Token proof format (JWT-VC)
Defines a standard way to express credentials on the Web in a way that is cryptographically secure, privacy respecting, and machine-verifiable, using the JSON Web Token proof format.
ISO 18013-5 for Mobile Driving License (mDL)
Focuses on “attended” mDL presentation, meaning the End-User presents the mDL to the relying party in-person, but using their mobile driving license. This standard covers several transport protocols including QR, NFC, BLE, and WiFi Aware.
ISO 18013-7 for Mobile Driving Licenses (mDL)
This is the “unattended” mDL presentation, where the End-User can present mDL to the relying party remotely (i.e: over the Internet). It is important to note this standard is still in development, and as such has yet to be published.
Your Digital Wallet
Once credentials are issued to users, they are stored in a digital wallet, such as:
Device native wallet, such as Samsung, Google or Apple
Easy administration and configuration of identity verification and digital credentials. Orchestration and execution can also be achieved using the RESTful API.
Neo easily plugs into new and existing deployments of PingFederate enabling the verification of the user’s identity by matching a person’s selfie against their authenticated government ID during user registration or subsequent user authentication. Admins can require any group of users to verify. New users can be verified and auto-registered.
Neo uses the world's most robust directory to manage devices and push notifications. The directory can be configured to store credential records.
View all integrations with third-party solutions on our Integration Directory.