PingOne Platform APIs

Configuration options

The following topics provide information about the platform’s advanced configuration options in authorize and token requests.

  • Redirect and non-redirect authentication flows

    Describes the authorize request’s response_mode options, which include the query, fragment, and form_post options for redirecting back to the client. It also describes how to use the PingOne pi.flow custom response option for non-redirect flows, returning response parameters encoded as a JSON object directly to the client.

  • Create a login_hint_token JWT

    Describes the claims required by the login hint token, and how to sign the JWT using an application’s client secret as the signing key.

  • Create a request property JWT

    Describes the claims required by the request property token, and how to sign the JWT using either the application’s client secret or a private key as the signing key.

  • Create a client secret JWT

    Describes the claims required by a JWT used to authenticate the PingOne /token request, and how to sign the JWT using an application’s client secret as the signing key.

  • Create a private key JWT

    Describes the claims required by a JWT used to authenticate the PingOne /token request, and how to sign the JWT using a private key as the signing key.

  • Create a private_key_jwt JWKS string

    Describes how to configure a JWKS string (or JWKS URL) to add to an application configuration to enable the use of a private key JWT as the authentication method for a PingOne /token request.

  • Use an authentication JWT for token fulfillment

    Describes how to map attributes from a source’s authentication JWT to the PingOne generated token.