https issues about scm-manager

[cesmarvin]

Original comment by Sebastian Sdorra (Bitbucket: sdorra, GitHub: sdorra).

---

Have you an SSL-Listener in the server-config.xml configured? The ssl-port in the general config panel is only for a redirect to that port.

[cesmarvin]

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>>.

[cesmarvin]

Original comment by Sebastian Sdorra (Bitbucket: sdorra, GitHub: sdorra).

---

To disable the https redirect do the following steps:

Edit the config.xml in your scm home. Search the line

true

and replace it with:

false

Restart the scm-server.

[cesmarvin]

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.......

[cesmarvin]

Original comment by Sebastian Sdorra (Bitbucket: sdorra, GitHub: sdorra).

---

I will add a wiki page tomorrow.

[cesmarvin]

Original comment by Anonymous.

---

That sounds GREAT!

Thanks

[cesmarvin]

Original comment by Anonymous.

---

Just a quick question - Any update here today?

THANKS A LOT!

[cesmarvin]

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

[cesmarvin]

Original comment by Anonymous.

---

okay - thanks!

Just one problem.....I'm running a windows server :-(

[cesmarvin]

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:

#!bash

c:\Progamm Files\java\jdk1.6.x\bin\keytool.exe -genkey -alias scm -keyalg RSA -keystore keystore.jks

[cesmarvin]

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:
CAfile: /bin/curl-ca-bundle.crt
CApath: none

What does this need?

[cesmarvin]

Original comment by Anonymous.

---

$ git clone https://[email protected]:8181/scm/git/test test_ssl2
Initialized empty Git repository in C:/Users/scmadmin/test_ssl2/.git/
Password:

error: error setting certificate verify locations:
CAfile: /bin/curl-ca-bundle.crt
CApath: none

while accessing https://[email protected]:8181/scm/git/test/info/refs

fatal: HTTP request failed

[cesmarvin]

Original comment by Sebastian Sdorra (Bitbucket: sdorra, GitHub: sdorra).

---

Git does not know the certifacte. A quick and dirty workaround is to disable the certificate check:

#!bash

git config http.sslVerify false

[cesmarvin]

Original comment by Sebastian Sdorra (Bitbucket: sdorra, GitHub: sdorra).

---

For the nice way you have to export the certificate from keystore:

#!bash

keytool -exportcert -keystore keystore.jks -alias scm -rfc -file cert.pem

And set the absolute path to cert.pem as sslCAInfo path:

#!bash

git config http.sslCAInfo c:\scm-server\conf\cert.pem

[cesmarvin]

Original comment by scm_manager_tester (Bitbucket: scm_manager_tester, ).

---

Second option sound useful - will give it a try but not before Thursday. - SORRY

[cesmarvin]

Original comment by Sebastian Sdorra (Bitbucket: sdorra, GitHub: sdorra).

---

Wiki page updated:

https://bitbucket.org/sdorra/scm-manager/wiki/scm-server-ssl

[cesmarvin]

Original comment by Sebastian Sdorra (Bitbucket: sdorra, GitHub: sdorra).

---

I think this issue is solved. The clone problem is a git problem. If you have questions to the git configuration send me a bitbucket notification.

[cesmarvin]

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?

[cesmarvin]

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.