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 Keycloak Server for OpenID Connect on the Barracuda Web Application Firewall

  • Last updated on

The Barracuda Web Application Firewall can authenticate users configured on Keycloak Server using OpenID Connect.

Perform the following steps to configure Keycloak Server on the Barracuda Web Application Firewall:

Step 1 - Create an HTTPS Service on the Barracuda Web Application Firewall. 

For more information on how to create a HTTPS service, see Creating an HTTPS Service

Step 2 - Generating Keycloak Server's Client ID and Client Secret
  1. Log into the Keycloak Server Administrator Console and provide administrator username and password.
  2. In the left pane, select Add Realm and specify the name of the realm. Example, Test.
  3. Select the realm that you added.
  4. Click Clients > Create to create a client. Example, adc-user. The client is displayed in the client ID column.
  5. Select the client that you created and configure Redirect URI for the client in the Valid Redirect URI box.
  6. Save the configuration.

     

Step 3 - Configuring Keycloak OpenID Connect provider on the Barracuda Web Application Firewall
  1. Navigate to ACCESS CONTROL > Authentication Services and click the OpenID Connect tab.
  2. In the Realm Name box, specify a name to identify the OpenID Connect.
  3. In the Open ID Connect Alias box, specify the OpenID Connect alias name to identify the OpenID Connect provider on the Barracuda Web Application Firewall. Example: Keycloak
  4. Choose Discovery URL as the mode to fill the end point URLs from metadata URL automatically.
  5. Specify the metadata URL of the Keycloak Server OpenID Connect. Example, https://<KeyCloak OpenID server IP>/.well -known /openid -configuration

  6. Click Retrieve to display the end point URLs in the fields by default (except for client/clientsec).
  7. Configure the client ID and client secret that you obtained when registering the application with the Keycloak OpenID Connect provider.
  8. Click Add. The Keycloak OpenID Connect authentication service is displayed in the Existing Authentication Service section.
Step 4 - Configure the Authentication Policy for the Service
  1. Go to the ACCESS CONTROL > Authentication Policies page.
  2. In the Authentication Policies section, for the service to which you want to enable authentication, click the drop-down list and select Edit Authentication from the Options column.
  3. In the Edit Authentication Policies window, configure the following:
    1. Set Status to  On .

    2. From the Authentication Service drop-down list, select the authentication service realm.  

    3. Enter the redirect URL. Ensure that you use the same redirect URL that was configured on the Keycloak server. For example, if the redirect URL configured on the Google server is  https://www.oauthtest.com/redirect.html, you can use /redirect.html here. 
  4. The login page is selected by default in the Access Control Pages section.

  5. (Optional) In the OpenID Connect Claim Configuration section, specify  the claim name and local ID received from the identity provider that needs to be sent to the application server.

  6. Click Save.

Step 5 - Configure the Authorization Policy for the Service
  1. Go to the ACCESS CONTROL > Authentication Policies page.
  2. In the Authentication Policies section, for the service to which you want to enable authorization.
  3. In the  Add Authorization Policy  section, configure the following:
    1. Policy Name – Enter a name for the policy.
    2. Set Status to  On .
    3. URL Match  – Enter the URL that needs to be matched in the request. For example  “/*”
    4. Host Match  – Enter the host name to be matched against the host in the request.
  4. Click Save.
Last updated on