# Can't retrieve Identity in Web Services Before Operation Rule **URL:** \ **Category:** SHF Discussion and Questions\ **Tags:** webservice-connector, identity-security-cloud\ **Created:** [June 12, 2025, 6:45pm UTC](https://developer.sailpoint.com/discuss/t/cant-retrieve-identity-in-web-services-before-operation-rule/144081 "2025-06-12T18:45:32Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![JackSparrow](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/jacksparrow/32/19685_2.png) [@JackSparrow](https://developer.sailpoint.com/discuss/u/JackSparrow)\ **Post date:** [June 13, 2025, 4:47am UTC](https://developer.sailpoint.com/discuss/t/cant-retrieve-identity-in-web-services-before-operation-rule/144081/7 "2025-06-13T04:47:03Z")
@jimjohnson WebServices before operation rule is a connector rule which will not have identity object in the plan. If you want to retrieve any identity attributes in connector rules, you need to have them added to provisioning plan using before provisioning rule. Check this post: > [@Pass Non-Provisioned Attributes from Before Provision rule to Connector Rules](https://developer.sailpoint.com/discuss/t/pass-non-provisioned-attributes-from-before-provision-rule-to-connector-rules/20470): > > Introduction A common use case when developing for provisioning is the need to provide information to a connector rule that is not available on the virtual appliance (VA). This can occur because you need identity information to perform additional logic, or because a request payload requires information that is not actively changing in the account. The first case can often occur in Active Directory and Azure Native Rules, where a developer must take additional actions based on… --- _[View the full topic](https://developer.sailpoint.com/discuss/t/cant-retrieve-identity-in-web-services-before-operation-rule/144081)._