tobiaslindulf
commented
6 years ago Hi, and sorry for a very late response. The library/package we use for communicating between SSEToRserve and RServe , called RserveCLI2 (https://github.com/konne/RserveCLI2), does not have TLS support (not to my knowledge at least). Only username and password protection. So one thing you could do is to ask them if they want to add TLS support in their lib. Maybe you can protect the communication in another way or even run the SSEToRserve plugin on the same machine as the RServe process is running (only localhost communication). You can also ask the community if they have some tips for you in the following slack channel: https://qlik-branch.slack.com/messages/C2J190P5M
Description
This is not an issue report. This is initially a query. Does the SSE R Plugin support encrypted connections to Rserve? From the conf file it appears it only supports encrypted connections to Qlik.
Steps to Reproduce
Rserve is configured to use TLS as per: tls.key /tmp/Rserv/CA/Rserve.key tls.cert /tmp/Rserv/CA/Rserve.crt tls.port 6311 https://github.com/s-u/Rserve/wiki/rserve.conf
Expected behavior
SSE R Plugin establishes a TLS encrypted connection to Rserve
Actual behavior
SSE R Plugin console shows connection established to Rserve. Error is displayed on console (apologies I don't have access to this presently can provide this error if necessary)
Environment
Operating system where the SSE plugin is deployed
Windows Server 2016
Qlik Sense
Server
Versions