JamesN.83470 (Customer) asked a question.
I'm attempting to update a single application's sign-on variable using the Okta API. I'm using Powershell\Invoke-RestMethod to PUT the proper value into a given application. I know that typically a 400 error means that something is wrong with the JSON body, but I can't see any problems and running it through a JSON validator doesn't yield any issues. What am I missing?
Sample of the JSON i'm sending:
{
"visibility": {
"autoSubmitToolbar": false,
"hide": {
"iOS": false,
"web": false
},
"appLinks": {
"testappdeletesoon_1_link": true
}
},
"features": [
],
"signOnMode": "SAML_2_0",
"credentials": {
"userNameTemplate": {
"template": "user.email",
"type": "CUSTOM",
"pushStatus": "PUSH"
},
"signing": {
"kid": "removed for security"
}
},
"settings": {
"app": {
},
"notifications": {
"vpn": "@{network=; message=; helpUrl=}"
},
"signOn": {
"defaultRelayState": "",
"ssoAcsUrl": "https://blah.lblah",
"idpIssuer": "http://www.okta.com/${org.externalKey}",
"audience": "Blah",
"recipient": "https://blah.lblah",
"destination": "https://blah.lblah",
"subjectNameIdTemplate": "${user.userName}",
"subjectNameIdFormat": "urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified",
"responseSigned": true,
"assertionSigned": true,
"signatureAlgorithm": "RSA_SHA256",
"digestAlgorithm": "SHA256",
"honorForceAuthn": true,
"authnContextClassRef": "urn:oasis:names:tc:SAML:2.0:ac:classes:PasswordProtectedTransport",
"spIssuer": null,
"requestCompressed": false,
"attributeStatements": "",
"inlineHooks": "",
"allowMultipleAcsEndpoints": false,
"acsEndpoints": "",
"samlSignedRequestEnabled": false,
"slo": "@{enabled=False}"
}
}
}
Hi James,
I would suggest for you to open support ticket with our support team to review the details of the configuration in order to provide the next step to resolve this issue.
Thank You.