We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda Web Application Firewall

Configuring Identity Provider (IdP) for SAML Authentication

  • Last updated on

An IdP is a service/website that certifies user identities using security tokens. The identity provider may be an on-premises Active Directory Federation Services (AD FS) setup, or an Active Directory (AD) located in the Azure cloud.

Configuring Azure Active Directory (AD) for SAML Authentication in the New Microsoft Azure Portal

Azure Active Directory (AD) is the identity provider responsible for authenticating users accessing web applications hosted on the Microsoft Azure cloud. Azure AD manages user identities along with applications. You should configure the SAML endpoints in Azure AD for web applications requiring protection from the Barracuda Web Application Firewall. Perform the following steps to configure Azure AD:

  1. Log into the Microsoft Azure Portal.
  2. Select Azure Active Directory and then from the left pane select Enterprise application.
  3. In the Enterprise applications page, click + New application.
  4. In the Add an application page, click Non-gallery application
    saml2.jpg
  5. In the Add your own application page, enter a name for the application and then click Add. For example: samlv2app
    The application page is created.
  6. In the Overview page, click 1. Assign users and groups.

    saml3.jpg
  7. Click Add users > Users and groups and from the right pane, select the user who has to be part of the application.
  8. Go to to the Overview page and then click Set up single sign on.
  9. Select SAML, scroll down, and then copy the App Federation Metadata Url link. This is the Identity Provider Metadata URL to be configured on the Barracuda Web Application Firewall in the ACCESS CONTROL > Authentication Services > New Authentication Service > SAML Identity Provider page. Example: https://login.microsoftonline.com/ <AzureAD tenantID>/federationmetadata/2007-06/federationmetadata.xml?appid=< app_ID>
  10. Use the IdP metadata information and create a SAML IDP authentication service on the ACCESS CONTROL > Authentication Services page. Also, verify that the SP Entity ID is the same and then click Save to save the metadata file to your desktop.
  11. Continue with Steps 3 to 6 under Configuring SAML on the Barracuda Web Application Firewall in the SAML Authentication article.
  12. Use the SAML identity provider created in the previous steps and create an authorization policy in the ACCESS CONTROL > Authentication Policies page.
  13. Click Generate to generate an XML file. For more information on how to generate the service provider (SP) metadata file, refer to, Generate Service Provider (SP) Metadata in the SAML Authentication article. 
  14. Go to the SAML-based sign on page, click Upload metadata file, select the XML file to upload and then click Save.
  15. Verify the same in Microsoft Azure Portal page.

Configuring Active Directory Federation Services (AD FS) 2.0 for SAML Authentication

Active Directory Federation Services (AD FS) is the identity provider responsible for authenticating users accessing the web applications hosted on the Microsoft Windows server. Perform the following steps to configure AD FS 2.0:

  1. Download the IdP metadata from the AD FS server.
  2. Use the IdP metadata information and create a SAML IDP authentication service on the ACCESS CONTROL > Authentication Services page.  
  3. Continue with Steps 3 to 6 under Configuring SAML on the Barracuda Web Application Firewall in the SAML Authentication article.
  4. Go to the ACCESS CONTROL > Authentication Policies page, and generate the Service Provider (SP) Metadata file by following the steps in Step 6   in the  Configuring SAML on the Barracuda Web Application Firewall article.
  5. Save the metadata file to the location you desire on the AD FS server.
  6. Log into the AD FS server, and do the following:
    1. Click the Start menu and select AD FS 2.0 Management.
    2. On the AD FS 2.0 window, expand the Trust Relationships folder under the AD FS 2.0 root directory by clicking the plus ( + ) button.
    3. Right-click Relying Party Trusts and select Add Relying Party Trust. The Add Relying Party Trust Wizard appears.
    4. In the Add Relying Trust Wizard window, click Start.
    5. In the Select Data Source step:
      1. Select Import data about the relying party published from a file.
      2. Click Browse and select the SP Metadata file saved in Step 5.
      3. Click Next.
      4. The message “Some of the content in the federation metadata was skipped because it is not supported by AD FS 2.0” may appear. Click OK.
    6. In the Specify Display Name step:
      1. Enter the service provider domain in Display Name. Example: service1.domain.com
      2. Click Next.
    7. In the Choose Issuance Authorization Rules step, keep the default settings and click Next.
    8. Click Next in the Ready to Add Trust step, and then click Close. The Edit Claim Rules window appears.
    9. In the Edit Claim Rules window, add, edit, or remove rules and click OK.
    10. The added trust displays in the Relying Party Trusts list.

Configuring SAML Attributes on the AD FS 2.0 Server

To illustrate how to configure SAML attributes on the AD FS server, the LDAP attributes User-Principal-Name and Token-Groups – Unqualified Names are used as examples in this section.

Perform the following steps to configure SAML attributes on the AD FS server:

  1. Log into the AD FS server.
  2. Click the Start menu and select AD FS 2.0 Management.
  3. In the AD FS 2.0 window, expand the Trust Relationships folder under the AD FS 2.0 root directory by clicking the plus ( + ) button.
  4. Click on the Relying Party Trusts folder. The Relying Party Trusts list appears in the right pane.
  5. Right-click on the relying party application you created, and select Edit Claim Rules. For example, service1.domain.com
  6. In the Edit Claim Rules window, click Add Rule in the Issuance Transform Rules tab.
  7. In the Add Transform Claim Rule Wizard window:
    1. Select Send LDAP Attributes as Claims in the Choose Rule Type step, and click Next.
  8. In the Configure Claim Rule step:
    1. Enter a name in Claim rule name.
    2. Select Active Directory from the Attribute store list.
    3. Under Mapping of LDAP attributes to outgoing claim types, create mappings for the attributes that need to be allowed in the SAML IdP response. Example:

      LDAP AttributeOutgoing Claim Type
      User-Principal-NameUPN
      Token-Groups – Unqualified NamesGroup
    4. Click Finish.
  9. Create transform rules for the attributes added in Step 8c (i.e., User-Principal-Name and Token-Groups – Unqualified Names).
  10. To add a transform rule for the attribute User-Principal-Name, repeat Step 6 and 7, and then continue with the steps below.
  11. Select Send Claims Using a Custom Rule in the Choose Rule Type step and click Next.
  12. In the Configure Claim Rule step:
    1. Enter a name in Claim rule name. Example: Transform UPN to epPN.
    2. Type or copy and paste the following in the Custom rule text box:

      c:[Type == "http://schemas.xmlsoap.org/ws/2005/05/identity/claims/upn"]
       => issue(Type = "urn:oid:1.3.6.1.4.1.5923.1.1.1.6", Value = c.Value, Properties["http://schemas.xmlsoap.org/ws/2005/05/identity/claimproperties/attributename"] = "urn:oasis:names:tc:SAML:2.0:attrname-format:uri");
    3. Click Finish.
  13. To add a transform rule for the attribute Token-Groups – Unqualified Names, repeat Step 6 and 7, and then continue with the steps below.
  14. Select Send Claims Using a Custom Rule in the Choose Rule Type step and click Next.
  15. In the Configure Claim Rule step:
    1. Enter a name in Claim rule name. Example: Transform Group to epSA
    2. Type or copy and paste the following in the Custom rule text box:

      c:[Type == "http://schemas.xmlsoap.org/claims/Group", Value == "Domain Users"]
       => issue(Type = "urn:oid:1.3.6.1.4.1.5923.1.1.1.9", Value = "member@domain.com ", Properties["http://schemas.xmlsoap.org/ws/2005/05/identity/claimproperties/attributename"] = "urn:oasis:names:tc:SAML:2.0:attrname-format:uri");

      The domain.com name above should be the domain name of the AD FS Server configured.

    3. Click Finish, and then OK.
  16. The added rules display under the Issuance Transform Rules tab.

Configuring Okta for SAML Authentication

The Barracuda Web Application Firewall can authenticate users configured on Okta using SAML single sign-on. Okta is as an SAML IDP provider and the Barracuda Web Application Firewall is the service provider to authenticate users. Perform the following steps to configure Okta:

  1. Download the IdP metadata from the Okta.
  2. Use the IdP metadata information and create a SAML IDP authentication service on the ACCESS CONTROL > Authentication Services page.
  3. Continue with Steps 3 to 6 under Configuring SAML on the Barracuda Web Application Firewall in the SAML Authentication article.
  4. Go to the ACCESS CONTROL > Authentication Policies page, and generate the service provider (SP) metadata file by following the steps under Generate Service Provider (SP) Metadata in the SAML Authentication article.
  5. Save the metadata file to your desktop.
  6. Open the metadata file and note the following:
    1. Entity ID
    2. AssertionConsumerService Location
  7. Log into the Okta application.
  8. Click Admin on the Okta homepage.

                  Admin.png
  9. On the Okta Dashboard, click Add Applications under Shortcuts.

                  Add Applications.png
  10. On the Add Application page, click Create New App and do the following:
    1. Select SAML 2.0 in the Create a New Application Integration window and click Create.

           Create_New_App.png
    2. In the Create SAML Integration page under General Settings, enter a name for the application in the App name field and click Next.

             General_Settings.png
    3. Under Configure SAML:
      1. Specify the AssertionConsumerService Location noted in Step 6 in the Single sign on URL field. Verify Use this for Recipient URL and Destination URL is selected.
      2. Specify the Entity ID noted in step 6 in the Audience URI (SP Entity ID).
      3. Select Transient as Name ID format.
      4. Click Next.

        Configuring_SAML.png
    4. Under Feedback:
      1. Select I’m an Okta customer adding an internal app next to Are you a customer or partner?.
      2. Select It’s required to contact the vendor to enable SAML next to Contact app vendor.

        Feedback.png
    5. Click Finish.

 

Last updated on