# Accessing Encrypted Application Attributes in Rule (Web Services Connector)

**URL:** <https://developer.sailpoint.com/discuss/t/accessing-encrypted-application-attributes-in-rule-web-services-connector/194874>\
**Category:** SHF Discussion and Questions\
**Tags:** webservice-connector, rules, sailpoint-identity-security\
**Created:** [February 3, 2026, 1:20am UTC](https://developer.sailpoint.com/discuss/t/accessing-encrypted-application-attributes-in-rule-web-services-connector/194874 "2026-02-03T01:20:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![sxxnex](https://avatars.discourse-cdn.com/v4/letter/s/ee59a6/32.png) [@sxxnex](https://developer.sailpoint.com/discuss/u/sxxnex)\
**Post date:** [February 3, 2026, 1:20am UTC](https://developer.sailpoint.com/discuss/t/accessing-encrypted-application-attributes-in-rule-web-services-connector/194874/1 "2026-02-03T01:20:28Z")

</div>

Is it possible to access **encrypted application attributes** from a rule?

I am using the **Web Services connector** and need the value in an **After Rule**.

Non-encrypted attributes work fine with:

```java
application.getAttributeValue("attribute_name")

```

But once the attribute is added to the application’s **encrypted attributes** , the value is no longer retrieved correctly.

I assumed encrypted attributes would be automatically decrypted when accessed from a rule, but that does not seem to be the case.

Is there a supported way to use encrypted application attributes inside a rule?

This question is a follow-up to the post linked below.

> [@Best Practice for Securing API Credentials in Web Services Connector After Rule](https://developer.sailpoint.com/discuss/t/best-practice-for-securing-api-credentials-in-web-services-connector-after-rule/194790):
>
> I am currently using the Web Services Connector in SailPoint Identity Security Cloud and implementing an After Rule. Inside the After Rule, I am calling an external API and modifying the response based on the API result. At the moment, the API credentials (client ID and client secret) are hardcoded directly in the rule, which is not ideal from a security perspective. I would like to ask: Is there a recommended way to secure or encrypt API credentials when using them in an After Rule? Is…

---

<div class="post-metadata">

**Author:** ![patrickboston](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/patrickboston/32/5876_2.png) [@patrickboston](https://developer.sailpoint.com/discuss/u/patrickboston)\
**Post date:** [February 3, 2026, 1:26am UTC](https://developer.sailpoint.com/discuss/t/accessing-encrypted-application-attributes-in-rule-web-services-connector/194874/2 "2026-02-03T01:26:55Z")

</div>

Why did you just post again instead of letting the conversation continue on your original thread?

---

<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:** [April 4, 2026, 1:27am UTC](https://developer.sailpoint.com/discuss/t/accessing-encrypted-application-attributes-in-rule-web-services-connector/194874/3 "2026-04-04T01:27:40Z")

</div>

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