sdn certs module

BenjiReis

Hello,

There's 2 ways to use the SDN controller as for the certificates:

You can provide the vertificate yourself, if you arleardy have certificates, in this case you need to provide a path to the certificate directory in the plugin configuration and make sure that there is client-cert.pem, client-key.pem and ca-cert.pem in the directory
If you don't have certificates, the SDN controller can create them, but they will be self signed. To do so you just leave the certificate configuration path empty.

Is that clear?

Regards,
Benjamin

adriangabura

Well the autogenerator dosn't work when you build from source. Apparently it lacks the said module. So how do I install the node-openssl-cert module so it works in yarn?

BenjiReis

That's strange, did you follow the official guide to build xen-orchestra from sources?
All dependencies should be installed.

BenjiReis

I've just tried locally from sources and everything went fine.

Can you try to call yarn and then yarn build at the root of xen-orchestra repository?

Thanks

adriangabura

Ok, I'll try later today, thanks for the answers!

adriangabura

Ok, I tried again, same thing. So I run sudo yarn start in xo-server directory. And I watch the logs while I try to use the certs autogenerator. This is what I get:

2019-07-29T18:20:46.778Z - xo:xo-server:sdn-controller - [DEBUG] No cert-dir provided, using default self-signed certificates
2019-07-29T18:20:46.780Z - xo:xo-server:sdn-controller - [DEBUG] No default self-signed certificates exists, creating them
2019-07-29T18:20:47.611Z - xo:xo-server:sdn-controller - [ERROR] Error while generating CA private key
{ error: false }

As I said it's not a problem per se, I'm just trying to figure out out of curiosity why it doesn't work.

olivierlambert

It could be something linked to your environment because it works on our side

But why? Hard to tell. That's exactly the main reason why we do pro support only on a controlled environment (XOA, Xen Orchestra virtual Appliance), because otherwise you could have tons of external factors that make it fails.

Double check you are on latest master commit, ideally clone it from scratch and rebuild everything. Check your Node and npm version.

BenjiReis

Hi,

I've managed to reproduce you're error. It's not a build issue.
A fix is coming right away, I'll post it here once it's merged into master so you can get it.

Thanks for the report.
Regards

olivierlambert

@BenjiReis do you know the problematic commit in question?

BenjiReis

Yes it's 5396b90695fbe2c7a5f56d72a94a208517b2d517 but its not its only modification so it can't just be reverted.
This is a really quick fix I can push a branch today and it can be used waiting for the merge.

BenjiReis

Hi!

The fix is available on master.
You should be able to generate certificate now.

olivierlambert

Well done

adriangabura

Great! Your team proves just how legendary it is once again! Thank you!