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 CloudGen Firewall

Attention

Barracuda CloudGen Firewall version 8.0 is a cloud-only version. It is currently not available for on-premises deployments and can only be deployed in Microsoft Azure, Amazon Web Services, or Google Cloud Platform public clouds.

How to Configure Access Control Policies for One-Time Password Authentication

  • Last updated on

Google Authenticator or Microsoft Authenticator are authentication schemes using Time-Based One-Time Passwords (TOTP) generated by an app on your mobile device to authenticate the user. The app generates temporary six-digit numbers calculated from a shared secret and the current time. To be able to use this on the CloudGen Firewall, the Google Authenticator app must be enrolled by the user in a two-step process. To associate the Google/Microsoft Authenticator with a user and group information, a helper scheme such as MSAD or LDAP must be configured. Google/Microsoft Authenticator is supported for CudaLaunch and the SSL VPN web portal. For users to be able to self-enroll, they must be able to access the SSL VPN through an Access Control Policy that is not using Google/Microsoft Authenticator as an authentication method. After all users are enrolled, the admin can then switch to an Access Control Policy requiring Google/Microsoft Authenticator. To be able to share the linked accounts over managed firewalls in a single HA cluster, use a repository entry.

auth_02.png

Enrolling Mobile Devices

  • Create an SSL VPN Access Control Policy that allows users to log in without Google/Microsoft Authenticator.
  • Instruct users to log into CudaLaunch or the SSL VPN web portal to enroll their devices. For more information, see Enroll your Mobile Device for use Time-Based One-Time Passwords (TOTP).
  • Deactivate the original Access Control Policy and enable an Access Control Policy using Google/Microsoft Authenticator.

Before You Begin

  • Enable SSL VPN. For more information, see How to Configure the SSL VPN Service.
  • Configure an authentication scheme with user/group information such as MSAD or LDAP to be used as the User Info Helper Scheme. For more information, see Authentication.

Step 1. Enable Google Authenticator

  1. Go to CONFIGURATION > Configuration Tree > Box > Infrastructure Services > Authentication Service.
  2. In the left menu, click Google Authentication.
  3. Click Lock.
  4. From the Google Authentication Scheme drop-down list, select Yes.
  5. (optional) Set User Info Helper Scheme to MSAD if group information is required.
    enable_google_auth.png
  6. Click Send Changes and Activate.

Step 2. Configure an MFA Access Control Policy for Google Authentication

Configure an Access Control Policy using Google Authentication as the secondary authentication scheme.

  1. Go to CONFIGURATION > Configuration Tree > Box > Virtual Servers > your virtual server > Assigned Service > VPN > SSL-VPN.
  2. In the left menu, click Access Control Policies.
  3. Click Lock.
  4. Click + to add an Access Control Policy. The Access Control Policies window opens.
  5. Enter the Name and click OK.
  6. In the Access Control Policy section, select the Active check box.
    activate_auth_scheme_00.png
  7. (optional) Add Allowed Groups and Blocked Groups.
  8. (optional) To use multi-factor authentication, add the primary authentication scheme:
    1. Click + to add the primary authentication scheme to the Authentication Scheme table. The Authentication Scheme window opens.
      add_authentication_scheme_00.png
    2. From the Authentication Scheme drop-down list, select the primary authentication scheme. E.g., MS Active Directory, or LDAP
      add_authentication_scheme01.png
    3. Click OK.
  9. Click + to add Google Authentication to the Authentication Scheme table. The Authentication Scheme window opens.  
  10. In the Authentication Schemes window, set Authentication Scheme to GoogleAuth.
    set_auth_scheme_googleauth_00.png
  11. Click OK. 
  12. (optional) Click + to add NAC criteria to the Network Access Control Criteria table.
  13. Click OK.
  14. Click Send Changes and Activate.

Step 3. Activate Access Control Policy for Google Authentication

  1. Go to CONFIGURATION > Configuration Tree > Box > Virtual Servers > your virtual server > Assigned Services > VPN > SSL-VPN.
  2. In the left menu pane, click Login.
  3. Click Lock.
  4. In the Login section, click and select the Access Control Policy created in Step 2.
    add_authentication_scheme02.png
  5. Click Send Changes and Activate.

Step 4. (Single HA Cluster only) Create a Repository Entry and Link

To be able to share the linked Google Authenticator accounts over managed firewalls in a high availability cluster, use a repository entry and create repository links. The primary and secondary firewall must use the repository entry.

  1. Log into the Control Center.
  2. Go to Your Managed Firewall > Infrastructure Services.
  3. Expand the configuration node, right-click Google Authenticator and click Copy To Repository. The Select Object window opens.
  4. Enter a Name for the new Object.
    google_auth_repository_01.png
  5. Click OK.
  6. Right-click Google Authenticator again and click Lock
  7. Right-click Google Authenticator again and click Link From Repository.
    google_auth_repository_02.png
  8. Select the Repository entry you just created.
    google_auth_repository_03.png
  9. Click OK.
  10. Click Activate.

You can now link this repository entry to the secondary firewall in your HA cluster.

google_auth_repository_04.png

Last updated on