07-05-24 03:19 PM
When installing and performing the initial configuration of Decipher, many customers do not do the necessary tasks to harden the security of the environment. This guide goes over the salient points required to make your Decipher installation as secure as possible.
Firstly, your admin password is probably set to the default “admin” password.
The password can be changed only in the Decipher website. To do this:
The default account used (actually recommended in the installation) by the Automated Client is the GeneralUser account. This has a default password of “user” (again, recommended by the installation). If left as “GeneralUser \ user” it can be security risk.
To change the account password, like the admin password (above) this has to be done on the Decipher Website.
Before the password is changed, stop the Decipher Automated Client Service on the machine that the Automated Client component is installed upon.
It will then need changing in several places as part of the Automated Client configuration.
Navigate to the Automated Client install directory (Usually C:\Program Files (x86)\Blue Prism\Decipher Automated Clients)
The files that need changing are:
For each file:
Next the files need encrypting
Open a command-line as Administrator.
Navigate to the Automated Client install directory.
Run each of the commands below once.
Then check each file, to ensure the password is now an encrypted string.
NOTE: If encryption was already applied during installation, or otherwise, and you need to change the password simply make the value of the UserName field plain text, for example:
<add key=”Password” value=”MyN3wP455w0rd!”
Then re-encrypt the file as per the instructions above.
Once all files have been changed and re-encrypted, restart the Automated Client and test that batches can still be processed.
If there are no problems, delete the backups of the config file taken earlier.
It is also an option to encrypt the Decipher Server Configuration at install.
If you chose not to do this at install, or since install, and you are using SQL Authentication, your Database passwords will be held in the plain text as per the screenshot below.
To encrypt this file:
ssiserver.exe -enc
When RabbitMQ is installed, there is a default “guest” account with “guest” password. The same account is commonly used by Decipher, as it is the default option in the installation.
As the “guest” account on every RabbitMQ installation, if it is used by Decipher, it can be a security risk.
If you wish to change the RMQ account used by Decipher, firstly you will need to create a new account in RabbitMQ. To do this:
To change the RabbitMQ credentials used by the Decipher Licensing Service either:
Either will allow to get to the installation options.
Simply click through the install options until the page presented with RabbitMQ connection configuration appears. Then insert the newly created account credentials.
Unfortunately, there is no easy way of changing the RabbitMQ credentials. It requires the Decipher server application to be uninstalled and reinstalled. If you attempt this ensure the configuration is the same before and after by keeping a copy of the SsiServer.exe.config file.
As of Version 2.3 the Decipher Web Client no longer uses RabbitMQ.
In versions prior to V2.3 the RabbitMQ credentials used by the Web Client are held in three separate files.
Each needs configuring individually.
The default location of each file is:
For each file:
Note: If the web.config has encrypted values simply copy the lines from another file, the format is consistent across all three files.
Once the files have been edited, the files need encrypting.
Firstly, stop the Decipher Web SDK Service.
Ssi.SdkService.exe
Ssi.SdkWrapper.exe -enc
C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -pef "appSettings" "C:\Program Files (x86)\Blue Prism\Decipher Web"
C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -pdf "appSettings" "C:\Program Files (x86)\Blue Prism\Decipher Web"
Finally, restart the Decipher Web SDK Service.
As of Version 2.3 the Decipher Plugin no longer uses RabbitMQ.
In versions prior to V2.3 the RabbitMQ credentials used by the Plugin can only be changed by using the DecipherServerConfigurator.exe, which is downloadable from https://portal.blueprism.com
Once all the above steps have been completed it should be possible to delete the guest account if required.
To check if the guest account is still being used by Decipher:
Provided your Connections look like the above it is safe to assume the guest account can be deleted if required.
This can be done from the “Admin” tab in the RabbitMQ management portal.
Simply click on the guest account, scroll to the bottom and click delete.
IMPORTANT NOTE: Before you delete the guest account ensure you have at least one account that has the “Administrator” tag, otherwise you will lock yourself out of the management portal.
Be sure to take advantage of the Logical Access Model in Decipher.
Not all users should use the admin account.
Take the time to create users with the relevant minimum permissions for their role.
The “Copy settings from” is a useful tool to quickly create users.
By default, the Decipher website is bound to port 80 (HTTP). This can be bound to a certificate very easily.
First request a certificate from your Certificate Authority (recommended) or create a Self-Signed certificate (not recommended!)
The certificate should have a Private Key.
The Subject – Your server’s name
The Subject Alternative Name – Something relevant, for example decipher-prod@mycomany.com
On your Decipher Server:
Note: When browsing to the Decipher website, remember to change your URL from http:// to https://
08-05-24 06:00 AM
Thanks for sharing a detailed guide on securing the Decipher setup. Much Needed.
08-05-24 11:20 AM
Just need to correct myself here.
The section "RabbitMQ with Decipher Web Client (Versions < V2.3)" only actually applies to Versions 2.X, this wasn't a configurable item in Versions 1.X.
Thanks.