Configuring PingIdentity as an Oauth2 provider – Support | JetBrains

You will need a new application with OIDC Web App type:

2. You need to enable the app after creation (toggle button in the top-right corner) and click on the Protocol tile to show advanced settings:

3. You need to add at least the refresh token, fill in the redirect URL and change the Token Authentication Method to be Client Secret Post

4. You can also click on the Resource Access tile to configure additional scopes. You need to add email and profile (for user name). The email scope is required. The profile scope is optional, but if it's missing, then users will get their subject as the username (their username will be a UUID).

5. application.yaml listed above is a little superfluous; you don't need to change login-url-prompt-param, jws-algorithms, and required-scopes params, it's not wrong though.

6. In the application.yaml the parameters map as such:

Authorization URL (PingIdentity) - login-url
Token Endpoint (PingIdentity) - token-url
JWKS Endpoint (PingIdentity) - jwt-certs-url

application.yaml:

auth:
    client-id: "a1b2c3d4-e5f6-7890-gh12-ijklmnopqrst"
    client-secret: "xYz12345~AbCdEfGhIjKlMnOpQrStUvWxYz0987654321abcdefgh"
    required-scopes: [ 'profile', 'email', 'openid' ]
    login-url-prompt-param: "login"
    root-admin-emails:
      - 'nikolai.maltsev@jetbrains.com'
    login-url: "https://auth.pingone.eu/dee2c369-5e34-47d8-93ff-58b3aa069d4c/as/authorize"
    token-url: "https://auth.pingone.eu/dee2c369-5e34-47d8-93ff-58b3aa069d4c/as/token"
    jwt-certs-url: "https://auth.pingone.eu/dee2c369-5e34-47d8-93ff-58b3aa069d4c/as/jwks"
    jws-algorithms: [ 'RS256', 'RS384', 'RS512', 'ES256', 'ES512' ]

IDP configuration: