Miscellaneous¶

Optional: Change Backend Database to MS SQL Server¶

You can change your backend database from the default PostgreSQL to MS SQL server.

When you change the backend database, you have the option to migrate the existing data or start afresh. If you start afresh, your existing data in PostgreSQL database will not be migrated.

To change the backend database from the default PostgreSQL to MS SQL Server, follow the steps below:

Stop the EPM Service from services.msc (on the machine in which Securden is installed).
Navigate to /bin folder and execute "ChangeDatabase.exe" and in the GUI, supply SQL instance name, database name, username, and password to connect to the database.
Click on Save to change the database without database migration. Click on Migrate to migrate the existing data from the PostgreSQL database to MSSQL database.
Now, start the the EPM Service from services.msc (you may ignore the other service named Securden Web Service, which is automatically taken care of)
Connect to the web interface https://<host-name>:5151
Clear browser cache

Replace Self-signed Certificate¶

By default, Securden comes bundled with a self-signed certificate. You can add your own Certificate Authority signed certificate by following the steps below.

Securden requires the certificate and the private key separately. If you have the CA signed certificate in .pfx format, follow the steps below:

Download OpenSSL (if you don't have that installed already).

You can download OpenSSL from here. Make sure the bin folder under the OpenSSL installation is included in the PATH environment variable.
Copy your certificate (e.g., .pfx) and paste it in the system from where you can execute OpenSSL.exe.

The *.pfx file is in PKCS#12 format and includes both the certificate and the private key.

Run the following commands to export the private key.

openssl pkcs12 -in <CERTIFICATE>.pfx -nocerts -out securden-key.pem -nodes

openssl rsa -in securden-key.pem -out securden-key.pem

Run the following command to export the certificate.
```
openssl pkcs12 -in <CERTIFICATE>.pfx -nokeys -out securden-cert.pem 
```
Note

In the above commands, substitute the ‘<CERTIFICATE>.pfx’ placeholder with the actual file name of the certificate obtained from your certificate authority.

For instance, if the certificate name is testsite.pfx, then the above command would look like:
```
openssl pkcs12 -in testsite.pfx -nokeys -out securden-cert.pem 
```
Once you execute the above steps, you will get an SSL certificate and a private key.
Copy and paste the securden-cert.pem and securden-key.pem files in the /conf directory of the Securden installation folder.
In services.msc, restart Securden EPM Service.

Troubleshooting tip

In some cases, the PEM file does not contain the private key, and this brings up the error - Expecting: ANY PRIVATE KEY. Ensure that you have the key along with the certificate.
Ensure that the .pfx file is in PKCS#12, as this format holds both the certificate and key in it. Hence, we recommend the certificate be exported in PKCS#12 format to extract the certificate and key separately.

If the issue persists, you may write to us at support@securden.com