I have two questions about using Stash over https with SLL..
1) we are using stash over https.. any way for it to stop asking for the password everything I try to do a push or pull
2) some of my users are getting the following error:
fatal: unable to access 'xxxx': Problem with the SSL CA cert (path? access rights?)
I fixed it but doing "git config --global http.sslVerify false"
but what is the real issue and how do I address it... thanks
Community moderators have prevented the ability to post new answers.
Hi Johnathan,
1) The answer given by Anurag is accurate on this one. Please refer to this article:
2) Git does not use the Java keystore for SSL certificates. This is not accurate. The blogpost below is based on Windows, but could be applied to any OS:
I hope that helps.
Best,
Thiago Bomfim
yea.. I try this and I am still getting .... fatal: unable to access 'https://XXX/';: SSL certificate problem: unable to get local issuer certificate
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
1) we are using stash over https.. any way for it to stop asking for the password everything I try to do a push or pull
You can use SourceTree to save password. [SourceTree-> Tools-> Options-> Authentication -> (Edit)]
You can also find other options here-> https://confluence.atlassian.com/display/STASH/Permanently+authenticating+with+Git+repositories .
2) some of my users are getting the following error:
fatal: unable to access 'xxxx': Problem with the SSL CA cert (path? access rights?)
I guess, you need to publish or add CA certificate to java keystore to authenticate.
http://stackoverflow.com/questions/4325263/how-to-import-a-cer-certificate-into-a-java-keystore
http://www.tutorialspoint.com/unix_commands/keytool.htm (check "Importing Certificates" topic)
It can be done using below commond:
.
..\..\bin\keytool -import -trustcacerts -keystore cacerts - storepass changeit -noprompt -alias yourAliasName -file path\to\certificate.cer
Hope this will help.
Regards,
Anurag Prakash
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
yea.. I try this and I am still getting .... fatal: unable to access 'https://XXX/';: SSL certificate problem: unable to get local issuer certificate
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.