In this use case we are going to change the look and feel for the Fortified ID application Enrollment. We will also add a language (Norwegian) and add information to the Swedish language file.
Note, this use case focus on activating different strong authentication methods for OATH Software, OATH Hardware, Passkey (FIDO2) and FortifiedID Mobile backend. Each method must be configured accordingly.
Prerequisite
There are some prerequisite for this use case.
Fortified ID Enrollment installed.
Microsoft SQL Server
Microsoft SQL Server Express
Microsoft SQL Server Management Studio (SSMS)
Create manually a database called Enrollment. If Enrollment database exist the Enrollment service will create all the tables when service start.
For this use case we use the sa account. Make sure the sa account has administrative rights to the database.
Download ZIP-file with example customer folder for Enrollment.
Add ZIP content to you installation
First, make a backup of your existing customer folder.
Open folder C:\Program Files\FortifiedID\enrollment
Rename customer folder to customer_ORG
From the downloaded ZIP-file, add the example customer folder to:
C:\Program Files\FortifiedID\enrollment\
The result should look like:
Update the configuration to map your environment
The downloaded folders contains all information needed. For example, a test certificate and metadata files are included and configured to work with the example applications.
However, some data needs to be changed to map your environment. You need to update the SQL data to match your environment. Since this example was done on a Windows server you might need to update file paths if you run something else. Also the http ports might need to be changed if they are not available in your environment.
To make it easy to change settings to your local environment. Go to the config folder and edit the file globals.json, that contains the information you need to change.
Config.json uses the variables in globals.json.
Open globals.json in \..\fortifiedid\enrollment\customer\config and update:
SQL data to map your environment
File paths if needed
HTTP if needed
Start Fortified ID enrollment service
Note. Since we use the NoOp authenticator there will be no login and use of Fortified ID Web/IdP.
Start the Fortified ID Enrollment service. Verify the service is running.
Test the overlay for OATH software
If you have added the folder structure and example config.json file used in this use case.
Below screenshot should be the result you should see
Try the other enrollment apps
https:/localhost:8444/enrollment/oathhw/
https:/localhost:8444/enrollment/webauthn/
https:/localhost:8444/enrollment/mobileid/
Example config.json
Below is an example config.json file with focus only on this use case. We use the NoOp authenticator so no need for an IdP (e.g. Fortified ID Web). This example config.json also maps to the overlay folder created for this use case.
