Credentials module

Plugsurfing will assume the CPO role during the handshake, with the CPO name Plugsurfing and the country_code "DE" and party_id "8PS". Example:

  "roles": [
            {
                "role": "CPO",
                "business_details": {
                    "name": "Plugsurfing"
                },
                "party_id": "8PS",
                "country_code": "DE"
            }
        ]

Plugsurfing does not use the HubClientInfo module.

Why not the entire roles list?

By only sharing Plugsurfing in the roles list, we avoid frequent handshake updates when CPOs are added or removed to the Plugsurfing network. We also avoid an unpractical too long list of CPOs in the handshake which it is not intended for, and manual work for the EMP to allow or deny new CPOs as the Plugsurfing network grows. Finally, the roles list would still not tell the whole truth since there are often sub-CPOs behind a connection where the CPO communicates with one party ID but share the real operator of the location in the locations object.

How do I know which operators are part of the solution?

Through a location pull, in the locations object the EMP will always receive:

• Country code + party ID
• Operator name populated in the Operator field

We will always share the country code + party ID of the connection owner as we have received it through OCPI, and in the Operator field you will receive the Operator name that the CPO has shared. Through this information you would know which CPOs are part of the network, and you could use the Operator name to get the details of sub-CPOs that are behind a connection.

If a CPO is removed, the locations belonging to this CPO will no longer be part of the location pull.