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
  • Update Google to trust Integrity
  1. Misc
  2. Google

Common configuration for Google Workspace - authentication for Fortified ID products

Scenario

In this scenario, Google Workspace will be used as the IdP to authenticate to a Fortified ID product (in the example below Forms is used as the Fortified ID product).

The integration between the Fortified ID product and Google is federation-based (SAML2). Google will pass user attributes necessary for identification, and potentially additional attributes for delegated administration purposes.

Prerequisite

There are some prerequisite for this use case. You will need the following:

  • Google administration rights.

  • Host (DNS) name of the Fortified ID product service (external access)

  • Fortified ID product installed

  • Fortified ID product SP (SAML Service Provider) configured

Configuration

Update Google to trust Integrity

Trust need to be established between the primary IdP (Google) and the SP (Fortified ID product ).

Create custom SAML app

  • Login to Google admin console (admin.google.com) as an administrator

  • In the left hand menu, select Apps->Web and mobile apps

  • Click Add app -> Add custom SAML app

  • Enter a name of the app, Fortified ID Forms

  • Continue

  • Click Download IdP metadata

  • Place the downloaded IDP metadata file in /customer/config/resources_external/saml_idp_metadata/ on your Forms server. Verify that the name of the file is GoogleIDPMetadata.xml.

  • Continue

  • Enter ACS URL = https://<your_forms_dns_name>/forms/authn/login

  • Enter Entity ID = FortifiedID_Forms

  • Leave the Name ID part unchanged

  • Continue

  • Click Add mapping

  • Select the Google Directory attribute field containing the email value

  • Enter App attributes = mail

  • Click Add mapping

  • Select the Google Directory attribute field containing the value used to connect the delegated admin with subordinates, for example department

  • Enter App attributes = department

  • Finish

  • On the User Access part of the app configuration, click Expand (down arrow)

  • Change the Service status. Select the group or OU that should be allowed to access Forms. (For example, teachers)

Update Forms to trust Google

  • Restart the Forms service

PreviousCommon configuration for Google Workspace - Directory APINextDelegated administration for Google Workspace - teacher updates student guardians

Last updated 10 months ago