Unsolved
This post is more than 5 years old
3 Posts
0
675
September 29th, 2016 23:00
approve MDM certificate fialed during config phase
Hi everyone,
I am running into an issue during the config phase and hope anyone can help me...
The case:
6 W2012R2 nodes
all with 64bit Java8u102 , 64bit c++, Python and 64bit Openssl
so I think the basics are covered.
Using the Installer V2.0.0.3 and Wizzard all works fine until the Config Phase.
There I get an error on the approval of the MDM certificate./ Secured communication is disabled on MDM
Is there anyone out there who has a clue as to what could cause this??
No Events found!
marc_punte
3 Posts
1
October 5th, 2016 03:00
Hi Pawel,
I think we found the problem.
It seems you can’t use the latest version of openssl on Scaleio 2.0.0.3
We tried with openSSL1.0.2J and that works.
Hope this helps anyone else…
Talk later,
Marc.
Van: pawelw
Verzonden: woensdag 5 oktober 2016 12:13
Aan: Marc Punte
Onderwerp: Re: - approve MDM certificate fialed during config phase
DECN
approve MDM certificate fialed during config phase
reply from Pawel in ScaleIO - View the full discussion
pawelw1
306 Posts
0
October 5th, 2016 03:00
Hi Marc,
Did you try to set "Allow unsecure communication" under Advanced tab?
Cheers,
Pawel
marc_punte
3 Posts
0
October 5th, 2016 05:00
Hi Pawel,
Yep,
The installer sends you to https://slproweb.com/products/Win32OpenSSL.html where you can find Win64 OpenSSL v1.0.2j.exe as latest version.
Met vriendelijke groet,
Marc Punte
+31 (0)35 6725574
pawelw1
306 Posts
0
October 5th, 2016 05:00
Hi Marc,
Many thanks for sharing.. do you remember what was the version of OpenSSL that didn't work?
Many thanks,
Pawel
RHasleton1
73 Posts
1
October 5th, 2016 10:00
Marc,
You are correct. Customers still need to use the v1.0.x versions. There is a caution on the website about the v1.1.0 version:
August 29, 2016 - OpenSSL 1.1.0 is quite different from previous releases. Developers need to recompile their software to support 1.1.0. Users should install BOTH the 1.0.2 series (LTS) and the 1.1.0 series for maximum application compatibility. See the official OpenSSL release strategy document for more details.
There's no need to install both as suggested, but just so you're aware of why it failed. At this point, the documentation needs to be updated to reflect that and possibly a note in the IM as well. Thanks for the information!