# Using ACCESS::session with an LTM Policy

**URL:** <https://community.f5.com/t/using-access-session-with-an-ltm-policy/57350>\
**Category:** Technical Forums\
**Tags:** design, local-traffic-policy, big-ip-access-policy-manager-apm, security, ltm, application-delivery\
**Created:** [August 21, 2015, 6:33pm UTC](https://community.f5.com/t/using-access-session-with-an-ltm-policy/57350 "2015-08-21T18:33:38Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Walter\_Kacynski](https://d1p9zq3aats0t8.cloudfront.net/user_avatar/community.f5.com/walter_kacynski/32/18653_2.png) [@Walter\_Kacynski](https://community.f5.com/u/Walter_Kacynski)\
**Post date:** [August 21, 2015, 6:33pm UTC](https://community.f5.com/t/using-access-session-with-an-ltm-policy/57350/1 "2015-08-21T18:33:38Z")

</div>

Is there any way to issue a TCL [ACCESS::session data set] within an LTM Policy decision? I want to be able to set a session variable based on a set of conditions.

Thanks.

---

<div class="post-metadata">

**Author:** ![Kevin\_Stewart](https://d1p9zq3aats0t8.cloudfront.net/user_avatar/community.f5.com/kevin_stewart/32/15267_2.png) [@Kevin\_Stewart](https://community.f5.com/u/Kevin_Stewart)\
**Post date:** [August 21, 2015, 6:37pm UTC](https://community.f5.com/t/using-access-session-with-an-ltm-policy/57350/2 "2015-08-21T18:37:45Z")

</div>

Not today. You’d need to use an iRule.

---

<div class="post-metadata">

**Author:** ![Walter\_Kacynski](https://d1p9zq3aats0t8.cloudfront.net/user_avatar/community.f5.com/walter_kacynski/32/18653_2.png) [@Walter\_Kacynski](https://community.f5.com/u/Walter_Kacynski)\
**Post date:** [August 21, 2015, 6:45pm UTC](https://community.f5.com/t/using-access-session-with-an-ltm-policy/57350/3 "2015-08-21T18:45:47Z")

</div>

OK, that’s what I figured. I’m going to try using a negative match for the rules that I want to fall thru the policy logic for a TCL set variable option then if the variable does not exist, the iRule will take over. In the iRule I will use the “[info exists sso\_config]”. I assume that in V12 things will change.