Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support multiple SECC leafs for each EVSE of a charging station #68

Open
AssemblyJohn opened this issue Apr 30, 2024 · 0 comments
Open
Assignees

Comments

@AssemblyJohn
Copy link
Collaborator

AssemblyJohn commented Apr 30, 2024

Describe the problem

According to the OCPP2.0.1 specification we have to support multiple SECC leaf certificates for a charging station. At the moment the concept supports having multiple leaf certificates installed, but they are not dedicated to individual EVSEs.

When a CSR is generated, the Common Name (CN) field of the certificate shall be set to the ISO15118SeccId of the EVSE. In case of multiple EVSEs per charging station, this variable is unique for every EVSE. The CN is already an argument of the generate_csr function so this does not need to change.

The get_key_pair function does currently return the most recent certificate that is already valid and the respective key, without differentiating between the EVSE it was issued for.

Describe your solution

Options:

  1. Extend the get_key_pair function by an argument that represents the ISO15118SeccId.
  2. Seperate the get_key_pair function into two different functions: One for CSMS and one for V2G.

The key pair that is returned shall match this id.

Additional context

The trigger of generating the CSR is outside the scope of this library. Libraries like libocpp need to take care of renewing certificates in case they are expired and calling the generate_csr function with the correct arguments

@AssemblyJohn AssemblyJohn self-assigned this Apr 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant