# ISC VA-Based Web Services Connector - Raw JWT Token Response **URL:** \ **Category:** SHF Discussion and Questions\ **Tags:** webservice-connector, identity-security-cloud\ **Created:** [September 7, 2026, 7:10am UTC](https://developer.sailpoint.com/discuss/t/isc-va-based-web-services-connector-raw-jwt-token-response/221667 "2026-09-07T07:10:52Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![SanjeevIAM](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/sanjeeviam/32/21695_2.png) [@SanjeevIAM](https://developer.sailpoint.com/discuss/u/SanjeevIAM)\ **Post date:** [September 7, 2026, 8:17am UTC](https://developer.sailpoint.com/discuss/t/isc-va-based-web-services-connector-raw-jwt-token-response/221667/2 "2026-09-07T08:17:52Z")
Yes VA based Webservices connector supports the After Operation Rule. I would suggest you review the following solution to see if you can use Before Operation Rule approach for your case. > [@Generation of JWT using a Web Services Before Operation Rule and Private Key on VA](https://developer.sailpoint.com/discuss/t/generation-of-jwt-using-a-web-services-before-operation-rule-and-private-key-on-va/89951): > > Hi, hoping to get some input on possible approaches for the use case below: Use Case: IDN needs to communicate to an end system using via an API for identity management operations. The system requires a private public key pair to be generated with the public key pair imported on the end system’s keystore. IDN must then generate a JSON web token with the following context: Header: { “alg”:RS256 } Payload: { “iss”: name of the user who holds the public key in the app’s user store, “exp… --- _[View the full topic](https://developer.sailpoint.com/discuss/t/isc-va-based-web-services-connector-raw-jwt-token-response/221667)._