Hello, I’ve recently been exploring some automation around app creation. Which led me to discover the inability to add an access profile to a newly created app/source? I’ve tested this in our prod environment, and I get the below
I’ve also tried directly patching the app with new source app api endpoint in v2024.
{
"detailCode": "404 Not found",
"trackingId": "8c0728026169415db3508e045f8b68a5",
"messages": [
{
"locale": "und",
"localeOrigin": "REQUEST",
"text": "The server did not find a current representation for the target resource."
},
{
"locale": "en-US",
"localeOrigin": "DEFAULT",
"text": "The server did not find a current representation for the target resource."
}
],
"causes": []
}
I can lookup the app by ID just fine with the v2024 endpoint as well. so it exists.
{
"cloudAppId": "19626",
"description": ".",
"enabled": false,
"provisionRequestEnabled": false,
"accountSource": {
"useForPasswordManagement": false,
"passwordPolicies": null,
"type": "SOURCE",
"id": "9948e85d7c3245b38fcdbf040b3105c6",
"name": "FIS ImageCentre (APP-1447)"
},
"matchAllAccounts": true,
"owner": {
"type": "IDENTITY",
"id": "2c918084749df3b60174b6ce23bc71e0",
"name": "Nicholas Danjou"
},
"appCenterEnabled": true,
"id": "738b10d0d0764d10bc7e1e3f80b7acac",
"name": "FIS ImageCentre (APP-1447)",
"created": "2024-10-16T16:11:21.928Z",
"modified": "2024-10-16T16:11:22.916Z"
}
The same issue doesn’t occur in our staging instance however. I can create and instantly add an access profile.
is there some sort of processing that needs to happen? The source and access profiles are newly created too - but it lets me add them to the app in the GUI. so i’m not sure if i am missing something or this is a bug. The fact I can look it up by GET call but get a 404 not found on a valid patch call leads me to think something isn’t right.