...
| Note |
|---|
This feature has changed since present version! |
In previous PrivateServer releases you had to paste private key, certificate and possibly CA root to add a new Certificate and thus validate your hostname for the services exposed. That method obliged Service Administrators to directly deal with Certificate's Private Key, which is kind of sensitive information. Also keypair creation and management had to take place somewhere else outside PrivateServer and then imported. As an improvement of both security and usability since Since present version you can (and must) deal with Certificates directly on PrivateServer: you can create CSR on PrivateServer with automatic sdlfkslf. Thisi is why Certificate Creation has been split in two steps:
- New Key and CSR creation
- Actual New Certificate upload
New Key and CSR
So first of all you start by creating a CSR: click on the New Key and CSR link above the certificate table.
...
A warning confirming creation and a new row in TLS Keypair list shows generation process has been successful.
| Notetip |
|---|
Using this new Certificate creation process you no longer don't have to deal directly with Private Keys. |
...
Anyway you need to Download CSR before you're done with Certificate creation, so use first link shown in detailed view
| Xref | ||
|---|---|---|
|
New Certificate upload
Once you have your CSR you just follow instructions by CA of your choice to obtain a new Certificate. As it's done, you can get back to form in
| Xref | ||
|---|---|---|
|
...