This blog article describes how to make for PowerSearch for Dynamics 365 FIPS compliant.
This article is ONLY relevant for you if FIPS compliance is enabled on your Dynamics 365 server OR you plan to enable it in the future.
Minimal PowerSearch version: 2017.12.1
It is recommended to create a backup of your existing PowerSearch configurations first. More information about how to export/import PowerSearch configuration records can be found here.
Then open Dynamics 365 Settings, navigate to the MSCRM-ADDONS-area and open Products. Select PowerSearch and add a new settings key to its settings subgrid by hitting the [+]-button on the right side and enter:
From now on, all configurations will be stored as FIPS compliant. Top convert all existing configurations, open the PowerSearch web configuration and navigate to the General Settings-tab. After reloading the config, you will be provided with the following option (see figure 2) at the bottom. Hit the [Start]-button.
The sample message below tells that 4 configs will not work if FIPS is enabled on the server. Hit the [OK]-button.
If everything was successful you will see the following notification:
Figure 4: Success notification
But if FIPS is already enabled on your server, it is not possible to convert the values directly. In this case, the following dialog will pop up:
Figure 5: Message if FIPS is enabled
It asks for permission to regenerate the config records instead of converting them. This is similar to a change of the InputFetchXML in the PowerSearch config. Afterward custom labels, orders, default values and so on will be reset. Hit the [OK]-button in order to start.
If you now see the following notification, the process was successful.
Figure 6: Success notification
Finally please install the FIPS compliance license key which you get from our Support team (email@example.com).
That’s it! We appreciate your feedback! Please share your thoughts by sending an email to firstname.lastname@example.org.