Are you trying to update an OpenID connect app that already exists in your org?
When you formed your request payload for this update, did you ensure that it included all the details specific to this application based on what was returned in a GET request for the same application instance?
Yes, it’s an existing OIDC app in my org, I can update it from UI but not via Okta APIs.
yes, I also tried fetching it’s details with GET API and sent the same values in PUT API just to check if it accepts… but it fails with PUT API
So we can better update our documentation (and help anyone else who runs into this issue), were you able to determine which specific attributes were missing?
Worked with this Input JSON for OIDC app, it fails with some or the other required field error if any of the below mentioned attribute is not passed
{
“name”: “oidc_client”,
“label”: “AUTOMATION- QA034 BASIC”,
“signOnMode”: “OPENID_CONNECT”,
“credentials”: {
“oauthClient”: {
“client_id”: “0oalxtp4bnLsQbduI5d7”,
“token_endpoint_auth_method”: “client_secret_basic”
}
},
“settings”: {
“oauthClient”: {
“redirect_uris”: [
“https://test.tst.com/oauth2/code/U0NfQVBBQzFfVE5CLVFBMDM0LWRlc2t0MDAwMDAwMDAwMDAyODg1”
],
“post_logout_redirect_uris”: [
“https://test.tst.com”
],
“response_types”: [
“code”
],
“grant_types”: [
“authorization_code”,
“client_credentials”
],
“application_type”: “web”,
“consent_method”: “REQUIRED”,
“issuer_mode”: “DYNAMIC”
}
}
}