LogoLogo
HomeIntegrityControlSolutionsManagement Center
3.1.0 - Access
3.1.0 - Access
  • Introduction
  • The Service
    • Overview
    • About this release
      • Release notes
      • Breaking changes
    • Architecture
      • Modules
      • Folder structure
      • Startup
    • Getting started
    • Installation
      • Container
      • Linux
      • Windows
    • Operations
      • Configuration
      • Metrics
      • Health check
      • Logging
        • System logging
        • Event logging
      • SBOM & license material
  • Modules
    • External modules
    • Internal modules
      • SAMLModule
      • OIDC
        • OpenID Configuration endpoint
        • JWKS endpoint
        • Authorization endpoint
        • Token endpoint
          • Authorization code
          • Refresh token
        • User info endpoint
        • Introspection endpoint
        • End session endpoint
  • Configuration reference
    • Introduction
    • Terms and abbreviations
    • Property expansion
    • File inclusion
    • Secrets management
    • Examples
  • Authenticators
    • Introduction
    • Common configuration
    • Web Authenticator API
    • Flow control
      • Selector
      • AuthController
      • SSO Authenticator
      • Chain
      • Impersonate
      • Impersonate With Search
    • Credential validators
      • SITHS eID
        • With QR or "app-switch"
      • BankID
        • On another device
        • On mobile device
      • Freja e-ID
        • With user input
        • With QR or "app-switch"
      • Mobile ID
        • With QR or "app-switch"
      • Header based
        • Certificate
      • Pointsharp Net iD Access server
        • On another device
        • On same device
      • Integrated windows login, IWA
      • User name & password
      • User lookup
      • OTP validator
      • Passkey validator
      • Exposed metrics
      • Test
        • Static SAML
        • No operation
    • Protocol managers
      • SAML
        • SAML IDP
        • SAML SP
        • IDP Discovery Service
      • OIDC
        • Authorization Code Flow
        • Implicit Flow
        • OIDC Relying Party
    • UI
Powered by GitBook
On this page
  • Configuration
  • Logging
  • Data sent to validation pipe
  • Data exposed to global state
  • API
  • Starting an authentication
  • Translation keys
  1. Authenticators
  2. Credential validators

User lookup

Provides a sing field of input for user to enter an identifier.

PreviousUser name & passwordNextOTP validator

Configuration

Authenticator type: UserLookup

Common Authenticator configuration can be found .

Name
Description
Default value
Mandatory

pipe_id

Name of pipe used for validation

N/A

allowed_retries

Allowed number of times a user is allowed to enter OTP before process is aborted.

2

webroot_dir

See common authenticator configuration

web/authenticator/user_lookup

{
    "id": "uidlookup",
    "type": "UserLookup",
    "config": {
        "base_path": "/saml/authn",
        "pipe_id": "finduser",
        "webroot_dir": "web/authenticator/user_lookup"
    }
}

Property base_path should not contain the full path when used in conjunction with the Selector, instead, the full URI will be handled by the selector. The full path will be base_path + / + id.

Logging

Apart from system logging, event logging is done when completing and failing a transaction.

Event ids are:

  • WEB_100024("Performed user lookup")

    • IDENTIFIER (user trace id)

    • CUSTOMER_IDENTIFIER (if configured)

    • SOURCE_USER_NAME (username entered by the user)

    • SOURCE_ADDRESS (ip of the remote session)

  • WEB_100025("User lookup failed")

    • IDENTIFIER (user trace id)

    • CUSTOMER_IDENTIFIER (if configured)

    • SOURCE_ADDRESS (ip of the remote session)

    • SOURCE_USER_NAME (username entered by the user)

Data sent to validation pipe

On validation, data sent to the pipe is:

  • identifier - the username provided by the user

Data exposed to global state

After a user completes a transaction, the authenticator is marked as done. Data from the authentication response is then put into the global state replacing existing values:

  • username

API

Starting an authentication

Start by sending in a Ajax request containing identifier & password:

{
    "type": "start",
    "data": {
        "identifier": "<user_data>"
    }
}

The response back will contain either a COMPLETED or ERROR:

{
    "status": "COMPLETED"
}

Translation keys

{
  "user_lookup.identifier": "Username",
  "user_lookup.start_authentication": "Sign in",
  "user_lookup.authentication_verified": "Identity verified",
  "user_lookup.redirecting": "Redirecting...",
  "user_lookup.cancel": "Cancel",
  "user_lookup.ERROR": "Wrong username or password.",
  "allow-cookies-body": "To save your language settings on this device you need to approve a language cookie.",
  "allow-cookies-button": "Approve language cookie",
  "change_language": ""
}
{
  "user_lookup.identifier": "Användarnamn",
  "user_lookup.start_authentication": "Logga in",
  "user_lookup.authentication_verified": "Identitet verifierad",
  "user_lookup.redirecting": "Omdirigerar...",
  "user_lookup.cancel": "Avbryt",
  "user_lookup.ERROR": "Felaktigt användarnamn eller lösenord",
  "allow-cookies-body": "Vill du spara dina språkinställningar på denna enhet behövs ett godkännande av  språk-cookie.",
  "allow-cookies-button": "Godkänn språk-cookie",
  "change_language": ""
}
here