Use Cases
HomeIntegrityControlManagement CenterSolutions
  • Get Started
  • Integrity | Access
    • Auth. methods
      • LDAP (Username/Password)
      • LDAP (Username/Password) + OTP (SMTP)
      • LDAP (Username/Password) + OTP (SMS)
      • Swedish BankID
      • Microsoft Entra ID (SAMLSPBroker)
      • Foregin eID (SAMLSPBroker)
    • Auth. methods (SAML)
      • One-Time Password (OATH)
      • Inera IdP (SITHS) (SAMLSPBroker)
      • ID-porten (Norway) (SAML IdP with OIDC RP)
      • Multiple SAML IdP's configured
        • Multiple JSON files
    • Auth. methods (OIDC)
      • Static values (OIDC) - Test only
      • Swedish BankID (OIDC)
      • UID/PWD (OIDC)
    • Auth. methods (MISC)
      • Selector filtering
      • AuthZ control
      • External links and Cancel location
    • Add a Federation or SAML SP
  • Integrity | Portal
    • Portal
  • Integrity | Enrollment
    • Software token (OATH)
    • Best practice configuration
  • Integrity | Radius
    • UID/OATH token
    • UID/Password/OATH token
    • UID/Password/SMTP
  • Integrity | API
    • Swedish Siths eID
    • Oath Token
  • Control | Applications
    • Password Reset
    • Password Reset for Entra ID
    • Password Reset for Google Workspace
  • OPERATION
    • Rolling upgrade - cluster
  • TROUBLESHOOTING
    • Wrong relaystate
  • Misc
    • Address configuration externally
    • ADFS
      • Protect Fortified ID apps
      • Install and configure Fortified ID ADFS adapter for Siths eID
      • Install and configure Fortified ID ADFS adapter for Oath
    • AWS
      • Protect AWS Cognito with eID MFA
      • Protect AWS IAM Identity Center with eID MFA
    • Customization
      • Overlay - WEB
      • Overlay - Portal
      • Overlay - Password Reset
      • Overlay - Enrollment
      • Logout page
    • Dependency-Track - protect with eID MFA and SSO
    • Digitala Nationella Prov (DNP) / Skolfederation
      • Active Directory Federation Services (ADFS) with BankID as step-up-method
      • Active Directory / LDAP with BankID as step-up-method
      • Entra ID (Azure AD) with BankID as step-up-method
      • Google with BankID as step-up-method
      • Generate eduPersonPrincipalName (eppn) and store in Google
      • Generate eduPersonPrincipalName (eppn) and store in Entra ID
      • Common configuration
    • Encrypt configuration secrets
    • Microsoft Entra
      • Protect Entra ID (Azure AD) with eID MFA
      • Entra External - Support for eID (SAML)
      • Entra External - Support for eID (OIDC)
    • Expressions
    • Google
      • Common configuration for Google Workspace - Directory API
      • Common configuration for Google Workspace - authentication for Fortified ID products
      • Delegated administration for Google Workspace - teacher updates student guardians
      • Delegated administration for Google Workspace - teacher updates student password
      • Protect Google Workspace with eID MFA
    • HTTPS
    • Protect sensitive data, such as social security numbers, through obfuscation
    • Reverse proxy
      • Install Apache Web Server on Windows
      • Add SSL certificate and enable https
      • Add a Fortified ID virtual host
    • Set AuthnContextClassRef
    • Wiki.js - OpenID Connect (OIDC)
Powered by GitBook
On this page
  • Scenario
  • Prerequisite
  • Install and prepare configuration
  • Test the configuration
  1. Integrity | Access
  2. Auth. methods

LDAP (Username/Password)

PreviousAuth. methodsNextLDAP (Username/Password) + OTP (SMTP)

Last updated 1 month ago

Scenario

In this scenario, we will append the default installation with a username and password authenticator against a LDAP-directory.

Prerequisite

  • This use case assumes that you have good knowledge of the product in question.

  • Fortified ID Access installed and configured with the default configuration

  • LDAP directory. Knowledge about the LDAP directory to be used, such as:

    • Hostname

    • Port

    • Service account / password

    • Location of the users to authenticate.

Install and prepare configuration

  1. Download

  2. Add files and folders from ZIP-file to the config-folder, ex: C:\Program Files\FortifiedID\mgmt-center\data\customer\access\config

  3. Optional: Adjust the LDAPSearch to match your requirement. The default query will find users based on their sAMAccountName.

  4. Append you globals with the following parameters and adjust them according to you needs

{
    "ldap1_name": "ad1",
    "ldap1_host": "ldapserver.company.local",
    "ldap1_port": 636,
    "ldap1_use_ssl": true,
    "ldap1_ssl_trust_all": true,
    "ldap1_base_dn": "dc=company,dc=local",
    "ldap1_bind_dn": "CN=admin,CN=Users,DC=company,DC=local",
    "ldap1_bind_password": "top_secret_password"
}
  1. Append the translations file with the following translation

{
    "uid_pwd_ldap_label": "Username & Password - LDAP"
}
  1. Append the selector with at reference to the new authenticator by appending this block to the default selector

{
    "id": "5",
    "target": "uid_pwd_ldap",
    "label": "uid_pwd_ldap_label"
}
  1. Restart the Access service

Test the configuration

  1. The selector should now be displayed, including the new option for "Username and Password - LDAP".

  2. Select "Username and Password - LDAP" and authenticate using the configured username (default sAMAccountName) and password.

  3. You should now be redirected to the selected application or the Fortified ID test application.

Browse to a site protected by the Access server. Optionally the default login url might be used.

this file
https://localhost:8443/access/authn/samllogin