# Creating an Account WEBSERVICES

**URL:** <https://developer.sailpoint.com/discuss/t/creating-an-account-webservices/176117>\
**Category:** SHF Discussion and Questions\
**Tags:** webservice-connector, identity-security-cloud, provisioning\
**Created:** [September 3, 2025, 3:07pm UTC](https://developer.sailpoint.com/discuss/t/creating-an-account-webservices/176117 "2025-09-03T15:07:04Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![torry\_salamat](https://avatars.discourse-cdn.com/v4/letter/t/3be4f8/32.png) [@torry\_salamat](https://developer.sailpoint.com/discuss/u/torry_salamat)\
**Post date:** [September 3, 2025, 3:07pm UTC](https://developer.sailpoint.com/discuss/t/creating-an-account-webservices/176117/1 "2025-09-03T15:07:04Z")

</div>

Hello Community,

I am trying to test the creation of an account on a WEB Application i configured the test connection,account aggregation and create an account operations

And on the identityProfile on the active state i added on the Enable Tab my Source

But when i refresh an identity to test the creation i don’t see any provisioning ongoing

am i missing something? Is there a simple way to test the creation without using the IdentityProfile because i don’t have any entitlements for now for my source I only want to create the account,

Many thanks,

---

<div class="post-metadata">

**Author:** ![iamology](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/iamology/32/6964_2.png) [@iamology](https://developer.sailpoint.com/discuss/u/iamology)\
**Post date:** [September 3, 2025, 3:22pm UTC](https://developer.sailpoint.com/discuss/t/creating-an-account-webservices/176117/2 "2025-09-03T15:22:14Z")

</div>

> [@torry\_salamat](#):
>
> added on the Enable Tab my Source

This will not create an account. This is to enable an account only if it already exists.

You need to set up a birth right role with an entitlement from the source to trigger the create account process

---

<div class="post-metadata">

**Author:** ![torry\_salamat](https://avatars.discourse-cdn.com/v4/letter/t/3be4f8/32.png) [@torry\_salamat](https://developer.sailpoint.com/discuss/u/torry_salamat)\
**Post date:** [September 3, 2025, 3:25pm UTC](https://developer.sailpoint.com/discuss/t/creating-an-account-webservices/176117/4 "2025-09-03T15:25:01Z")

</div>

Hello Nithesh,

Thank you for your answer,

Are there any ways to tell ISC to create the account without using the entitlements?

---

<div class="post-metadata">

**Author:** ![sauvee](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/sauvee/32/23601_2.png) [@sauvee](https://developer.sailpoint.com/discuss/u/sauvee)\
**Post date:** [September 3, 2025, 3:32pm UTC](https://developer.sailpoint.com/discuss/t/creating-an-account-webservices/176117/5 "2025-09-03T15:32:05Z")

</div>

You have to trigger creation from an entitlement being assigned. With a webservices connector however you can setup a ‘dummy’ entitlement and trigger creation based on that (ignoring the dummy entitlement in provisioning).

Check this topic for inspiration:

> [@Use after operation rule to create entitlements in SailPoint](https://developer.sailpoint.com/discuss/t/use-after-operation-rule-to-create-entitlements-in-sailpoint/174242):
>
> Problem We have an internal home made application which only connection method for provisioning is a SOAP WebService with one operation for create and update accounts. However this web service does not include any read operation for either accounts or entitlements. Solution One way I think I could solve this is by configuring the aggregate group operation with the provisioning endpoint of the web service and send an invalid request. Then implement an after operation rule which will have harcode…

---

<div class="post-metadata">

**Author:** ![udayputta](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/udayputta/32/14195_2.png) [@udayputta](https://developer.sailpoint.com/discuss/u/udayputta)\
**Post date:** [September 3, 2025, 7:35pm UTC](https://developer.sailpoint.com/discuss/t/creating-an-account-webservices/176117/6 "2025-09-03T19:35:50Z")

</div>

Hi Torry,

If this is a birthright access to every user then you may configure a Role with matching criteria to assign the access from this source and eventually trigger create account operation. If you are just testing if create account is working then you need make one of the access from this source as requesable via APs or Role or Entitlement (if feature is available) and raise the request from the Request Center.

---

<div class="post-metadata">

**Author:** ![torry\_salamat](https://avatars.discourse-cdn.com/v4/letter/t/3be4f8/32.png) [@torry\_salamat](https://developer.sailpoint.com/discuss/u/torry_salamat)\
**Post date:** [September 4, 2025, 7:59am UTC](https://developer.sailpoint.com/discuss/t/creating-an-account-webservices/176117/7 "2025-09-04T07:59:03Z")

</div>

Thank you for your answers @udayputta @sauvee ,

I have a special entitlement usecase :

I have this attibute called role but there’s no specific endpoint to get it

the only way to get it is in the account itself because it’s within reach with a GET USERS : When you do a GET USERS you’ll get the specific role too

How can i aggregate this entitlement? I already tried to add a new schema for this entitlement and i configured a new operation Group Aggregation - Role that is calling the Account Aggregation Operation first ( as a Parent) to get the role

Is this the way to get this entitlement?

Thank you,

---

<div class="post-metadata">

**Author:** ![sauvee](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/sauvee/32/23601_2.png) [@sauvee](https://developer.sailpoint.com/discuss/u/sauvee)\
**Post date:** [September 4, 2025, 8:41am UTC](https://developer.sailpoint.com/discuss/t/creating-an-account-webservices/176117/8 "2025-09-04T08:41:25Z")

</div>

I’ve seen this use case in the past as well.

It’s easiest to create a dummy user in the target system that has ALL entitlements that are available in the system. Then create a group aggregation operation that gets this single user and pull off all entitlements from the user.

---

<div class="post-metadata">

**Author:** ![torry\_salamat](https://avatars.discourse-cdn.com/v4/letter/t/3be4f8/32.png) [@torry\_salamat](https://developer.sailpoint.com/discuss/u/torry_salamat)\
**Post date:** [September 4, 2025, 8:56am UTC](https://developer.sailpoint.com/discuss/t/creating-an-account-webservices/176117/9 "2025-09-04T08:56:42Z")

</div>

Hello Edwin,

Thanks again for answering,

I am just trying to aggregate only one entitlement for now just to test but it doesn’t seem to work for me am i missing a step?

---

<div class="post-metadata">

**Author:** ![sauvee](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/sauvee/32/23601_2.png) [@sauvee](https://developer.sailpoint.com/discuss/u/sauvee)\
**Post date:** [September 4, 2025, 9:10am UTC](https://developer.sailpoint.com/discuss/t/creating-an-account-webservices/176117/10 "2025-09-04T09:10:26Z")

</div>

Can you share the raw response as well as your configured response mapping + schema? That way it’s easier to check what might be the issue.

---

<div class="post-metadata">

**Author:** ![torry\_salamat](https://avatars.discourse-cdn.com/v4/letter/t/3be4f8/32.png) [@torry\_salamat](https://developer.sailpoint.com/discuss/u/torry_salamat)\
**Post date:** [September 4, 2025, 12:18pm UTC](https://developer.sailpoint.com/discuss/t/creating-an-account-webservices/176117/11 "2025-09-04T12:18:43Z")

</div>

Hello Back Edwin,

It worked i think it was a cache problem,

Thanks for the help

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\
**Post date:** [November 3, 2025, 12:19pm UTC](https://developer.sailpoint.com/discuss/t/creating-an-account-webservices/176117/12 "2025-11-03T12:19:25Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
