Secure Install HTTPS and LDAPS

OL Connect Automate
1

My organization requires that all web traffic, even within the organization, use HTTPS and LDAPS authentication.

How would we achieve a secure OL Connect Automate / Node Red installation on an internal server such that the sessions to create flows are authenticated against our Domain Server(s) using LDAPS, port 636, and the session encrypted via HTTPS?

2

Bump. Any feedback on this? I’m trying to plan ahead and anticipate the move to Automate, but if the installation doesn’t support LDAPS and HTTPS then, sadly, it’s a non-starter.

3

Hi TGreer,

Quick question. Does the following related to the flow editor itself?
“sessions to create flows are authenticated against our Domain Server(s)”

We have an internal document describing how to protect the editor using SAML, OIDC & OAUTH. This will be added to the online documentation we are setting up. Will check if I can share the current info.

Erik

4

Yes, the flow editor itself requires authentication, using LDAPS, to our DS. The session(s) must also be HTTPS.

5

Any updates on this request?

6

Hi Tgreer,

I’ve extracted the topic from our oncoming Online Help (not public yet). Although we currently do not have an example for LDAP specifically it may provide useful information. I’ve created a ticket for the team to provide the instructions on how to setup things for LDAP, this will be added to the Online Help.

Erik

Protecting Node-RED.pdf (123.5 KB)

7

My organization requires LDAPS, the secure version. But I’ll check out the documentation, thank you for the link!

8

Bumping this question: when will LDAPS authentication be supported by OL Connect Workflow / Node.JS input? Or in OL Automate, since that was my original query?

9

TGREER,
Based on what I see in Jira, it is intended for 2026.1 if all goes as planed. Of course it could change!
Thanks

1 Like