Barracuda WAF Single Sign-On SSO
Single Sign-On (SSO) solution by miniOrange provides secure Single Sign-On access into Barracuda WAF using a single set of login credentials. You can log into Barracuda WAF using miniOrange credentials or Microsoft Entra ID credentials or any of your existing identity providers. With miniOrange SSO services, along with Barracuda WAF you can also login into other On-Premise and Cloud Applications using your existing Identity Providers/User Store (Azure Active Directory, Okta, Ping) credentials . Follow the given setup guide to integrate SAML SSO for your Barracuda WAF account.
miniOrange and Barracuda WAF Single Sign-On (SSO) integration supports the following features:
- SP Initiated Single Sign-On (SSO)
- IdP Initiated Single Sign-On (SSO)
Connect with External Source of Users
miniOrange provides user authentication from various external sources, which can be Directories (like ADFS, Microsoft Active Directory, OpenLDAP, AWS etc), Identity Providers (like Microsoft Entra ID, Okta, AWS), and many more. You can configure your existing directory/user store or add users in miniOrange.
Follow the Step-by-Step Guide given below for Barracuda WAF Single Sign-On (SSO)
1. Configure Barracuda WAF in miniOrange
- Login into miniOrange Admin Console.
- Go to Apps and click on Add Application button.
- In Choose Application, select SAML/WS-FED from the application type dropdown.
- Search for Barracuda WAF in the list, if you don't find Barracuda WAF in the list then, search for custom and you can set up your application in Custom SAML App.
2. Configure SSO in Barracuda WAF
To setup Barracuda WAF as the Service Provider, please follow the below steps:
-
Configure a SAML IdP Authentication Service
- The Identity Provider server should be configured as the authentication service on the ACCESS CONTROL > Authentication Services page, in the SAML Identity Provider tab. The Barracuda Web Application Firewall uses this information to communicate with the Identity Provider server to authenticate a user.
- Go to the ACCESS CONTROL > Authentication Services page, select the SAML Identity Provider tab, and specify values for the following:
|
Realm Name
|
Enter a name to identify the SAML authentication service on the Barracuda Web Application Firewall. |
|
Identity Provider Name
|
Enter a name to identify the Identity Provider on the Barracuda Web Application Firewall. |
|
Identity Provider Metadata Type
|
Select URL or File Upload to associate the metadata file. |
|
Metadata URL
|
You will find the Metadata URL in Step 1 |
|
Metadata File Upload
|
Click the Browse button to select the Identity Provider metadata file. Upload the Metadata file you downloaded in Step 1. |
- Click on Add.
- SAML authentication service with the specified values gets created under Existing Authentication Service. The Type for the SAML authentication service will be displayed as “SAMLSP”.
-
Enable Authentication and Configure SAML Service Provider
- Go to the ACCESS CONTROL > Authentication Policies page.
- In the Authentication Policies section, click on Edit Authentication next to the service to which you want to enable authentication.
- In the Edit Authentication Policies window:
- Configure the following in the Edit Authentication Policy section:
- Set Status to On.
- Select the SAML authentication service created in Configure a SAML IdP Authentication Service from the Authentication Service drop-down list.
- Configure the following in the SAML Service Provider Configuration section:
|
Organization Name
|
Enter your organization name. This name will be used when the Barracuda Web Application Firewall sends SAML requests to the IdP.
|
|
Organization URL
|
Enter the URL of the organization. Example: https://serviceprovider.com
|
|
Organization Display Name
|
Enter a name to be displayed to the users accessing this service.
|
|
SP Entity ID
|
Enter either the fully qualified domain name through which the service can be accessed or the SAML entity ID if you have any for the application. Example: https://waf.example.com/.
|
|
Choose the signing certificate.
|
It is recommended to select Encryption Certificate to avoid SAML vulnerability [CVE-2018-0486].
|
- Specify values for other parameters as required.
- Click Save.
-
After you have configured the Barracuda Web Application Firewall, you must generate the metadata file of the SAML service provider (i.e., the Barracuda Web Application Firewall), and export the metadata file to the Identity Provider (IdP).
To Generate the metadata file of the SAML Service Provider (SP):
- Go to the ACCESS CONTROL > Authentication Policies page.
- In the Authentication Policies section, click Generate next to the service under Metadata.
- Save the Service Provider (SP) metadata XML file to your local machine. Example: sp_metadata_app.xml, where “sp_metadata” indicates the Service Provider metadata file configured for the service “app”.
3. Test SSO Configuration
Test SSO login to your Barracuda WAF account with miniOrange IdP:
4. Configure Your User Directory (Optional)
miniOrange provides user authentication from various external sources, which can be Directories (like ADFS, Microsoft Active Directory, Microsoft Entra ID, OpenLDAP, Google, AWS Cognito etc), Identity Providers (like Okta, Shibboleth, Ping, OneLogin, KeyCloak), Databases (like MySQL, Maria DB, PostgreSQL) and many more. You can configure your existing directory/user store or add users in miniOrange.
- Click on Identity Providers >> Add Identity Provider in the left menu of the dashboard
- In Choose Identity Provider, select AD/LDAP Directories from the dropdown.
- Then search for AD/LDAP and click it.
- STORE LDAP CONFIGURATION IN MINIORANGE: Choose this option if you want to keep your configuration in miniOrange. If the active directory is behind a firewall, you will need to open the firewall to allow incoming requests to your AD.
- STORE LDAP CONFIGURATION ON PREMISE: Choose this option if you want to keep your configuration in your premise and only allow access to AD inside premises. You will have to download and install miniOrange gateway on your premise.
- Enter AD/LDAP Display Name and Identifier name.
- Select Directory Type as Active Directory.
- Enter the LDAP Server URL or IP Address against the LDAP Server URL field.
- Click on the Test Connection button to verify if you have made a successful connection with your LDAP server.
- In Active Directory, go to the properties of user containers/OU's and search for the Distinguished Name attribute. The bind account should have minimum required read privileges in Active Directory to allow directory lookups. If the use case involves provisioning (such as creating, updating, or deleting users or groups), the account must also be granted appropriate write permissions.
- Enter the valid Bind account Password.
- Click on the Test Bind Account Credentials button to verify your LDAP Bind credentials for LDAP connection.
- Search Base is the location in the directory where the search for a user begins. You will get this from the same place you got your Distinguished name.
- Select a suitable Search filter from the drop-down menu. If you use User in Single Group Filter or User in Multiple Group Filter, replace the <group-dn> in the search filter with the distinguished name of the group in which your users are present. To use custom Search Filter select "Write your Custom Filter" option and customize it accordingly.
- Click on the Next button, or go to the Login Options tab.
- You can also configure following options while setting up AD. Enable Activate LDAP in order to authenticate users from AD/LDAP. Click on the Next button to add user store.
Here's the list of the attributes and what it does when we enable it. You can enable/disable accordingly.
| Attribute |
Description |
| Activate LDAP |
All user authentications will be done with LDAP credentials if you Activate it |
| Fallback Authentication |
If LDAP credentials fail then user will be authenticated through miniOrange |
| Enable administrator login |
On enabling this, your miniOrange Administrator login authenticates using your LDAP server |
| Show IdP to users |
If you enable this option, this IdP will be visible to users |
| Sync users in miniOrange |
Users will be created in miniOrange after authentication with LDAP |
- Click on the Next button, or go to the Attributes tab.
Attributes Mapping from AD
User Import and Provisioning from AD
- If you want to set up provisioning, click here for detailed information. We will skip this step for now.
Test Connections
- You will see a list of directories under Identity Providers. From the dropdown, select AD/LDAP Directories, search for your configured directory, click the three dots next to it, and select Test Connection.
- A pop-up appears prompting you to enter a username and password to verify your LDAP configuration.
- On Successful connection with LDAP Server, a success message is shown.
Test Attribute Mapping
- You will see a list of directories under Identity Providers. From the dropdown, select AD/LDAP Directories, search for your configured directory, click the three dots next to it, and select Test Attribute Mapping.
- A pop‑up appears to enter a username and click Test.
- The Test Attribute Mapping Result will be displayed.
Set up AD as External Directory configuration is complete.
Note: Refer our guide to setup LDAP on windows server.
miniOrange integrates with various external user sources such as directories, identity providers, and etc.
5. Adaptive Authentication with Barracuda WAF
A. Restricting access to Barracuda WAF with IP Configuration
You can use adaptive authentication with Barracuda WAF Single Sign-On (SSO) to improve the security and functionality of Single Sign-On. You can allow a IP Address in certain range for SSO or you can deny it based your requirements and you can also challenge the user to verify his authenticity. Adaptive authentication manages the user authentication bases on different factors such as Device ID, Location, Time of Access, IP Address and many more.
You can configure Adaptive Authentication with IP Blocking in following way :
- Login to Self Service Console >> Adaptive Authentication >> Add Policy.
- Add a Policy Name for your Adative Authentication Policy.
- Select Action for Behavior Change, click the Edit link, and then choose the appropriate Action and Challenge Type for the user from that section.
Action for behavior Change Options :
| Attribute |
Description |
| Allow |
Allow users to authenticate and use services if Adaptive authentication condition is true. |
| Challenge |
Deny user authentications and access to services if Adaptive authentication condition is true. |
| Deny |
Challenge users with one of the three methods mentioned below for verifying user authenticity. |
Challenge Type Options :
| Attribute |
Description |
| User second Factor |
The User needs to authenticate using the second factor he has opted or assigned for such as
- OTP over SMS
- PUSH Notification
- OTP over Email and, many more.
|
| KBA (Knowledge-based authentication) |
The System will ask the user for 2 of 3 questions he has configured in his Self-Service Console. Only after the right answer to both questions is the user allowed to proceed further. |
| OTP over Alternate Email |
User will receive an OTP on the alternate email they have configured through the Self Service Console. Once the user provides the correct OTP, they are allowed to proceed further. |
- Now click Edit option from the IP Configuration section to configure custom IP range.
- Select Add IP if the User's IP Address is not in the configured list.
- Specify the IP Address that you want to whitelist. For the IP Range other than the whitelisted one, you can select the above setting to reflect.
- Choose either allow or deny by selecting the corresponding option from the dropdown.
- If a user tries to login with the whitelisted IP address, they will always be allowed access.
- We support IP address range in three formats i.e., IPv4, IPv4 CIDR, and IPv6 CIDR. You can choose whichever is suitable for you from the dropdown menu.
- You can add multiple IPs or IP ranges by clicking the + Add IP button.
- Once the changes are made, scroll down to the end and click on Save.
B. Adaptive Authentication with Limiting number of devices
Using Adaptive Authentication you can also restrict the number of devices the end user can access the Services on. You can allow end users to access services on a fixed no. of devices. The end users will be able to access services provided by us on this fixed no. of devices.
You can configure Adaptive Authentication with Device Restriction in following way
- Login to Self Service Console >> Adaptive Authentication >> Add Policy.
- Add a Policy Name for your Adaptive Authentication Policy.
- Select your Action for behavior Change and Challenge Type for user from the Action for behavior Change Section.
- On the Add Policy tab, go to the Device Configuration section and click the Edit button.
- Enter the Number of Device Registrations Allowed as per your requirement. (2-3 devices are recommended.)
- Choose Action if number of devices exceeded (This will override your setting for Action for behavior Change.)
- Challenge: The user needs to verify himself using any of the three methods mentioned in table in step 5.1
- Deny : Deny users access to the system
- Enable Mobile Device Restriction to block logins from mobile devices. This ensures all login attempts from mobile devices will be declined.
- Enable MAC Address Based Restriction if you want to restrict access based on device MAC address.
- Scroll down to the bottom of the page and click on Save.
C. Add Adaptive Authentication policy to Barracuda WAF
- Login to Self Service Console >> Policies >> Add Login Policy.
- Click on Edit icon option for predefined app policy.
- Set your policy in the Policy Name and select Password as First Factor.
- Enable Adaptive Authentication on Edit Login Policy page and select the required restriction method as an option.
- From Select Login Policy dropdown select the policy we created in last step and click on Submit.
D. Notification and Alert Message.
How to add a trusted Device
- When End-user log in to the self service console after the policy for device restriction is on, he is provided the option to add the current device as a trusted device.
External References
