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)
      • Certificate-Based Authentication
      • 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
    • Add Fortified ID app to Access
    • Use Access as logout
  • 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
    • OIDC M2M Authentication & Token Service
  • Control | Password Reset
    • Active Directory
    • 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
    • Change look and feel
    • 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
      • mTLS in Apache HTTPD using a Self-Signed CA and Client Certificates
    • Set AuthnContextClassRef
    • Wiki.js - OpenID Connect (OIDC)
    • Add roles based on memberOf
    • ScriptEval Examples
Powered by GitBook
On this page
  • Scenario
  • Prerequisite
  • Configure Portal to use Access as logout location
  • Configure Access to host a logout page
  1. Integrity | Access

Use Access as logout

Scenario

Each of the Fortified ID SAML apps (Portal, Forms, Enrollment and Password Reset) has a local logout page the will redirect to when you do logout in any of the products. If you want all or any of the products to use Access instead of logout, this use case describes it. Another advantage is that Access can use the same look and feel as other graphical components in Access.

Note. If you like to cahnge look and feel for your installed products, check out this use case: https://docs.fortifiedid.se/use-cases/misc/change-look-and-feel

Prerequisite

  • You have installed one or more of the Fortified ID product and Fortified ID Access.

Configure Portal to use Access as logout location

In this use case we will use Fortified ID Portal as an example. (Forms, Enrollment and Password Reset are configured the same way).

  1. Stop the service of the application your changing look and feel.

  2. Open a file/folder explorer and go to drive:\\FortifiedID\mgmt-center\data\customer\portal\config\modules

  3. Open portal.json and add

    "logout_endpoint_url": "${globals.logout_endpoint_url}",
  4. Save and close

  5. Open global.json and add

    "logout_endpoint_url": "${globals.host_uri}access/logout/"
  6. Save and close

  7. Restart service

Configure Access to host a logout page

  1. Stop the Fortified ID Access service

  2. Open a file/folder explorer and go to drive:\\FortifiedID\mgmt-center\data\customer\access\config\modules

  3. Download the following zip-file, infoendpoint_logout.json

  4. Drop the infoendpoint_logout.json file in above folder.

  5. Open global.json and add

    "overlay_dir": "${system.customer_home}/overlay",
  6. Save and close

  7. Start the Fortified ID Access service

PreviousAdd Fortified ID app to AccessNextPortal

Last updated 3 days ago