Hi, just to let you know ...
I try my certificat with a test environnement with old version : HTTPD 2.2, with 2.0.3 version of OCS Inventory server and Mac Agent. It works well for deployement (inventory works only in HTTP because this version does not include SSL=0 option) ... So back to our new test environnement with 2.4.3 server.
I try to change httpd conf ssl file. I put all loglevel in max information (debug). I change SSLProtocol to "all -SSLv2" ... And the ssl_access_log, ssl_request_log and ssl_error_log give me much informations.
With 2.4.3 Server and 2.3.1 Mac Agent, inventory works in HTTPS (with SSL=0 option) but the Agent does not ask for the deployement info url (https://server/download/XXXXXXXX/Info) !
With old Mac agent (2.0.3) we can see the SSL error (hanshack failed) when it try to connect to https://server/download/XXXXXXXX/Info. But no trace of this connection with the new agent.
It seems that the new agent does not launch the download mechanism.
With new Agent with SSL=1, we have SSL hanshack failed (I let the error mistake ... I know it's "handshake"). With old agent in HTTPS, same error.
We still search. Do you have news from you side ?
I try my certificat with a test environnement with old version : HTTPD 2.2, with 2.0.3 version of OCS Inventory server and Mac Agent. It works well for deployement (inventory works only in HTTP because this version does not include SSL=0 option) ... So back to our new test environnement with 2.4.3 server.
I try to change httpd conf ssl file. I put all loglevel in max information (debug). I change SSLProtocol to "all -SSLv2" ... And the ssl_access_log, ssl_request_log and ssl_error_log give me much informations.
With 2.4.3 Server and 2.3.1 Mac Agent, inventory works in HTTPS (with SSL=0 option) but the Agent does not ask for the deployement info url (https://server/download/XXXXXXXX/Info) !
With old Mac agent (2.0.3) we can see the SSL error (hanshack failed) when it try to connect to https://server/download/XXXXXXXX/Info. But no trace of this connection with the new agent.
It seems that the new agent does not launch the download mechanism.
With new Agent with SSL=1, we have SSL hanshack failed (I let the error mistake ... I know it's "handshake"). With old agent in HTTPS, same error.
We still search. Do you have news from you side ?