Web service application failing due to incorrect parameters

IdentityIQ (IIQ) IIQ Discussion and Questions
, , , , , ,
1

Hi all,

We have a web service application for which the “Identity attribute = email” and “Display Attribute = email”

While performing a create operation for a web service application, I am observing the below:

  1. When I put $plan.email$ in the body, the access request says that the email wasn’t supplied and the call fails
  2. When I put $plan.nativeIdentity$ in the body, the access request gets the value and is successful

Note: We already have a provisioning policy in place which uses a script to returns the email attribute to the plan

Thanks in advance

2

In the code, please try to print the plan before the create operation Check if the email is part of the plan or not.

3

Sure @msingh900 . But my concern is why would the email be left out whereas there are other attributes like firstname and lastname also being in the policy and being used in the body through $plan.lastname$ and $plan.lastname$

4

double check whether all user attributes are in place and print plan in before operation rule for create operation

5

Printing plan is just to make sure that whether email attribute is present or not in the plan.

6

Please use before operation rule. it will help to check plan and update payload.

7

Hi @rishavghoshacc ,

As you have marked it as account ID email would be populated using $plan.nativeidentity$ not with $plan.email$

Try changing the account id from email to another attribute and then use $plan.email$ then it should populate as expected as per my knowledge

Thanks in advance

Avinash Mulpuru

2 Likes
8

I would also suggest, write a before operation rule, since all the attributes are getting sent in the payload, just add the small line of code to add email also in payload.