The Web services connector create account

RiyazuddinM · December 30, 2024, 10:54am

I have received the requirement to create accounts in the end application using SailPoint. There is no role or group management involved in the end application.

The task is to retrieve direct employee details from Active Directory (AD) into SailPoint and then create the accounts in the end application.

Retrieve the data for direct employee is done. since the sailpoint is integrated with AD.

Thanks
Md Riyazuddin

Arpitha1 · December 30, 2024, 11:11am

Hi @RiyazuddinM If your requirement is to just perform aggregation and create account, then you can change the Identity Attribute from ‘Employee ID’ to ‘Username’.

Also add the field in create provisioning form with Username and pass the identity email.

RiyazuddinM · December 30, 2024, 12:15pm

Hi @Arpitha1 ,

I changed the identity attribute to username and try to create an account, lucky now account was getting created in the end appllication, but I am still getting the native identity warm

also, in the access request its showing as the requested got failed.

also, in the identity cube I am seeing two application.
why is this showing in this way.

can you please guide me.

Thanks,
Md Riyazuddin

Arpitha1 · December 30, 2024, 1:32pm

@RiyazuddinM

Can you send,

Application xml or ProvisioningForm entry
Debug → IdentityRequest → export the content of 4044. You may need to append some zeros like (000004044) . Basically I need to see what’s your plan

RiyazuddinM · December 30, 2024, 1:57pm

Hello @Arpitha1

Application Xml
Availo.xml (17.6 KB)

Identity request
IdentityRequest4044.xml (29.8 KB)

Thanks for your support

Thanks
Md Riyazuddin

mkumariaas · December 30, 2024, 2:35pm

@RiyazuddinM i believe it is type which you have for idenity Attribute, which is correct or not please revalidate
you have mapping like

While passing in json you are using
"UserName" : "$plan.userName$"
In provisioning policy

In idenitty Attribute
identityAttribute=“Username”

So somewhere your mapping is not correct , but the correct mapping and for safer side while you are sending create request that time also put the mapping like you have account aggreatuo for single user. This issue will be resolve once you add resource mapping for create and correct the mapping.

Arpitha1 · December 30, 2024, 3:12pm

Hi @RiyazuddinM

I can see userName is plan. Hence your API is executed successfully and account might have created in target.

The issue is in identifying nativeIdentity. Can you change userName field as Username in create provision policy. Basically is should look as below.

And then update the Body in Create Account operation.

$plan.nativeIdentity$

RiyazuddinM · December 31, 2024, 9:23am

Hi @Arpitha1 ,

I have updated the provisioning and the body

and try to test the create account from SailPoint it giving me an error/warm of native identity.
the account is getting created in the target application