How to setup login/password in the node-red-contrib-ocpp node 'Server'.

[MikePhoenixAutomation]

I try to use the node-red-contrib-ocpp
Actually, i have a charge point that tries to communicate with the OCPP Server, but I only get an ONLINE and an OFFLINE message, boot notification, time sync, ...
I am surprised, because in the help of this contrib, there is a possibility to define login/password on the Server node, but in the really available node, only the path is modifiable, the version of OCPP, but I could not find the way to define login and password (for the Server)
I hop you can help me, because i am actually stuck to continue my dev.
Thanks

[MikePhoenixAutomation]

nobody to answer?

[bnystrom]

Hi Mike,

For the OCPP 1.6j node server (CS Server node), you can send it a message like this:

msg = {
   "payload": {
      "command": "LOCAL_SET_ALL_AUTH_EVSES",
      "data": {
          "EVSE1":"password1234",
          "EVSE2": "anotherpassword"
       }
    }
}

The ability to add the password in the server node is currently only in the OCPP 2.x implementation of the nodes (node-red-contrib-ocpp2)

Be sure you are using the latest version of these nodes, as an earlier version had a bug that prevented EVSE without passwords from connecting. That is resolved in the latest update.

[MikePhoenixAutomation]

hi bnystrom.
Where must I send this message to?
Onto the CS Request JSon?

In my case, the OCPP Charger mus be configured with Login and PAssword.
I suupose what you wrote as EVSE1, EVSE2 is only the name of the Charger, right?
Where can I make a link with a user, using the password to connect to the OCPP server?

[MikePhoenixAutomation]

I made a test, and it seems that I receive datas from my EV chargers. But, it seems that the transaction is accepted by default. What can I do to check, for example, the TAG ID that has been scanned before sending the 'Accepted' answer?

[Paul-Reed]

The ability to add the password in the server node is currently only in the OCPP 2.x implementation of the nodes (node-red-contrib-ocpp2)

That's unfortunate, because I've just fitted a new charger, but it's OCPP v1.6 compliant and not v2.
I was hoping to use a cloud based server, and therefore keep things nice & secure...

[bnystrom]

Mike, You inject the message I gave into the "CS Server" node itself, not the "CS Request JSON" node. And yes, it's an array of key/value pairs, with key="ChargeBoxId" and value="password". If you pass in ``` [ { "EVSE1": "mypassword" } ] ``` when EVSE1 tries to connect, the connection must contain a password of "mypassword", or the "CS Server" node will reject the connection. Paul-Reed, Maybe I wasn't clear. The ability to enter password information directly into the "Server" node ("CS Server" node in 1.6, "CSMS" node in 2.x) settings dialog is only available in the OCPP 2.x nodes. You can inject my example payload into the OCPP 1.6 "CS Server" node (via code/flow). There just isn't a settings dialog for the "CS Server" node that allows doing that. I use the node-red-contrib-ocpp nodes all the time to set up password protection to allow/disallow EVSEs to connect to the CS Server. One other point: the password support is only available for the OCPP 1.6j (json) setup. It doesn't work for if you are using OCPP 1.6 SOAP. Best Regards Bryan Nystrom

…

On Fri, Jun 13, 2025 at 3:00 AM Paul ***@***.***> wrote: *Paul-Reed* left a comment (argonne-vci/node-red-contrib-ocpp#94) <#94 (comment)> The ability to add the password in the server node is currently only in the OCPP 2.x implementation of the nodes (node-red-contrib-ocpp2) That's unfortunate, because I've just fitted a new charger, but it's OCPP v1.6 compliant and not v2. I was hoping to use a cloud based server, and therefore keep things nice & secure... — Reply to this email directly, view it on GitHub <#94 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AANQYL5LYRCHQZC6CRIDMRD3DKAKNAVCNFSM6AAAAAB5V4VUAKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSNRZGQ2TINBSGA> . You are receiving this because you commented.Message ID: ***@***.***>

[Paul-Reed]

You can inject my example payload into the OCPP 1.6 "CS Server" node (via
code/flow).

Hi Bryan, sorry, but what I'm finding confusing is that the OCPP 1.6 "CS Server" node does not have an input pin, therefore I'm not seeing a way to inject it 😒

Regards
Paul

[bnystrom]

Paul-Reed, You are absolutely right. I guess I forget my own code after a while. My apologies. You inject that code into the "CS request JSON" node. It ends up passing it to the server node. If you take a look at the "help" for that node, the "LOCAL_SET_ALL_AUTH_EVSES" is even mentioned there. Sorry about the confusion (I was the one confused) Best Regards Bryan Nystrom

…

On Sat, Jun 14, 2025 at 7:17 AM Paul ***@***.***> wrote: *Paul-Reed* left a comment (argonne-vci/node-red-contrib-ocpp#94) <#94 (comment)> You can inject my example payload into the OCPP 1.6 "CS Server" node (via code/flow). Hi Bryan, sorry, but what I'm finding confusing is that the OCPP 1.6 "CS Server" node does not have an input pin, therefore I'm not seeing a way to inject it 😒 Regards Paul ocppserver.png (view on web) <https://github.com/user-attachments/assets/019b7b53-a7dc-40ee-9859-e50bc3ec32a4> — Reply to this email directly, view it on GitHub <#94 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AANQYLYXNIA6LDIJN7IEP633DQHGPAVCNFSM6AAAAAB5V4VUAKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSNZSG4ZDENJQGE> . You are receiving this because you commented.Message ID: ***@***.***>

[MikePhoenixAutomation]

I made a test, and it seems that I receive datas from my EV chargers. But, it seems that the transaction is accepted by default. What can I do to check, for example, the TAG ID that has been scanned before sending the 'Accepted' answer?

Hello.
What can I do so that after a tag is read and sent to the OCPP server, the transaction is not accepted directly, but controlled by an external event?

[bnystrom]

Mike, Are you referring to the idTag info sent with a transaction request? I ask because this thread was discussing the ability to accept/deny an EVSE to be allowed to talk to the backend (CSMS). Tag info for transactions is sent with a "StartTransaction" request or "AuthorizeTransaction" request. You would need to pass along the tag info to your external event and decide if you will respond with a status of "Accepted","Blocked","Expired", or "Invalid". The node-red server node doesn't automatically accept transaction requests. That's up to the flow to respond appropriately. The example flows probably do just accept everything. They are only examples and you should write your own logic for that. Best Regards Bryan Nystrom

…

On Mon, Jun 16, 2025 at 1:29 AM MikePhoenixAutomation < ***@***.***> wrote: *MikePhoenixAutomation* left a comment (argonne-vci/node-red-contrib-ocpp#94) <#94 (comment)> I made a test, and it seems that I receive datas from my EV chargers. But, it seems that the transaction is accepted by default. What can I do to check, for example, the TAG ID that has been scanned before sending the 'Accepted' answer? Hello. What can I do so that after a tag is read and sent to the OCPP server, the transaction is not accepted directly, but controlled by an external event? — Reply to this email directly, view it on GitHub <#94 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AANQYLZN5ETBZOMVISQXZ4L3DZP6HAVCNFSM6AAAAAB5V4VUAKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSNZVGI3DEMZXGM> . You are receiving this because you commented.Message ID: ***@***.***>

[MikePhoenixAutomation]

Hi Bryan. As you thought, i use the example. But I did not find the node that accepts everything. Where must I look? De : Bryan Nystrom ***@***.***> Envoyé : lundi 16 juin 2025 17:23 À : argonne-vci/node-red-contrib-ocpp ***@***.***> Cc : Michel Schneider ***@***.***>; Author ***@***.***> Objet : Re: [argonne-vci/node-red-contrib-ocpp] How to setup login/password in the node-red-contrib-ocpp node 'Server'. (Issue #94) ***External email! Do not click links or open attachments unless you recognize the sender and know the content is safe.*** [https://avatars.githubusercontent.com/u/1772591?s=20&v=4]bnystrom left a comment (argonne-vci/node-red-contrib-ocpp#94)<#94 (comment)> Mike, Are you referring to the idTag info sent with a transaction request? I ask because this thread was discussing the ability to accept/deny an EVSE to be allowed to talk to the backend (CSMS). Tag info for transactions is sent with a "StartTransaction" request or "AuthorizeTransaction" request. You would need to pass along the tag info to your external event and decide if you will respond with a status of "Accepted","Blocked","Expired", or "Invalid". The node-red server node doesn't automatically accept transaction requests. That's up to the flow to respond appropriately. The example flows probably do just accept everything. They are only examples and you should write your own logic for that. Best Regards Bryan Nystrom

On Mon, Jun 16, 2025 at 1:29 AM MikePhoenixAutomation < ***@***.***<mailto:***@***.***>> wrote: *MikePhoenixAutomation* left a comment (argonne-vci/node-red-contrib-ocpp#94) <#94 (comment)> I made a test, and it seems that I receive datas from my EV chargers. But, it seems that the transaction is accepted by default. What can I do to check, for example, the TAG ID that has been scanned before sending the 'Accepted' answer? Hello. What can I do so that after a tag is read and sent to the OCPP server, the transaction is not accepted directly, but controlled by an external event? — Reply to this email directly, view it on GitHub <#94 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AANQYLZN5ETBZOMVISQXZ4L3DZP6HAVCNFSM6AAAAAB5V4VUAKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSNZVGI3DEMZXGM> . You are receiving this because you commented.Message ID: ***@***.***<mailto:***@***.***>>

— Reply to this email directly, view it on GitHub<#94 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ALN7Z5VGAZC3O2TXCDCA22L3D3OMZAVCNFSM6AAAAAB5V4VUAKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSNZXGA3TINBUHE>. You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>> Vous trouverez les informations sur le traitement de vos données personnelles dans notre politique de confidentialité. Veuillez consulter notre site web, rubrique [Protection des données].

[bnystrom]

Do your own "Generic Status="Accepted" node for both "Authorize" and "StartTransactions" from the switch node.

[Paul-Reed]

Hi Bryan, tried the above, but it will not auth when using the correct username/password.
Firstly, I contacted the charger manufacturer and obtained the default auth username/password, then checked it by inspecting the the WebSocket handshake to see the Authorization header, decoded it as a Base64-encoded username and password, and the result was the same, so I'm happy that I have the correct details.
Then injected the command into the CS Requests JSON node;

{
    "command": "LOCAL_SET_ALL_AUTH_EVSES",
    "data": {
        "BS542T543": "73654322"
    }
}

Restarted the server, and the ocpp node status changed to 'disconnected from BS542T543', and would not connect.
I could only get reconnected by re-injecting the above again with a blank password.

I'm connecting charger/CS via ws:// and not wss://.

Any thoughts please?

[bnystrom]

Paul, Strange. I'll try setting up one of our EVSEs with the same password and give it a try. I'll let you know how it goes. Best Regards Bryan Nystrom

…

On Wed, Jun 18, 2025 at 2:30 PM Paul ***@***.***> wrote: *Paul-Reed* left a comment (argonne-vci/node-red-contrib-ocpp#94) <#94 (comment)> Hi Bryan, tried the above, but it will not auth when using the correct username/password. Firstly, I contacted the charger manufacturer and obtained the default auth username/password, then checked it by inspecting the the WebSocket handshake to see the Authorization header, decoded it as a Base64-encoded username and password, and the result was the same, so I'm happy that I have the correct details. Then injected the command into the CS Requests JSON node; { "command": "LOCAL_SET_ALL_AUTH_EVSES", "data": { "BS542T543": "73654322" } } Restarted the server, and the ocpp node status changed to 'disconnected from BS542T543', and would not connect. I could only get reconnected by re-injecting the above again with a blank password. Any thoughts please? — Reply to this email directly, view it on GitHub <#94 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AANQYL6RZO646HWSSA5OYHL3EG435AVCNFSM6AAAAAB5V4VUAKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSOBVGQ3DCNJXGU> . You are receiving this because you commented.Message ID: ***@***.***>

[bnystrom]

Paul,

I set up one of the commercial EVSEs we have (FractalEV) with the same password and had no issues.

If you stop Node-RED, then set up an environment variable named "DEBUG" with "anl:ocpp:*" and you look at the Node-Red logs, it will tell you what the password is it checking against. Here is a snippet of the NR log file with DEBUG enabled. I changed the last number of the password you gave me from a 2 to a 3 so that it would fail the connection. This is what you get in the logs:

2025-06-19T18:49:22.675Z anl:ocpp:cs:server Got A connection from: Fractal0001
2025-06-19T18:49:22.675Z anl:ocpp:cs:server Setting up callback for Fractal0001::REQUEST
2025-06-19T18:49:22.675Z anl:ocpp:cs:server Websocket connection to : Fractal0001
2025-06-19T18:49:22.676Z anl:ocpp:cs:server Try to Auth: Fractal0001 = Fractal0001 with p/w 73654323
2025-06-19T18:49:22.676Z anl:ocpp:cs:server NOT Authorized

Maybe the debug log will help trace what is going on. Perhaps the password being sent isn't what you think it is.