Can I create a client in Okta with a given clientID and clientSecret

Similar to bulk user migration, can we do a bulk client migration to Okta as well. We already have huge number of clients setup with their clientID and clientSecrets.
Now just because we are migrating to Okta we can’t ask all of them to reconfigure these credentials. So similar to the approaches available for user provisioning with password inline hook etc, can we do a client migration as well so the application side don’t have to change their credentials?

So you’ll be creating new applications with your Org org with existing client ids and client secrets from another platform?

You can create applications using our Apps endpoint and when you do, you can set your own client_id and client_secret within the credentials objects. Here’s an example request body for reference

    "name": "oidc_client",
    "label": "Sample Client",
    "signOnMode": "OPENID_CONNECT",
    "credentials": {
      "oauthClient": {
          "client_id": "test_client_id",
          "client_secret": "test_client_secret",
          "token_endpoint_auth_method": "client_secret_post"
      }
    },
    "settings": {
      "oauthClient": {
        "client_uri": "http://localhost:8080",
        "logo_uri": "http://developer.okta.com/assets/images/logo-new.png",
        "redirect_uris": [
          "https://example.com/oauth2/callback",
          "myapp://callback"
        ],
        "response_types": [
          "token",
          "id_token",
          "code"
        ],
        "grant_types": [
          "implicit",
          "authorization_code"
        ],
        "application_type": "native"
      }
    }
}```
1 Like

This is exactly what I was looking for… Thanks a lot.!
I couldn’t capture it from the Apps API documentation…

Have a great day!

1 Like

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.