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
  • Configuration
  • Download and add configuration
  • Update the configuration to map your environment
  1. Integrity | API

Swedish Siths eID

PreviousUID/Password/SMTPNextOath Token

Last updated 10 months ago

Scenario

This use case will show how you can add Siths eID authentication using Fortified ID Integrity API. This can be used for services unable to consume authentication using standard protocols. For example, the Fortified ID SITHS ADFS adapter use this pattern to perform Siths eID authentication.

Fortified ID Integrity API connects to the Inera SITHS REST authentication service to perform the authentication.

This use case support Siths eID authentication using smart card or mobile app.

Prerequisite

  • FortifiedID API installed

  • Keystore in p12 format, for connection to the Inera SITHS authentication service

  • Keystore password

Configuration

Download and add configuration

Remember that this use case does not describe installation of the products. Products are expected to be installed in advanced. The use case template is pointing to the Inera QA environment.

  1. Download ZIP containing configuration for Integrity API

  2. Add the configuration to your environment.

    1. Add the customer folder to your \..\fortifiedid\api\ folder. (Rename the existing customer folder to customer_ORG)

Update the configuration to map your environment

  1. Rename the file config/siths_auth_service.p12 to config/siths_auth_service.p12.org

  2. Add the keystore file to the config folder

  3. Rename the keystore file to siths_auth_service.p12

  4. Open config/config.json

  5. Change these values

    1. YOUR_SITHS_AUTH_SERVICE_KEYSTORE_PASSWORD_GOES_HERE -> the password of your keystore file/key

    2. Generate a random password. Change YOUR_API_KEY_SECRET_GOES_HERE -> the generated password.

    3. Verify file paths. If necessary, change to match your environment.

  6. Restart the Fortified Integrity API services.

Click to download customer folder

If connecting to Inera SITHS production environment, change the endpoints. For a complete list of endpoints, please , Adress för relying party API.

USE_CASE_LINK
view this page