# Set SSL session in Gatling 3

**URL:** <https://community.gatling.io/t/set-ssl-session-in-gatling-3/4802>\
**Category:** Gatling (Open-Source)\
**Created:** [February 7, 2019, 2:35am UTC](https://community.gatling.io/t/set-ssl-session-in-gatling-3/4802 "2019-02-07T02:35:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Radi\_S](https://avatars.discourse-cdn.com/v4/letter/r/7ab992/32.png) [@Radi\_S](https://community.gatling.io/u/Radi_S)\
**Post date:** [February 7, 2019, 2:35am UTC](https://community.gatling.io/t/set-ssl-session-in-gatling-3/4802/1 "2019-02-07T02:35:42Z")

</div>

Hello,

We have to set different keystore (p12 file) for every virtual user. We were using .disableClientSharing and setting the session attributes as below:

session =\>  
session.set(“gatling.http.ssl.keyStore.file”, session(“user”).as[String]+".p12")

This was working fine in Gatling 2.2. But, after switching to Gatling 3.0, I am not able to set the session as above. I know that the .disableClientSharing is removed in Gatling 3.0. Can you please suggest how I can do something like this in Gatling 3.0? I get the required response code if I configure the keystore in ‘gatling.conf’ file in Gatling 3.

Thank you for great product and support!

---

<div class="post-metadata">

**Author:** ![slandelle](https://dub1.discourse-cdn.com/flex013/user_avatar/community.gatling.io/slandelle/32/4_2.png) [@slandelle](https://community.gatling.io/u/slandelle)\
**Post date:** [February 7, 2019, 8:17am UTC](https://community.gatling.io/t/set-ssl-session-in-gatling-3/4802/2 "2019-02-07T08:17:32Z")

</div>

This feature (that was clearly implemented as a hack) hasn’t been ported in Gatling 3 yet.  
That’s something we might consider for a future version.