# Configuring client certificate to login

**URL:** <https://community.gatling.io/t/configuring-client-certificate-to-login/2501>\
**Category:** Gatling (Open-Source)\
**Created:** [August 31, 2015, 12:54pm UTC](https://community.gatling.io/t/configuring-client-certificate-to-login/2501 "2015-08-31T12:54:46Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Giorgi](https://avatars.discourse-cdn.com/v4/letter/g/838e76/32.png) [@Giorgi](https://community.gatling.io/u/Giorgi)\
**Post date:** [August 31, 2015, 12:54pm UTC](https://community.gatling.io/t/configuring-client-certificate-to-login/2501/1 "2015-08-31T12:54:46Z")

</div>

I’m trying to run a Recording PoC with Gatling for one of our applications.  
To login to the application user has to submit a client certificate.  
When I’m accessing the login web-page, GET request is successfully recorded, but when I’m submitting the certificate browser fails with error: “Secure Connection Failed”

Am I missing some piece of configuration here?

HTTPS Mode: Self-signed Certificate

gatling.conf

ssl {  
trustStore {  
type = “JKS” # Type of SSLContext’s TrustManagers store  
file = “C:/work/gatling/certificate/truststore.jks” # Location of SSLContext’s TrustManagers store  
password = “pass” # Password for SSLContext’s TrustManagers store  
#algorithm = “” # Algorithm used by SSLContext’s TrustManagers store  
}  
keyStore {  
type = “JKS” # Type of SSLContext’s KeyManagers store  
file = “C:/work/gatling/certificate/mykeystore.jks” # Location of SSLContext’s KeyManagers store  
password = “pass” # Password for SSLContext’s KeyManagers store  
#algorithm = “” # Algorithm used SSLContext’s KeyManagers store  
}  
}

mykeystore.jks contains only one Alias