Installing SSL module for REST Requests

[heber_silva]

Hi Experts,

I built a customizer using the Python Requests library to invoke an API REST/JSON from my Custom-IVR flow, but as my endpoint uses HTTPS, when I invoke the endpoint the following error message is raised on CEM log:

"ERR> <class 'requests.exceptions.SSLError'> : HTTPSConnectionPool(host='xyz.com', port=443): Max retries exceeded with url: /xxx/xxx/xx/xxx/xxx (Caused by SSLError("Can't connect to HTTPS URL because the SSL module is not available."))"

I've installed a standalone Python 3.8 software on the same CCtr Server and using Python console for testing purposes the script works fine with no error related to SSL module.

How can I install the SSL module for importing on my Customizer or is there any workaround on this issue?

- Running on SAP CCtr FP16 P1.

Best Regards,

Heber Olivar

[former_member594564]

Hey! Have you solved this problem? I have the same one and I don't know what I can do.

I have installed OpenSSL on the server but nothing has changed.

Best regards,

Pavel Mazharov.

[former_member736352]

Hi Guys,

due to shipping restrictions we are not allowed to ship encryption related code in our package and therefore the built-in Python package is very limited. Therefore CEM is not able to take the related connection and even installing separate Python package to server doesn't help as CEM is by default using Python from our shipment. You can see this from CEM startup log; on the very top there is reference to Python and pointing to specific folder. (which is not pointing to locally installed Python)

If you wish to use full Python package, then you can define in IA to use "external Python". Pre-requisite is FP16P1 or newer and best instructions for that can be found from SAP Note 2933871. It's speaking about Microsoft Exchange but there is instructions how to do external Python. After you have installed "external Python" you should be able to see in CEM logs pointing to the folder where Python is located.

NOTE: by installing the external Python you accept that SAP (Sinch) is not anymore responsible to maintain the used Python version. In such a case it's you who should make sure it's secure and up-to-date.

Long time ago there were unofficial instructions at this community how to import Python modules to standard package and that is also a way to forward. I didn't try to find it now but you may try.

This info should help you guys forward.

BR,
Jukka