Final MRE script; includes certificate configuration #29
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Shankari <k.shankari@ee.doe.gov>
Signed-off-by: Shankari <k.shankari@ee.doe.gov>
It ends with instructions to `docker exec` into the container and run the startup command. Note that the command is currently expected to fail. This should allow the EVerest OCPP implementers to reproduce the error and then investigate it while still "logged in to" the container. Signed-off-by: Shankari <k.shankari@ee.doe.gov>
shankari
changed the title
|
Test results (release |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Simple MRE that showcases the current failure in configuring SecurityProfile: 2
#25
The script ends with instructions to
docker execinto the container and run the startup command. Note that the startup command is currently expected to fail with the error (get_issuer_key_hash must only be used on self-signed certs) #25 (comment)Running after
docker execshould allow the EVerest OCPP implementers to reproduce the error and then investigate it (potentially by turning on debug logging or by examining the certificates) while still "logged in to" the container.