-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
https issues #16
Comments
Original comment by Sebastian Sdorra (Bitbucket: sdorra, GitHub: sdorra). When you try to access your scm-manager the ssl-filter redirects you to https://hostname:sslport/scm and if no listener is configured to hostname:sslport then you get this issue. Have a look at <<issue 9>>. |
Original comment by Anonymous. okay, looks like this is not so easy to handle because there is no listener configured from my site. I have no idea how to do this....... |
Original comment by Anonymous. That sounds GREAT! Thanks |
Original comment by Anonymous. Just a quick question - Any update here today? THANKS A LOT! |
Original comment by Sebastian Sdorra (Bitbucket: sdorra, GitHub: sdorra). Here is a first version of the wiki page. https://bitbucket.org/sdorra/scm-manager/wiki/scm-server-ssl |
Original comment by Anonymous. okay - thanks! Just one problem.....I'm running a windows server :-( |
Original comment by Sebastian Sdorra (Bitbucket: sdorra, GitHub: sdorra). That is not a problem. Start the cmd.exe and run the keytool.exe. If the keytool.exe is not in your path then you must use the complete path. For example:
|
Original comment by Anonymous. okay - scm manager is using ssl now. When I try to clone the repository now git clone https://host.com:8181/git I receive an error error: error setting certificate verify locations: What does this need? |
Original comment by Anonymous. $ git clone https://scmadmin@host.com:8181/scm/git/test test_ssl2 error: error setting certificate verify locations: while accessing https://scmadmin@host.com:8181/scm/git/test/info/refs fatal: HTTP request failed |
Original comment by Sebastian Sdorra (Bitbucket: sdorra, GitHub: sdorra). For the nice way you have to export the certificate from keystore:
And set the absolute path to cert.pem as sslCAInfo path:
|
Original comment by scm_manager_tester (Bitbucket: scm_manager_tester, ). Second option sound useful - will give it a try but not before Thursday. - SORRY |
Original comment by Sebastian Sdorra (Bitbucket: sdorra, GitHub: sdorra). Wiki page updated: https://bitbucket.org/sdorra/scm-manager/wiki/scm-server-ssl |
Original comment by Luís Bastiao Silva (Bitbucket: [Luis Bastiao](https://bitbucket.org/Luis Bastiao), ). Sorry for re-open this topic. But why this is a git issue? The https works in github. Can you clarify it to me? |
Original comment by Sebastian Sdorra (Bitbucket: sdorra, GitHub: sdorra). It is not really a git issue. It is the normal behavior of a ssl connection. If the client could not verify the certificate, it abort the connection (same behavior you could watch with a browser and a self signed certificate). Https works for github, because they have signed their certificate by a authority like verisign. You could also use a signed certificate with scm-manager, than you don't have to configure "http.sslVerify" or "http.sslCAInfo". For more information's on ssl connections http://en.wikipedia.org/wiki/Secure_Sockets_Layer. Next time please write to the mailing list https://groups.google.com/group/scmmanager for questions. |
Original report by Anonymous.
Hi,
I just changed the SCM manager settings to use https on an different port but now I can't reach the SCM Manager again.
using https://host:sslport/scm
any idea?
From the system output I can't see any entry about sslport (using 8001).
Just the http port is shown at the end:
2011-05-16 14:06:37.951:INFO::Started SelectChannelConnector@0.0.0.0:8000
but http://hostname:port/scm is not working as well.
Thanks!
The text was updated successfully, but these errors were encountered: