Add support for HTTP Basic Authentication #123
Merged
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.
This change adds support for HTTP Basic Authentication to the OCPP-J
client, via two additional JSONConfiguration parameters for username and
password. When both are set, the HTTP Basic Authentication header will
be added to the websocket connect request.
Note that HTTP Basic Authentication transmits username and password
without encryption, so for secure communication, it must be used within
a trusted channel, e.g. a secure websocket connection (WSS) or maybe an
encrypted VPN connection.
This change has originally been prepared by our former colleague:
rtzll@8652108
and has successfully been tested in a plugfest.