Closed fulup-bzh closed 8 months ago
So Hubject is providing the PKI capabilities for our Plug & Charge functionality. By default MaEVe is configured to use the Hubject test environment https://hubject.stoplight.io/. All the documentation required to use the Hubject test environment is available there. MaEVe automatically retrieves the token needed to make API calls to this environment. This is fine for local testing.
For real-world PnC implementations, you would need to enrol with Hubject at which point you would receive your own API token. You would then provide this to MaEVe using an environment variable: https://github.com/thoughtworks/maeve-csms/blob/main/manager/config/README.md#environment-token-auth-service.
Thank you very much for your quick response. I will look deeper into https://hubject.stoplight.io
We are working on Tux-EVSE a charger open source modular stack in Rust. Obviously an OCPP backend is required for test. I originally though about using ocpp-rpc, but maeve-csms that I discovered throught a post on Everest mailing list is far more complete and hopefully will allow us to test ISO15118-2/20 with OCPP-201.
Question about maeve-csms:
Sorry, I missed the follow up on this. There is currently no graphical user interface. All admin operations are performed using the API. MaEVE supports a number of different extensions for PnC over 1.6 including the OCA extensions.
I would be please to get some explanation on how/when 'hubject.com' enter in the process and how we may use it to test plug&charge.
Looks like manager/config.toml already have an authorization token.