Depending on the input data that Fortified ID (IdP/OP) receives, you can control which selectors and/or authenticators to be presented to a user.
In the picture above the scenario is:
A user comes from the Portal (id=portal) app, the user gets two options to choose from, Employee or Customer.
If the user comes from Password reset (id=pwdreset), he is directly directed to the UID + MFA authenticator.
In this use case
Fortified ID Portal and Fortified ID Password Reset will act as SAML SPs. The input data they present to the SAML IdP to act on is and spEntityID = FortifiedID_Portal and spEntityID = FortifiedID_PWD_Reset
The SAML IdP is Fortified ID WEB.
Notes regarding this Use Case
Here are some information about what is core of this use case.
The key configuration parts, see config.json at the bottom of this use case, are
Line 154, 160 and 166
Here we use the parameter include_expr to decide if this option should be presented or not. In this case we verifying which service provider the request came from.
In our scenario with use exports.spEntityID. What parameters that is available is something you can check when logging a authenticators, see separate use case for that.
Line 143
If only one option is available the you can decide if this option should be presented or if you find that unnecessary. "auto_select": true
The value true is by default. If you try false and then try Password Reset you will se that the user will be presented with one option.
Prerequisite
This use case assumes that you have good knowledge of the product in question.
Fortified ID WEB installed and configured
LDAP directory. Location are the users to authenticate.
The example code is configured using an Active Directory.
We are using mail attribute when authenticating the Active Directory user.
Fortified ID Portal installed and configured
Fortified ID Password Reset installed and configured
FakeSMTP. This is used when a user reset its own password. When authenticating to the self service we will use UserID (mail) and a mail delivered one-time password (otp).
Download and install FakeSMTP on the same host as the use cases and start the smtp service on port 25.
Note. If you have an "real" SMTP server then use that instead.
Note. All configuration and testing is done on the scenario server.
Basic configuration of Fortified ID Web, Portal and Password Reset
Install and prepare configuration
Download and install Fortified ID Web, Fortified ID Portal and Fortified ID Password Reset.
To install Integrity Web and Integrity Portal, see documentation and installation.
Add files and folders from ZIP-file to Fortified ID Web, Fortified ID Portal and Fortified ID Password Reset
Replace the customer folders for your installations with the ones from the zip-file.
Note. This use case was initially done on a Windows server, if you run Container/Docker or Linux you might have to changes something to work in your environments like file paths e.g..
Open the globals.json in both customer folders and update to match your environment.
Start services
Start Fortified ID WEB
Start Fortified ID Portal
Start Fortified ID Password Reset
Test the configuration
Verify services are started
Verify Fortified ID WEB is started
Verify Fortified ID Portal is started
Verify Fortified ID Password Reset is started
Login to Fortified ID Portal using Fortified ID WEB as IdP
This is the address to Fortified ID Password Reset acting as a SAML SP
You should be redirected to the Fortified ID WEB acting as SAML IdP and see the following:
Note. There are three options available on selector root but only one is matching SP Password Reset. Since it is only one option the user will be passed directly to the authenticator available for that option.
Complete config.json file of Fortified ID WEB
Other configuration and reference files will be found in the ZIP-file you downloaded.