Establishing an unsecured communication channel with Softdpac on a Ubuntu virtual machine.

[NascimentoOliveira]

I'm starting a SofdPAC in an Ubuntu virtual machine. However, I need to create an unsecured communication channel, and I would like to use port 51499 for this purpose. The problem is that I can't find which parameter to modify or the configuration in order to create this channel, since the default setup uses port 51433 and creates a secured channel.

The SoftdPAC version is 24.0.24178.

The EAE version used to access the SofdPAC is 24.0

[theo.bagieu]

Hi @NascimentoOliveira 

Can you precise which communication you're expecting to be unsecure : Communication between softdpac and Buildtime (EAE Studio Engineering Tool) ? a communication protocol ? Deployement ?

[NascimentoOliveira]

Hi @theo.bagieu.

It is a Deployment communication.

[KarimBenameur]

Hi, 

We are not officially supporting unsecure communication but ...you can try that for test purpose only:

- Start manually soft dpac by using startSoftdPAC.sh script

 Note that this will be deprecated soon and it is not recommended to use that script.
- Manage your Soft dPAC docker Linux as a Soft dPAC Windows.
Refer to Soft dPAC user manual following chapters

Configure Soft dPAC for Windows for Non-Secure Communications

I have copy/paste user manual for 24.1

Configure Soft dPAC for Windows for Non-Secure Communications

Soft dPAC for Windows supports only non-secure communications. By default, EcoStruxure Automation Expert - Buildtime configures Soft dPAC controllers for secure communications. Thus, you need to configure each Soft dPAC for Windows controller for non-secure communications.

If you do not configure a Soft dPAC for Windows controller for non-secure communications, it will not be possible to login to the controller from EcoStruxure Automation Expert - Buildtime.

Prerequisites

Before performing the following tasks:

• Verify that your solution contains the SE.DPAC library reference.

• Disable the host firewall when performing the following tasks. When the tasks are completed, re-enable the firewall.

1. In the Physical Devices Editor

Configure the host device:

NOTE: When the Soft dPAC manager service is activated, it is not possible to create Soft dPAC runtime services in the Runtimes Editor.

1. Add a host device - for example a workstation - to the physical devices network.

2. Select the host device (and not its NIC) to display the Properties tab. (If necessary, select View > General Pads > Properties in the main menu.)

3. In the Runtimes row, click the ellipsis (...) to open the Runtimes Editor.

4. Click Add then select Soft dPAC. A new runtime is created and displayed in the right pane.

   NOTE: After the Soft dPAC manager service is activated, It is not possible to create Soft dPAC runtime services in the Runtimes Editor (accessed by clicking the ellipsis (...) at Runtimes Settings > Runtimes).

5. Click OK to close the Runtimes Editor.

6. Click on the NIC (i.e. the Ethernet port) on the host device to display its properties.

7. Configure its Name, IP Address and Logical network properties.

   NOTE: The IP Address is the actual IP address of the host device where the Soft dPAC is running.

2. In the Logical Devices Editor

Configure the security settings of the logical device:

1. Open the Logical Devices editor in EcoStruxure Automation Expert - Buildtime.

2. Open the Properties pad ( View > General pads > Properties) if it is not already open.

3. In the Logical Devices editor, select the Soft dPAC for Windows controller in the list of logical devices to display its properties.

4. In the Properties pad configure the following settings:

   • Change the Security Settings > Use Encryption setting to False.

     NOTE: A message asks you to confirm changes. Click I confirm to continue.

   • Change the Runtime Configuration > Communication > Endpoint > WebSocket > Encryption setting to False.

     NOTE: A message opens reminding you to edit the Use Encryption setting (which you did, above) and to re-deploy the device configuration. Click OK to continue.

   • Press Ctrl + S (or the main toolbar Save command) to save your changes.

5. If you have not yet done so, in the Logical Devices editor, associate the Soft dPAC logical device with a Physical Device.

6. Confirm that the physical device hosting the Soft dPAC is a Windows™ device, which requires a non-secure connection, and not a device (e.g., a Linux device) that supports only secure connections.

7. In the Deploy and Diagnostic pad, you can now proceed to Compile, Login to the device, and Deploy the device configuration.

8. Once deployed, if no OPC UA communication can be established, confirm that the real physical device is configured with an unsecure connection for OPC UA.

3. In the Deploy and Diagnostic Editor

Deploy and run the Soft dPAC:

1. Select Action > Login.

2. After login, select Action > Compile.

3. Once compiled, select Action > Device configuration > Deploy Device Configuration. The Deploy Device Settings dialog opens, presenting the options:

   • Deploy and Restart

   • Deploy only

   • Cancel

4. Select Deploy and Restart.

5. After all device configuration is complete, deploy the configuration to runtime by selecting Action > Deploy > Deploy.

6. After deploy is complete, you can run the device by selecting Action > Device action > Run.

   The Soft dPAC runs in unsecured mode.

[NascimentoOliveira]

When I try to initiate a sofdPAC by running  startSoftdPAC.sh, I received this error message: 

However, I configured the daemon file as this installation note demands: