Citrix Integration
General Overview
This guide explains the configuration of multi-factor authentication (MFA) for Citrix Gateway utilizing Mirket as the identity provider. Prior configuration and deployment of Citrix Gateway are required before setting up MFA with Mirket.
Citrix Gateway offers various MFA configuration modes. In this integration, we'll configure Citrix Gateway to authenticate local Mirket users using the PAP authenticate protocol.
Note: Use the MS-CHAPv2 authentication protocol when configuring Citrix Gateway to authenticate with users pulled from Active Directory. Also, make sure that NPS is installed, as the MS-CHAPv2 protocol does not support OTP.
To enable RADIUS authentication with Citrix Gateway, you'll need to install and set up the Mirket. The Mirket acts as a RADIUS server and should be installed within a network that has both Internet connectivity and access to your RADIUS clients.
This integration was tested with version NS13.1: Build 12.11.nc of Citrix ADC, where Citrix Gateway is a component of Citrix ADC.
Preparation Steps
Before proceeding with these procedures, ensure the following:
You've completed the installation and configuration of the Mirket (go to Mirket Installation Steps).
End-users can access the Citrix Gateway.
Configuring Citrix Gateway
RADIUS Authentication Policy and Server Creation
Access the Citrix Gateway administrator web console.
Select the Configuration tab and go to Citrix Gateway > Policies > Authentication > RADIUS.

Click on Add and enter a policy name in the Name field.

Click on the Add option next to the Server field.
Enter a server name in the Name field. Then choose the Server IP option.
Input the IP address of the Mirket (RADIUS server) in the IP Address field.
Input the port number for communication with the Mirket (RADIUS server) in the Port field. The default gateway port is 1812.
Assign a shared secret key to identify your RADIUS client in the Secret Key and Confirm Secret Key fields. Make sure to use the same shared secret key while configuring your RADIUS client resource in Mirket.
Input 30 in the Time-out field. Then click on Create.

Choose the "ns_true" option from the Saved Policy Expressions dropdown list.

Then click on the Create option to complete the process.
If a warning about classic authentication policies pops up, click on OK.

Connect RADIUS to the Virtual Server
Select the Configuration tab and go to Citrix Gateway > Virtual Servers. Then select your virtual server. You can refer to the Citrix documentation for creating a virtual server.

Click on Edit. Then click the "+" icon next to the Basic Authentication field.

Choose the "RADIUS" option from the Choose Policy dropdown list.
Choose the "Primary" option from the Choose Type dropdown list. Then click on Continue.

Click on the ">" icon next to the Select Policy field under the Policy Binding section.

Select the RADIUS policy that was previously created. Then click on the "Select" option.

Then, click on Bind.
Configure Mirket
To enable Mirket to receive authentication requests from Citrix Gateway, follow these steps:
Define Citrix Gateway as a RADIUS client resource within Mirket.
Create an authentication policy for the Citrix Gateway RADIUS client resource or include it in an existing authentication policy.
Attach the Citrix Gateway resource to the Mirket Radius.
Add Citrix as a Resource in Mirket with Radius Gateway
Before starting, ensure that you have installed Mirket Radius Gateway from the Configuration > Gateway. To add a Radius Gateway to the Mirket, follow these steps:
Go to Configuration > Gateway and click on the Add Radius Gateway button.
On the displayed screen, enter a name for your Radius Gateway in the Name field.
Enter the SAM value of the gateway in the Sam Value field. In Mirket, user identification is done using the SAM (Security Account Manager) name. This is preferred over the standard username. This username is used for authentication and access controls.
Enter the IP address of the server where the gateway is installed in the Host IP Address field.
Enter the authentication port value you set for the gateway in the Auth Port field. The default value is 1812.
Enter the accounting port value you specified for the gateway in the Acc Port field. The default value is 1813. Note: After completing these fields, you must create a RADIUS client for the newly created RADIUS Gateway.
Click on the Add Radius Client option at the bottom of the displayed screen.
Enter a name for your Radius Client in the Radius Client field.
Enter the IP address of the client(firewall) that will communicate with the gateway in the IP Address field.
Enter the secret key that the client will communicate with the gateway in the Secret Key field.

Click on the Save button to confirm the settings.

Configuring Radius Gateway
After creating the Radius Gateway, click on the Download > Config from the menu on the right side of the gateway.

This option will generate a script related to the gateway, which will be displayed from the RADIUS Setup config file. The config file will automatically begin downloading once this option is selected.

Replace the existing config file in the
"C:\MirketRadius"
directory with the downloaded file. Alternatively, copy the displayed script and paste it into the config file in"C:\MirketRadius"
.

Then, restart the Mirket Radius Service.

You can check whether the Radius Gateway you created is active by navigating to Configuration > Gateway.
User and Group configuration on Mirket
To set up multifactor authentication, make sure you have at least one user or group in Mirket.
If it is preferred to use a local user, you can first create a local group and then create a local user and make the user a member of the group. Alternatively, you can create a local user without creating a local group.
If it is preferred to use LDAP users, the priority External Source is created by pulling users from Active Directory or OpenLDAP in Mirket. Note: Before proceeding, ensure that you have installed Mirket LDAP Gateway. (Refer to create LDAP Gateway.)
Add a Radius Rule to Mirket
Radius Rules define user access to resources and the authentication methods available (such as SMS, Approve / Deny, OTP, etc.).
First, you should follow these steps:
Go to Configuration > Radius Rules.
Click on the Add Radius Rule button.
On the displayed screen, enter a name for the rule in the Name field.
Enter the rule description in the Description field.
Select the Radius Client to which the rule will apply from the Radius Client dropdown list.
Enter the source IP addresses to which the rule will apply in the Source Adress field.
Select the source countries where the rule will be applied from the Source Country dropdown list.
Click on the Next button.

Specify whether the rule will be applied to a user or a group.
After specifying, click on the Next button.

Select the users or groups to which the rule will apply. Transfer your selections to the Selected Users/Groups table by clicking the arrow icon next to the Available Users/Groups table.
Click on the Next button.


Select the time period when the rule will run.
All: The rule will run every day.
Recurring: The rule will run on the specified days and times.
One Time: The rule will run within the date range you specify.
After selecting, click on the Next button.

Specify whether the user or group will be granted access based on the rule in the Action field.
Select the authentication provider to which the rule will apply from the Auth Method dropdown list.

Click on Save to confirm the settings.

Test the Integration
To validate the integration between Mirket MFA and your Citrix Gateway, perform authentication using a mobile token on your mobile device. For RADIUS resources, available authentication methods include Approve/Deny authentication.
In this example, we illustrate the use of the Approve/Deny authentication method.
Go to the login page of the virtual server in a web browser.
Enter your Mirket username and password.
Click on Log On. Then, select the 'Approve' option(found in the Mirket mobile app) immediately and make sure it doesn't time out.
Related Topics
Last updated