Sahi Pro is an enterprise grade test automation platform which can automate web, mobile, windows and java based applications. Get your 30 day free trial.
Discuss your Sahi Pro usage patterns, best practices, problems and solutions. Help others solve their problems and seek help from the community when needed. If you need specific support on your application, please email support @ sahipro.com
Discuss your Sahi Pro usage patterns, best practices, problems and solutions. Help others solve their problems and seek help from the community when needed. If you need specific support on your application, please email support @ sahipro.com
How configure SAHI PRO to use a certificate with a key GEMALTO
PremiumReflexes
Members
Hi everybody.
I experiment all the possibilities SAHI PRO in order to be able to know if SAHI PRO meets our needs.
Today I work on the possibility of SAHI to connect to a Flex application with a certificate Gemalto.
I have search on the documentation and i discover that SAHI auto generates these certificates. (Don't hesitate to tell me if i don't understand the real functioning of SAHI)
This is a bit annoying for us. The access to our application is normally impossible without presentation of a certificate with key Gemalto. (for testing scripting on SAHI etc. we have bypassed the connexion but it restrained our possibility. We need a GEMALTO access in order to go further in our application and for not denaturate application with not desired modifications by developpement's team)
I do not know a lot about this way to authenticate.
However, I know that how I have configure Firefox without SAHI on my pc, and my question is, can we do the same things with SAHI PRO ?
1 installation GEMALTO on the pc.
2 installation GEMALTO DRIVER on the browser
2-1 FF -> Option -> Advanced -> Certificates -> device security -> load (and give to FF the file xltCk.dll from GEMALTO)
3 Configuration of the user certificate's
3-1 FF -> Option -> Advanced -> Certificates -> View Certificates -> Your Certificates -> Import -> and give the certificates.p12
I have read on the doc that we can configure profile for Firefox and I have manually configure the GEMALTO certificate on the sahi FF, but when I a attempt to connect, i have a an error.
Here the error displayed by the browser :
Sahi Error - Received fatal alert: handshake_failure
Sahi could not connect to the desired URL
And here, the stacktrace of JAVA :
javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
at sun.security.ssl.Alerts.getSSLException(Unknown Source)
at sun.security.ssl.Alerts.getSSLException(Unknown Source)
at sun.security.ssl.SSLSocketImpl.recvAlert(Unknown Source)
at sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source)
at sun.security.ssl.SSLSocketImpl.readDataRecord(Unknown Source)
at sun.security.ssl.AppInputStream.read(Unknown Source)
at java.io.BufferedInputStream.fill(Unknown Source)
at java.io.BufferedInputStream.read1(Unknown Source)
at java.io.BufferedInputStream.read(Unknown Source)
at sun.net.www.http.HttpClient.parseHTTPHeader(Unknown Source)
at sun.net.www.http.HttpClient.parseHTTP(Unknown Source)
at sun.net.www.http.HttpClient.parseHTTP(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown So
urce)
at java.net.HttpURLConnection.getResponseCode(Unknown Source)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(Unk
nown Source)
at net.sf.sahi.RemoteRequestProcessor.processHttp(RemoteRequestProcessor
.java:128)
at net.sf.sahi.RemoteRequestProcessor.processHttp(RemoteRequestProcessor
.java:75)
at net.sf.sahi.RemoteRequestProcessor.processHttp(RemoteRequestProcessor
.java:71)
at net.sf.sahi.ProxyProcessor.processAsProxy(ProxyProcessor.java:134)
at net.sf.sahi.ProxyProcessor.run(ProxyProcessor.java:75)
at net.sf.sahi.ProxyProcessor.processConnect(ProxyProcessor.java:169)
at net.sf.sahi.ProxyProcessor.processAsProxy(ProxyProcessor.java:127)
at net.sf.sahi.ProxyProcessor.run(ProxyProcessor.java:75)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
fÚvr. 03, 2014 11:26:26 AM net.sf.sahi.RemoteRequestProcessor processHttp
Avertissement: Returning CannotConnectResponse for: https://aaaaaaaaaaaaaaa.fr/aaaaaa/aaa.aa
Thank you in advance for each board or solution that could do me going further on the subject.
I experiment all the possibilities SAHI PRO in order to be able to know if SAHI PRO meets our needs.
Today I work on the possibility of SAHI to connect to a Flex application with a certificate Gemalto.
I have search on the documentation and i discover that SAHI auto generates these certificates. (Don't hesitate to tell me if i don't understand the real functioning of SAHI)
This is a bit annoying for us. The access to our application is normally impossible without presentation of a certificate with key Gemalto. (for testing scripting on SAHI etc. we have bypassed the connexion but it restrained our possibility. We need a GEMALTO access in order to go further in our application and for not denaturate application with not desired modifications by developpement's team)
I do not know a lot about this way to authenticate.
However, I know that how I have configure Firefox without SAHI on my pc, and my question is, can we do the same things with SAHI PRO ?
1 installation GEMALTO on the pc.
2 installation GEMALTO DRIVER on the browser
2-1 FF -> Option -> Advanced -> Certificates -> device security -> load (and give to FF the file xltCk.dll from GEMALTO)
3 Configuration of the user certificate's
3-1 FF -> Option -> Advanced -> Certificates -> View Certificates -> Your Certificates -> Import -> and give the certificates.p12
I have read on the doc that we can configure profile for Firefox and I have manually configure the GEMALTO certificate on the sahi FF, but when I a attempt to connect, i have a an error.
Here the error displayed by the browser :
Sahi Error - Received fatal alert: handshake_failure
Sahi could not connect to the desired URL
And here, the stacktrace of JAVA :
javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
at sun.security.ssl.Alerts.getSSLException(Unknown Source)
at sun.security.ssl.Alerts.getSSLException(Unknown Source)
at sun.security.ssl.SSLSocketImpl.recvAlert(Unknown Source)
at sun.security.ssl.SSLSocketImpl.readRecord(Unknown Source)
at sun.security.ssl.SSLSocketImpl.readDataRecord(Unknown Source)
at sun.security.ssl.AppInputStream.read(Unknown Source)
at java.io.BufferedInputStream.fill(Unknown Source)
at java.io.BufferedInputStream.read1(Unknown Source)
at java.io.BufferedInputStream.read(Unknown Source)
at sun.net.www.http.HttpClient.parseHTTPHeader(Unknown Source)
at sun.net.www.http.HttpClient.parseHTTP(Unknown Source)
at sun.net.www.http.HttpClient.parseHTTP(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown So
urce)
at java.net.HttpURLConnection.getResponseCode(Unknown Source)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(Unk
nown Source)
at net.sf.sahi.RemoteRequestProcessor.processHttp(RemoteRequestProcessor
.java:128)
at net.sf.sahi.RemoteRequestProcessor.processHttp(RemoteRequestProcessor
.java:75)
at net.sf.sahi.RemoteRequestProcessor.processHttp(RemoteRequestProcessor
.java:71)
at net.sf.sahi.ProxyProcessor.processAsProxy(ProxyProcessor.java:134)
at net.sf.sahi.ProxyProcessor.run(ProxyProcessor.java:75)
at net.sf.sahi.ProxyProcessor.processConnect(ProxyProcessor.java:169)
at net.sf.sahi.ProxyProcessor.processAsProxy(ProxyProcessor.java:127)
at net.sf.sahi.ProxyProcessor.run(ProxyProcessor.java:75)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
fÚvr. 03, 2014 11:26:26 AM net.sf.sahi.RemoteRequestProcessor processHttp
Avertissement: Returning CannotConnectResponse for: https://aaaaaaaaaaaaaaa.fr/aaaaaa/aaa.aa
Thank you in advance for each board or solution that could do me going further on the subject.
Answers
http://sahi.co.in/forums/discussion/1335/connecting-to-https-with-keystore-generated-by-another-program/p1
I can now connect when using the client certificate (.pkcs and not .p12) directly, the config settings can be found below:
# Uncomment the following lines to use a client certificate.
# If there is no password, do not uncomment the password line.
# keystore type can be JKS, PKCS12 etc.
ssl.client.keystore.type = PKCS12
ssl.client.cert.path = ../certs/MyCert.pkcs12
ssl.client.cert.password = password