Setting createaccountifnotexists:true for /createrequest API is not creating new account task

[KT]

Hi,

We are using /createrequest API to request entitlements for users already having account to the endpoint where requesttype is set as "ADD" in the API payload as shown in the below example.

This is working as per the expectation, and it is creating a new request and subsequent add access tasks are created.

When the similar request is raised for user who does not already have an account to the endpoint, then it is not creating the task for new account, but it creates tasks for just for add access which does not get processed as there is no parent task created.

We believe that the attribute "createaccountifnotexists":"true" is used for this scenario, which we have used in the payload, but it is not giving us the expected results.

Are we missing something here? Please let us know if we need to make any changes in the payload to achieve this use case.

Example of request payload:

{

"requesttype":"ADD",

"username":"UA99820",

"endpoint":"AD - Secure - EMSDomain - Test",

"securitysystem":"ActiveDirectory - Secure - EMSDomain - Test",

"accountnamefromrule":"true",

"createaccountifnotexists":"true",

"accountid":"1234566",

"entitlement":[

    {"entitlementtype":"memberOf","entitlementvalue":"PG100-GH3H34ESU5D","startdate":"25-05-2023","enddate":"12-05-2024","businessjustification":"test business justification" }

]

}

Thanks

[dgandhi]

Can you change request type to NEW and try? Also what is the error that you get when you use your payload?

{
"requesttype":"NEW",
"username":"usngom",
"endpoint":"amigopod",
"securitysystem":"amigopod",
"comments":"add comment",
"accountname":"usngom3",
"requestor":"gbana5",
"dynamicattr": {
"parent":"TEST1",
"child":"TEST2"
},
"entitlement":[
{"entitlementtype":"Access","entitlementvalue":"Absence Partner","startdate":"10-11-2018","enddate":"12-05-2018"},
{"entitlementtype":"Access","entitlementvalue":"Absence Administrator"}
],
"checksod":"true"
}

[KT]

Hi Devang,

Thanks for the response.

I have tried the API with request type set to new.

The issue with using 2 different request types is that it will be an additional overhead to check if the user already has an account to the endpoint or not and based on that decide whether to set request type as ADD/NEW.

We would like to avoid this additional overhead by using only ADD as the request type and set the attribute "createaccountifnotexists":"true". 

I am not getting any error for this payload, it is returning success response, it's just that it is not working as expected for users not having the account already provisioned to the endpoint as explained above.

Restating the line from above which explains this use case.

"When the similar request is raised for user who does not already have an account to the endpoint, then it is not creating the task for new account, but it creates tasks for just for add access which does not get processed as there is no parent task created."

[rushikeshvartak]

What is create task action set under Security System

[KT]

Create task action under security system is blank.

[rushikeshvartak]

Ideally it should be managed inside code itself please raise enhancement request

[ShyamSrisailam]

Hi @KT,

Did your issue got resolved, we are also seeing the same issue. It's not creating the task for New Account but it's creating Add Access but not processing as it doesn't have any parent task.

If you got any solution. Let me know, what is the reason?

Thanks,

Shyam

[rushikeshvartak]

This is working in v23.6

[ShyamSrisailam]

Hi @rushikeshvartak,

The New Account task is creating for all the apps except for one app and why is that. Does there might be any other reason ? I checked the above-mentioned posts also but still the issue is same.

[rushikeshvartak]

Its configuration issue