Originally published on 2011-09-08 01:40
Hi, I'm just wondering if it works to run cov-manage-im on secure connections only to the CIM-server (version 5.3 & version 5.4)? The guys that are doing the installations have a hard time getting this to work. I'm asking for both versions since one server runs here in Stockholm (5.3), and one in Madrid (5.4).
Originally published on 2011-09-08 08:34
to add some more info: we're running the coverity server on a separate backend server that is not directly available to the users with a frontend server doing a ProxyPass and ProxyPassReverse to the backend and presenting the data to the users. the frontend is doing the SSL towards our users while talking normal http with the backend. on one of our coverity's we don't use SSL yet and on that coverity our setup works without any problems, when cov-manage-im want 's to talk to the backend it talks over port 80 towards the frontend server which in it's turn gets the data over a non standard port from the backend server and presents the data to the user on the server where we have enabled SSL though the request to port 80 would be redirected to port 443 by a 302 redirect. when the client (cov-manage-im) tries to ask for the data over port 443 I'm guessing the reply is a "400 Bad Request" because we're talking plain http to an SSL-enabled port The error message we receive is: user@server~/:> cov-manage-im --mode projects --port 443 --show --stream example-prj --host coverity.domain.com --user covuser [Error] XML reader error: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '"' (code 34) in DOCTYPE declaration; expected a space between public and system identifiers at [row,col,system-id]: [1,50,"http://coverity.domain.com:443/ws/v2/configurationservice?wsdl"] so i guess we would like to get the cov-manage-im to speak https some way.. is that possible?
It wasn't really clear, but cov-manage-im doesn't follow 302 redirects to SSL pages, you need to add the --ssl --port 8443 flags to get it to work as expected.
Otherwise, you get an error that looks like this:
[Error] XML reader error: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF in prolog
at [row,col,system-id]: [1,0,"http://localhost:8080/ws/v4/configurationservice?wsdl"]