This repository has been archived by the owner on Jan 2, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 72
Configuring and using SSL Certificates
Tayane Fernandes edited this page May 8, 2017
·
2 revisions
A LEAP Provider will usually have those two endpoints:
-
LEAP Web
- This is an interface for creating and managing accounts on provider. It usually runs on port 443.
- The SSL certificate and available services are listed on a provider.json file.
- On https://yourdomain.org/provider.json you'll see that it points to where the LEAP API certificate and services are:
"ca_cert_uri": "https://yourdomain.org/ca.crt", -
LEAP API (+other services)
- Those services are accessed using a Pixelated or Bitmask client. It usually runs on port 4430 with other ports and services.
- Browsers can't view it you can check accessing https://api.yourdomain.org:4430
- Official certificate
- Leap CLI support certificates generations using Let's Encrypt. To generate certificates for your provider run:
leap cert renew dev.pixelated-project.org leap deploy your-node
You might also need to add your LEAP provider ssl certificate to pixelated manually for now, with the following steps:
The easiest way to get this is downloading if from https://your.provider.org/ca.crt.
Rename the certificate based on your provider domain name like this your.leapprovider.org.crt and put it into services/pixelated/certificates/.