How to Configure Netreo to Use SAML 2.0 for User Management
  • 02 Apr 2024
  • 5 Minutes to read
  • Dark
    Light
  • PDF

How to Configure Netreo to Use SAML 2.0 for User Management

  • Dark
    Light
  • PDF

Article summary

When using SAML 2.0 authentication, users may no longer log in as regular web users using Netreo local user accounts.

Configuring SAML single sign-on in Netreo requires configuration both within Netreo itself and within your identity provider account.

Adding and configuring applications in an identity provider is highly specific to each provider, and these instructions are not specific to any single provider. Check your identity provider's documentation for the most up to date information on how to add an application to your account and configure their service appropriately.

Netreo SaaS and your ACS URL
Netreo automatically generates the ACS URL value to supply to your identity provider. However, when configuring SAML in Netreo SaaS, the ACS value is based on the Netreo SaaS URL that you used to log in for that session. Since Netreo SaaS allows logging in from three different URL options (netreo.cloud, www.netreo.cloud, portal.netreo.cloud), it is highly recommended that you select only one URL option and use only that URL. Then, log in to Netreo SaaS using that URL, configure SAML, and then make sure all of your users log in using that preferred URL. Once SAML is configured, if a user logs in using a different URL they may experience redirection issues.
  1. Log in to Netreo as a user with the SuperAdmin access level.
  2. Go to the main menu and select Administration > Users > Authentication Settings to navigate to the Authentication Settings page.
  3. In the TYPE field of the Authentication panel select SAML (2.0) from the pull-down menu. The SAML configuration options become visible.
    • Three URLs are automatically provided in the Service URLs for Your Identity Provider panel that can be used to add an application and configure their service to work with Netreo. These URLs are specific to each Netreo instance.
      • AUDIENCE (ENTITYID) URI
        The signature to identify Netreo as the service provider.
      • ACS (CONSUMER) URL
        (Assertion Consumer Service) The Netreo endpoint to provide as a response to a successful login through the identity provider. Sometimes referred to as recipient.
      • SINGLE LOGOUT URL
        The Netreo endpoint used to log a user out of Netreo simultaneously when the identity provider logs the user out of their Netreo session. Your identity provider must support federated logout to use this endpoint.
  4. Now log in to your identity provider and create a new application.
  5. In the configuration area for your application:
    • For the Audience (or Entity ID) field in your identity provider application configuration, copy the AUDIENCE (ENTITYID) URI value from Netreo and paste it into the appropriate field.
    • For the Recipient (or ACS Consumer) fields in your identity provider application configuration, copy the ACS (CONSUMER) URL value from Netreo and paste it into the appropriate fields.
      • Some identity providers combine the recipient and ACS consumer into a single field, while others use separate fields. The same value is used for both.
      • Netreo does not use ACS URL validation. Consult your identity provider documentation for the proper value to use in the validator field, if present. (Wildcard is a common value.)
    • For the initiator field select Service Provider.
    • For the name ID format select Email.
    • For signature element select Both.
    • Set all remaining options as appropriate for your organization (timeout duration, etc.).
  6. In the Identity Provider Configuration panel in Netreo:
    • Copy the issuer URL from your identity provider and paste that value into the ENTITY ID field.
      • (This value is likely found in the SSO section of the application you created above. Look for metadata in the URL to identify the correct URL to copy.)
    • Copy the login endpoint URL from your identity provider and paste that value into the LOG IN URL field.
      • (This value is likely found in the SSO section of the application you created above. Look for login or sso in the URL to identify the correct URL to copy.)
    • Copy the X.509 certificate string from your identity provider and paste it into the X509 CERTIFICATE STRING field.
      • (This value is likely found in the SSO section of the application you created above. Copy/paste the string exactly as provided by the identity provider. Leave newlines intact. Do not attempt to format the string.)
    • If you are using Azure SAML, you may need to select OFF for the INCLUDE SUBJECT IN REQUEST field.
      • Azure SAML doesn't accept how regular SAML is processed. In a typical SAML environment, one of the objects sent back is the subject, but Azure won't accept that object when it's in the payload. Since Azure may require the subject parameter to be omitted from the login request, the toggle should be OFF when using Azure ADIf you wish to follow the normal SAML 2.0 standard the toggle should be ON.
  7. If you have an Active Directory account associated with your identity provider account, Netreo supports the use of a user permission mapping attribute key and values. This allows you to provide a higher Netreo user access level to certain accounts. All other accounts default to the "User" access level, which has the least privileges. (These must initially be set up as parameters in the identity provider application you created above. Then the matching attribute key and attribute values must be added to Netreo using the following steps.)
    1. In the User Mapping Permissions panel in Netreo:
      1. In the ATTRIBUTE NAME field enter the name of the Active Directory group attribute key configured in your identity provider application.
      2. For each Netreo user access level  field enter the attribute value configured in your identity provider application that corresponds to the group that you wish to have that access level.
        • Netreo supports the use of user groups containing additional nested groups.
    2. If you do not provide user mapping permissions here, all users will be logged in to Netreo at the "User" access level.
  8. Select Save.

All user log-ins are now managed by your identity provider. However, any logged in users must log out and log back in again for the change to take effect.

Active Directory User Role Changes
When you add/change Netreo user access roles for Active Directory users, you must delete the affected Netreo web user accounts so that Netreo can recreate those accounts using the newly assigned roles.

Was this article helpful?