In the Preferences -> XNAT Connection put a HTTPS adress in server adress field, user name and password.
Click Connect button.
Then the connection is failed because of some ssl problems and shown in the console.
Description
Description
Related Objects
Related Objects
- Mentioned In
- T23249: Ensure openSSL availability for MITK installers using XNAT plugin or other REST services
rMITKe5949d790a0d: Merge branch 'T18908-add-option-to-include-openssl-libs-in-installer'
rMITK6e557f85faef: Merge branch 'T18908-add-option-to-include-openssl-libs-in-installer'
rMITKd683f1c6342c: Merge branch 'T18908-add-option-to-include-openssl-libs-in-installer'
Event Timeline
Comment Actions
A Workaround might be:
- Download latest openssl
- Put the DLL-files into the bin-folder of Qt (MyPath: "C:\Qt\Qt5.4.1\5.4\msvc2013_64_opengl\bin")
Comment Actions
This is a know issue for Qt:
http://stackoverflow.com/questions/20351155/how-can-i-enable-ssl-in-qt-windows-application
Comment Actions
This is a deliberate decision of the Qt team due to import/export restrictions regarding OpenSSL to some parts of the world, see http://doc.qt.io/qt-5/ssl.html. We might consider deploying OpenSSL with our installers.
Comment Actions
I added a find package openssl to the CMakeLists.txt of the xnat plugin. If openssl can not be automatically found (which is likely for windows), you can set LIB_EAY_RELEASE to your libeay32.dll and SSL_EAY_RELEASE to your ssleay32.dll and they will be automatically:
- copied to you binary directory
- copied to the installer directory if an installer is build
This way it should be easier to create an installer featuring the xnat plugin on windows. (I assume that openssl will be available on most *nix installs anyway )