Use security profiles with virtual machines and stay connected #169
Unanswered
bstampfl22
asked this question in
Q&A
Replies: 5 comments 1 reply
-
|
I still have the problem. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Hi, Sorry for the delay, I forgot to respond to your message. In these example, the charge point first connects to the central system using security profile 0 on port 8080. Once connected, the central system reconfigures the charge point to use security profile 1 (new URL + authorization key + security profile key). The charge point then disconnects itself automatically to reconnect to the new URL on port 8081 using the new security profile. Once reconnected, the central system reconfigures the charge point to use security profile 2 (new URL + server CA certificate + security profile key). The charge point then disconnects itself automatically to reconnect to the new URL on port 8082 using the new security profile. Once reconnected, the central system reconfigures the charge point to use security profile 3 (new URL + client certificate + security profile key). The charge point then disconnects itself automatically to reconnect to the new URL on port 8083 using the new security profile. Once reconnected, the central system send a few requests added by the OCPP 1.6 security white paper to the charge point : GetLog, GetInstalledCertificateIds, InstallCertificate and SignedUpdateFirmware. |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Here are the logs that you must have on the central system side : |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Here are the logs that you must have on the charge point side : |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
So this is normal and expected that during the startup of the example you see some disconnections, but once the entire process implemented in this example has been executed, the connection should be stabled and should use security profile 3. How are you implementing your central system with security profiles? Regards. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
Thanks for your reply. Okay, I understand. I had already seen all the disconnects and startups before. I only have the problem that if I change the URL from 127.0.0.1 to something different with 192.X.X.X:, the whole process runs through (i.e. all startups and disconnects), but at the end, when it should actually be running, the connection between CS and CP does not remain.
I only use your implementation of the CS in a virtual machine |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello,
I use version 1.4.0 and 1.4.1 and try to connect the security_centralsystem and the security_chargepoint. Sometimes there is a connection, but only for a few seconds. Is there a way to make the connection permanent?
Am I missing a setting or something else? I have followed the installation guide and also change the corresponding urls each time.
I have installed the VM that acts as a server (central system) with Debian 12 and the other VM (Chargepoint) uses Kali Linux. Both VMs are on different computers
I have already tried to use both elements (Centralsystem & Chargepoint) in the same VM or on the same computer. However, even there I cannot get a permanent connection between the CS and the CP with security profiles.
Beta Was this translation helpful? Give feedback.
All reactions