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

Optionally disable XML signatures #11

Closed
Sevenstax opened this issue Aug 29, 2017 · 4 comments
Closed

Optionally disable XML signatures #11

Sevenstax opened this issue Aug 29, 2017 · 4 comments

Comments

@Sevenstax
Copy link

Hi, you did some great work with this project!

We have a V2G stack and want to use this server to test our implementation. I got it working but I had to disable the use of XML signatures because our stack in it's current version is missing the XML signature parsing support.

Is there a possibility that the use of XML signatures could be optionally disabled in the config file of the server?

@MarcMueltin
Copy link
Contributor

MarcMueltin commented Aug 29, 2017

Hi there,

glad you are working with RISE V2G. :)
Well, if you do not want to use XML signatures, you can set the property "TLSSecurity" in the EVCCConfig.properties to "false". This way you will have a communication via TCP, not secured via TLS. In pure TCP communication, there are no XML signatures applied.

However, if you do use TLS, then XML signatures are mandatory. There is no property to disable XML signatures (as this would not be standard conform).

Does that help you?

@Sevenstax
Copy link
Author

Thank you for the information.

If it's violating the standard then it doesn't make sense to optionally disable it.

@MarcMueltin
Copy link
Contributor

One side note:
To be completely correct: You could use TLS with EIM (External Identification Means). Here, you don't use certificates or digital XML-based signatures. So you can use TLS without using XML signatures. For this, the SECCConfig.properties file needs to set the property "SupportedPaymentOptions" to "ExternalPayment" only.

However, if you use Plug & Charge (property "SupportedPaymentOptions" is set to "Contract" as well), then XML signatures and X.509 certificates are mandatory.

@Sevenstax
Copy link
Author

Sevenstax commented Aug 31, 2017

I think this is exactly what we need for testing, until we finish our implemenatation of the XML signatures.

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