Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

How to set up Squirro Single Sign-On with Microsoft Active Directory Federation Services (AD FS).

Table of Contents

Configure AD FS

This walk-through assumes AD FS 2019, and the screenshots are from Windows Server 2019. The process is very similar on earlier versions.

Relying Party Trust

  1. Open the AD FS Console and "Add Relying Party Trust…"


  2. Select the "Claims aware" option
  3. Enter data about the relying party manually


  4. For display name enter any name, for example "Squirro"


  5. Enable support for the SAML 2.0 WebSSO protocol. The service URL is https://SQUIRRO/sso/callback (URL of your Squirro installation plus the path /sso/callback)


  6. For the relying party trust identifier enter https://sso.squirro.com/o/saml2/entity


  7. Decide on an Access Control Policy. For example limited to a given Active Directory group
  8. In the last step confirm that you want to configure claims issuance policy

Claim Rules

  1. Add a new Rule
  2. Choose the claim rule template "Send LDAP Attributes as Claims"


  3. Select the "E-Mail-Address" attribute and send it as the "Name ID". Additionally send the "Given Name" and "Surname".


  4. To pass over group memberships, create another claim rule - this one of type "Send Group Membership as Claim"
  5. Fill out the parameters as follows:
    • Claim rule name: Can be freely chosen, use for example "Group - <groupname>"
    • User's group: Select the AD group to pass over
    • Outgoing claim type: Group
    • Outgoing claim value: put in the name of the group
  6. The group membership claim rule can be added more than once, in case multiple groups should be sent over. A good idea is to have a administrator group (e.g. "Squirro_Admins" that is sent as a claim value).

Export Federation Metadata

Download the FederationMetadata.xml file. This can be downloaded from the ADFS server at https://ADFS_SERVER/FederationMetadata/2007-06/FederationMetadata.xml.

Configure SAML Metadata

To configure SAML Single Sign-On with the federation metadata file, go to the Server space in Squirro and in the navigation on the left select Single Sign-On (SAML).

Press the red plus button on the top right. Fill out the form:

  • Domain: *
  • Enabled: Check
  • Entity ID: leave empty for the default
  • Metadata file: upload the FederationMetadata.xml file
  • Certificate file: can be left empty
  • User group: Select a user group which should be assigned to all SSO users - this is optional
  • Group names field: put in the value http://schemas.xmlsoap.org/claims/Group
  • Mapping of groups to Squirro roles:
    this defines the server-wide permissions for SSO users based on the group names that were retrieved from the claims
    Example value: Squirro_Admins=admin; Squirro=user; reject
    This example gives admin rights to all users in the Squirro_Admins group, normal access to all users in the Squirro group and rejects all other logins.


Enable SSO

For security reasons, the final configuration needs to be done directly on the server. Log into the server using SSH or similar means and edit the file /etc/squirro/frontend.ini. Then append the following lines at the end:

[security]
sso_enabled = true
sso_endpoint = http://localhost:81/studio/extauth_saml/extauth

Reduce HTTP Session

By default Squirro will keep user sessions for 30 days, surviving browser restarts as well. In a Single Sign-On environment, this should be changed to the session expiring once the user restarts the browser. This can be achieved by changing /etc/squirro/frontend.ini and adding the following lines:

[frontend]
session_permanent = false
  • No labels