In this scenario, we will use Postman as an OIDC Relying Party (RP) and Integrity Web as an OpenID Connect Provider (OP). The guide is designed for a Windows installation but can be adapted for Docker and Linux installations as well. The configuration will use port 8443.
Authentication will be performed using a username and password against LDAP.
Prerequisite
There are some prerequisites for this use case. You will need the following:
Server platform. Docker, Windows or Linux. In this use case we have used a Windows server with an Active Directory with at least one LDAP account.
In this example, we will use one "administrator" account and one user account..
The current version of FortifiedID Integrity Web is installed.
Note. All configuration and testing are done on the scenario server.
Configuration
Download and modify configuration
Copy the customer_WEB folder to you \..\fortifiedid\web\ folder.
Rename the existing customer folder to customer_ORG and rename customer_Web to customer.
Update the configuration to map to your environment
The downloaded folders contains all needed files. For example, test certificates files are included and configured to work with the example application.
However, some data needs to be changed to map your environment. You need to update the LDAP data to map 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.
You will need an account for the LDAP connection. You can use a regular user account for this configuration. In normal cases, an administrator account should be used.
To make it easy the application folder have a file called globals.json that contains the data you need to change. Config.json uses the variables in globals.json.
Open globals.json for \..\fortifiedid\enrollment\customer\config and \..\fortifiedid\web\customer\config folder and update:
LDAP data to map your environment
File paths
HTTP if needed
When updated, start the Integrity Web service.
Wait until Integrity Web service has started before continuing.
Test the use case
OIDC well-known information
Open a browser on the Integrity Web server
Browse to https://localhost:8443/oidc/tenant1/.well-known/openid-configuration
Verify that the well-known page opens
Use Postman to test the OIDC flow
Unzip the file and import the collection to Postman.
The collection will be called "FID-OIDC-UseCases" in Postman
Open the Request "OIDC Case 4" in the "FID-OIDC-UseCases" collection
Select the Authorization tab of the request
Click on the "Get New Access Token" button.
Enter your LDAP account username and password.
Copy the content of the ID-token
Note: Some of the data in the OIDC Claim are hardcoded for demonstration purposes.
Complete config.json file
The config.json for Integrity Web can be found in the included ZIP file associated with this use case.
Basic knowledge about Postman and Postman installed on the local computer, with access to the Integrity server.You will also need the following pre-configured Postman Collection
To download the ZIP file containing the configuration and all other necessary files for Integrity Web, click to download the customer folders for the web..
Download the file
To verify the content of the ID-token, simply paste it into the "Encoded" section of the webpage.