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.

Sign up for GitHub

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

Jump to bottom

Add Certificate Management #29

Closed
1 of 4 tasks
jeremypoulter opened this issue Oct 1, 2019 · 3 comments · Fixed by #695
Closed
1 of 4 tasks

Add Certificate Management #29

jeremypoulter opened this issue Oct 1, 2019 · 3 comments · Fixed by #695
Assignees
@jeremypoulter
Labels
enhancement New feature or request

Comments

@jeremypoulter
Copy link
Collaborator

jeremypoulter commented Oct 1, 2019 •
edited
Loading

  • Disable root certificate validation per client
  • Update root certificates
  • HTTPS server certificate/private key (GUI)
  • MQTT client certificate/private key
@jeremypoulter jeremypoulter mentioned this issue Oct 1, 2019
Closed
@jeremypoulter jeremypoulter added this to the v3.0.0 milestone Oct 23, 2019
@jeremypoulter jeremypoulter removed this from the v3.0.0 milestone Dec 17, 2019
@jeremypoulter jeremypoulter mentioned this issue Jun 7, 2020
Closed
@glynhudson glynhudson added the enhancement New feature or request label Jun 18, 2020
@chris1howell
Copy link
Member

Does this issue include client certificates?

Client certificates are required for MQTT for use on Amazon AWS, Google Cloud, Microsoft Azure, etc.

Client Certificates are also required for OCPP 1.6J an 2.0 Security Profile 3 TLS with Client side certificate.
https://www.openchargealliance.org/uploads/files/OCPP_1.6_Security_Whitepaper_-_2018.zip

@Laikulo
Copy link

Laikulo commented Oct 24, 2021

Does this also include managing/replacing the root CA bundle? I'm currently using a patcheset to add in my private CA:

https://github.com/ArchLayperson/ESP32_WiFi_V3.x/tree/haunhaus-patches

https://github.com/ArchLayperson/ESP32_WiFi_V3.x/tree/haunhaus-ca

@jeremypoulter
Copy link
Collaborator Author

Yes, the intention is to allow the root CAs to be updated via the API/GUI

@fhteagle fhteagle mentioned this issue Oct 25, 2022
Closed
This was referenced Jun 1, 2023
Open
Open
Open
@jeremypoulter jeremypoulter self-assigned this Jun 14, 2023
@jeremypoulter jeremypoulter moved this from Todo to In Progress in OpenEVSE v5.1 release Jul 27, 2023
@jeremypoulter jeremypoulter mentioned this issue Jul 27, 2023
Merged
@jeremypoulter jeremypoulter mentioned this issue May 21, 2024
Open
@github-project-automation github-project-automation bot moved this from In Progress to Done in OpenEVSE v5.1 release Aug 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jeremypoulter jeremypoulter

Labels
enhancement New feature or request
Projects
OpenEVSE v5.1 release
Status: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Certificate management OpenEVSE/openevse_esp32_firmware
4 participants
@glynhudson @chris1howell @Laikulo @jeremypoulter