I think the “Create Account With Ent Request” is conflicting with the “addRemoveEntInSingleReq” option, because I’m using this functionality with a different system.
This would be a real hack, but you might able to get around this if you
uncheck the “Create Account With Ent Request” checkbox
use a “GET” call as your Account Create operation just to return the account ID.
Reconfigure your current “create” as an “Add Entitlement” operation.
This will force a successful response on the account creation task and then rely on the add entitlement option to add the access after the account is “created”.
@KevinHarrington , since accounts aren’t really created on the target environment, the “Get” operation won’t return the user, unless I create a dummy “Get” operation that returns a 200 Ok each time it’s targeted. wdyt?
Do you not have an API that can give you the results of the current user using GET operation. Then you can use that operation in Create Account operation and if this fails or the result is not found then anyways group membership should not proceed further.
And you can then use the current create operation as add Entitlement operation. CreateAccountWithEntRequest may not be needed here. If you want to use this operation then web service operation rule will be needed where you need to create your own restclient and then use a for loop against groups and make these api calls from the rule.
Created a dummy “Get Object” operation that always return 200 Ok
Created a dummy “Create Account” which is a copy of the “Get Object”
Created a “Add Entitlement” operation that will add the user to the group + Changed the body email value from $plan.userEmail$ to $plan.nativeIdentity$
DIsabled the “Create Account With “Ent” Request” option
The “addRemoveEntInSingleReq” is still set to false
This allowed me to add the external user to two different Google groups.
If Operation Type is Create Account and we are passing Get Request , So according to your solution it should work but I’m getting Bad request . I think it should give Bad Request only.
Indeed, my “Create account” type operation is configured with a Get method and, AFAIK, is working fine. I’d like to know where did you spot the “Bad request” error message? I may be missing something so I need to check on my side as well.
