Manually Configure the Firebox for Mobile VPN with SSL

1. Select VPN > Mobile VPN.

2. To configure a new Mobile VPN with SSL configuration, in the SSL section, click Manually Configure.

3. To edit an existing configuration, in the SSL section, click Configure.
   The Mobile VPN with SSL Configuration page opens.

4. Select the Activate Mobile VPN with SSL check box.

5. In the Primary text box, type a public IP address or domain name.
   This is the IP address or domain name that Mobile VPN with SSL clients connect to by default. This can be an external IP address, secondary external IP address, or external VLAN. For a device in drop-in mode, use the IP address assigned to all interfaces.

You do not have to regenerate the SSL VPN certificate if you change this IP address later. For more information about certificates, go to Use Mobile VPN with SSL with an OpenVPN Client.

6. If your Firebox has more than one external address, in the Backup text box, type a different public IP address.
   This is the IP address that the Mobile VPN with SSL client connects to if it is unable to establish a connection with the primary IP address. If you add a secondary IP address, make sure it is an IP address assigned to a Firebox external interface or VLAN. If you want the Mobile VPN with SSL client to use a secondary IP address, you must also select the Auto reconnect after a connection is lost check box in the Authentication settings, as described in the Authentication section.

7. To configure the networking and IP address pool settings, go to the next section in this topic.

1. Select VPN > Mobile VPN > Get Started.

2. In the SSL section, click Manually Configure.
   The Mobile VPN with SSL Configuration dialog box opens.

3. Select the Activate Mobile VPN with SSL check box.

4. In the Primary text box, type or select a public IP address or domain name. This is the IP address or domain name that Mobile VPN with SSL clients connect to by default. This can be an external IP address, secondary external IP address, or external VLAN. For a device in drop-in mode, use the IP address assigned to all interfaces.

You do not have to regenerate the SSL VPN certificate if you change this IP address later. For more information about certificates, go to Use Mobile VPN with SSL with an OpenVPN Client.

5. If your Firebox has more than one external address, in the Backup text box, type or select a different public IP address.
   This is the IP address that the Mobile VPN with SSL client connects to if it is unable to establish a connection with the primary IP address. If you add a backup IP address, make sure it is an IP address assigned to a Firebox external interface or VLAN. If you want the Mobile VPN with SSL client to use a backup IP address, you must also select the Auto reconnect after a connection is lost check box in the Authentication settings.

1. In the Networking and IP address pool section, from the drop-down list, select the method the Firebox uses to send traffic through the VPN tunnel:

   • Select Bridge VPN Traffic to bridge SSL VPN traffic to a network you specify. When you select this option, you cannot filter traffic between the SSL VPN users and the network that the SSL VPN traffic is bridged to.
   • Select Routed VPN Traffic to route VPN traffic to specified networks and resources. This is the default for all Fireboxes.

2. Select or clear the Force all client traffic through the tunnel check box.

   • To route all traffic from the VPN client to your private network and to the Internet through the tunnel, select Force all client traffic through tunnel.
     This option sends all external traffic through the Firebox policies you create and offers consistent security for mobile users. However, because it requires more Firebox processing power, access to Internet resources can be very slow for mobile users.
     For information about how to allow clients to access the Internet when this option is selected, go to Options for Internet Access Through a Mobile VPN with SSL Tunnel.

   • To route only traffic from the VPN client to your private networks through the tunnel, clear the Force all client traffic through tunnel check box.
     This option gives your users better network speeds by only routing traffic to private network resources through the Firebox. Other traffic to the Internet does not go through the tunnel and is not restricted by the policies on your Firebox.

     1. To allow access to all internal networks, select Allow access to all Trusted, Optional, and Custom networks.
     2. To restrict Mobile VPN with SSL client access to only specified devices on your private network, select Specify allowed resources. To specify an allowed resource, type the IP address of the network resource in slash notation and click Add.

1. In the Networking and IP Address Pool section, from the drop-down list, select one of these options:

   1. Routed VPN Traffic — To route VPN traffic to specified networks and resources. This is the default option.
   2. Bridge VPN Traffic — To bridge SSL VPN traffic to a network you specify. Tip! When you select this option, you cannot filter traffic between the SSL VPN users and the network that the SSL VPN traffic is bridged to.

2. Select one of these options:

   1. To route all traffic from the VPN client to your private network and to the Internet through the tunnel, select Force all client traffic through tunnel. Tip! This option sends all external traffic through the Firebox policies you create and offers consistent security for mobile users. However, because it requires more Firebox processing power, access to Internet resources can be very slow for mobile users. For information about how to allow clients to access the Internet when this option is selected, go to Options for Internet Access Through a Mobile VPN with SSL Tunnel.
   2. To route only traffic from the VPN client to your private networks through the tunnel, clear the Force all client traffic through tunnel check box.

3. If you cleared the Force all client traffic through tunnel check box, select one of these options:

   1. To allow access to all internal networks, select Allow access to all Trusted, Optional, and Custom networks.
   2. To restrict Mobile VPN with SSL client access to only specified devices on your private network, select Specify allowed resources. To specify an allowed resource, type the IP address of the network resource in slash notation and click Add.

Routed VPN traffic

1. For the virtual IP address pool, keep the default setting of 192.168.113.0/24 or enter a different range.
2. Type the IP address of the subnet in slash notation. IP addresses from this subnet are automatically assigned to Mobile VPN with SSL client connections. You cannot assign an IP address to a specific user.

Bridge VPN traffic

1. From the Bridge to interface drop-down list, select the name of the interface to bridge to. You can bridge VPN traffic only to a LAN bridge.

For more information, go to Plan Your Mobile VPN with SSL Configuration.

2. In the Start and End text boxes, type the IP addresses in the range that you want to assign to Mobile VPN with SSL client connections. The Start and End IP addresses must be on the same subnet as the bridged interface.
   For more information about virtual IP addresses, go to Virtual IP Addresses and Mobile VPNs.

Routed VPN traffic

For the Virtual IP Address Pool, keep the default setting of 192.168.113.0/24 or enter a different range.

Bridge VPN traffic

1. From the Bridge to interface drop-down list, select the name of the interface to bridge to. You can bridge VPN traffic only to a LAN bridge.

For more information, go to Plan Your Mobile VPN with SSL Configuration.

2. In the Start and End text boxes, type the first and last IP addresses in the range that you want to assign to Mobile VPN with SSL client connections. When you bridge VPN traffic to a LAN bridge, the Start and End IP addresses must be on the same subnet as the bridged interface.

For more information about virtual IP addresses, go to Virtual IP Addresses and Mobile VPNs.

1. On the Mobile VPN with SSL page, select the Authentication tab.
   

2. From the Authentication Server drop-down list, select an authentication server you want to use for Mobile VPN with SSL user authentication.
   Only enabled authentication method servers and domains are listed. For information about supported authentication methods, go to Authentication Server Types.

3. Click Add.

4. Repeat Steps 2 to 3 to add more authentication servers.

5. If you add multiple authentication servers, select the server you want to be the default server. Click Move Up to move that server to the top of the list.
   Mobile VPN with SSL uses the default authentication server unless a user specifies an authentication server in the Username text box on the Mobile VPN with SSL client.
   

6. To add users and groups, go to the next section in this topic.

If you configure Mobile VPN with SSL to use more than one authentication server, users who do not use the default authentication server must specify the authentication server or domain as part of the user name. For more information and examples, go to Download, Install, and Connect the Mobile VPN with SSL Client.

1. In the Mobile VPN with SSL Configuration dialog box, select the Authentication tab.
   

2. Click Configure.
   For information about supported authentication methods, go to Authentication Server Types.

3. To select an authentication server that is already configured on your Firebox, select the check box for that server.

4. If you add multiple authentication servers, select the server you want to be the default server. Click Make Default to move that server to the top of the list.
   Mobile VPN with SSL uses the default authentication server unless a user specifies an authentication server in the Username text box on the Mobile VPN with SSL client.

5. If you want the Mobile VPN with SSL client to be able to automatically reconnect, select Auto reconnect after a connection is lost.
   If you enable this option, mobile users can select a check box on the Mobile VPN with SSL client to control whether the client automatically reconnects. You must also enable this option if you want the client to automatically use the secondary IP address when it cannot connect to the primary IP address. By default, the keep-alive interval is 10 seconds, and the keep-alive timeout is 60 seconds. Do not enable this setting if you require multi-factor authentication for Mobile VPN with SSL.
   

6. To require users to authenticate after a Mobile VPN with SSL connection is disconnected, select the Force users to authenticate after a connection is lost check box .
   We recommend that you select this check box if you use a two-factor authentication method with a one-time password, such as RADIUS or SecurID. If you do not force users to authenticate after a connection is lost, the automatic connection attempt can fail. This is because the Mobile VPN with SSL client tries to use the one-time password the user originally entered, which is no longer correct, to automatically reconnect after a connection is lost.

7. If you want the Mobile VPN with SSL client to be able to remember the password, select the Allow the Mobile VPN with SSL client to remember password check box.
   If you enable this option, the mobile user can select a check box in the Mobile VPN with SSL client to control whether the client remembers the password.

8. To add users and groups, go to the next section in this topic.

If you configure Mobile VPN with SSL to use more than one authentication server, users who do not use the default authentication server must specify the authentication server or domain as part of the user name. For more information and examples, go to Download, Install, and Connect the Mobile VPN with SSL Client.

1. In the Mobile VPN with SSL page, select the Authentication tab.
   The Authentication settings open.

2. In the Users and Groups section, from the Create new drop-down list, select an authentication server.

3. From the adjacent drop-down list, select User or Group.

4. Click Add.
   If you selected Firebox-DB, the Firebox User or Firebox Group dialog box opens.
   If you selected Any, the Add User or Group dialog box opens.

5. To add a new Firebox-DB user, follow Steps 6 to 14 in the Define a New User for Firebox Authentication topic.

6. To add a new Firebox-DB group, follow Steps 4 to 9 in the Define a New Group for Firebox Authentication topic.

7. To add new users and groups for third-party authentication, follow Steps 4 to 9 in the Use Users and Groups in Policies topic.

8. (Optional) To apply enforcement settings to Mobile VPN with SSL groups:
   1.  Select the check box for a group.
   2. In Fireware v12.9 or higher, in the Network Access Enforcement column, select Yes.
      
9. To disable enforcement for a group, select the check box for that group and select No.

10. If you want the Mobile VPN with SSL client to be able to automatically reconnect, select Auto reconnect after a connection is lost. If you enable this option, mobile users can select a check box on the Mobile VPN with SSL client to control whether the client automatically reconnects. You must also enable this option if you want the client to automatically use the secondary IP address when it cannot connect to the primary IP address.

11. To require users to authenticate after a Mobile VPN with SSL connection is disconnected, select the Force users to authenticate after a connection is lost check box . We recommend that you select this check box if you use a two-factor authentication method with a one-time password, such as RADIUS or SecurID. If you do not force users to authenticate after a connection is lost, the automatic connection attempt can fail. This is because the Mobile VPN with SSL client tries to use the one-time password the user originally entered, which is no longer correct, to automatically reconnect after a connection is lost.

12. If you want the Mobile VPN with SSL client to be able to remember the password, select the Allow the Mobile VPN with SSL client to remember password check box. If you enable this option, the mobile user can select a check box in the Mobile VPN with SSL client to control whether the client remembers the password.

1. Select Setup > Authentication >Users and Groups.

2. Click New.

3. Select Firebox-DB User/Group or External User/Group.
   If you selected Firebox-DB User/Group, the Authentication Servers dialog box Firebox-DB tab opens.
   If you selected External User/Group, the Add User or Group dialog box opens.

4. To add a new Firebox-DB user, follow Steps 5–14 in the Define a New User for Firebox Authentication topic.

5. To add a new Firebox-DB group, follow Steps 4–9 in the Define a New Group for Firebox Authentication topic.

6. To add new users and groups for third-party authentication, follow Steps 4–11 in the Use Users and Groups in Policies topic.

7. (Optional) To apply enforcement settings to Mobile VPN with SSL groups:
   1. Select the check box for a group.
   2. In Fireware v12.9 or higher, select Network Access Enforcement check box.
      
8. To disable enforcement for a group, select the check box for that group and select No.

1. Select VPN > Mobile VPN with SSL.
   The Mobile VPN with SSL Configuration page opens.

2. Select the Advanced tab.

3. Configure the authentication, encryption, port, and timeout settings:

Authentication

Select an authentication method for the connection: SHA-1, SHA-256, or SHA-512. We recommend the SHA-2 variants, SHA-256 and SHA-512, which are stronger than SHA-1.

Encryption

Select an algorithm to encrypt the traffic: 3DES, AES (128-bit), AES (192-bit), or AES (256-bit). In Fireware v12.2 or higher, you can also select AES-GCM (128-bit), AES-GCM (192-bit), or AES-GCM (256-bit). We recommend AES encryption. For the best performance, choose a 128-bit AES variant. For the strongest encryption, choose a 256-bit AES variant.

If you select 3DES, be aware of a potential, but unlikely, security attack. For more information, go to Sweet32 Vulnerability in the WatchGuard Knowledge Base.

Data channel

Select the protocol and port that Mobile VPN with SSL uses to send data after a VPN connection is established. You can use the TCP or UDP protocol. The default protocol and port for Mobile VPN with SSL is TCP port 443. This is also the standard protocol and port for HTTPS traffic. You can use port 443 for Mobile VPN with SSL as long as you do not use the same external IP address in an incoming HTTPS policy.

If you change the data channel to use a port other than 443, users must manually type this port in the Mobile VPN with SSL connection dialog box. For example, if you change the data channel port to 444, and the Firebox IP address is 203.0.113.2, users must type 203.0.113.2:444 instead of 203.0.113.2.

If the port is set to the default 443, users must only type the IP address of the Firebox. It is not necessary to type :443 after the IP address.

For more information, go to Choose the Port and Protocol for Mobile VPN with SSL.

Mobile VPN with SSL does not support a UDP data channel for VPN connections to a secondary external interface IP address.

Configuration channel

The Configuration Channel specifies the channel where Mobile VPN with SSL users can download SSL client software.

Select the protocol and port that Mobile VPN with SSL uses to negotiate the data channel and to download configuration files. If you set the data channel protocol to TCP, the configuration channel automatically uses the same port and protocol. If you set the data channel protocol to UDP, you can set the configuration channel protocol to TCP or UDP, and you can use a different port than the data channel.

In Fireware v12.1.x, the Configuration Channel shows in the VPN Portal settings and is named the VPN Portal port. For configuration instructions that apply to Fireware v12.1.x, go to Configure the VPN Portal settings in Fireware v12.1.x in the WatchGuard Knowledge Base.

Keep-Alive Interval

Specify how often the Firebox sends traffic through the tunnel to keep the tunnel active when there is no other traffic sent through the tunnel. The default value is 10 seconds.

Keep-Alive Timeout

Specify how long the Firebox waits for a response. If there is no response before the timeout value, the tunnel is closed and the client must reconnect. The default value is 60 seconds.

Renegotiate Data Channel

If a Mobile VPN with SSL connection has been active for the amount of time specified in the Renegotiate Data Channel text box, the Mobile VPN with SSL client must create a new tunnel. The minimum value is 60 minutes. The default value is 480 minutes.

4. Configure the DNS settings:
   

In Fireware v12.2.1 or higher, you can assign or not assign the Network (global) DNS/WINS settings to Mobile VPN with SSL clients.

Assign the network DNS/WINS settings to mobile clients

If you select this option, mobile clients receive the DNS and WINS settings you specify at Network > Interfaces > DNS/WINS. For example, if you specify the DNS server 10.0.2.53 in the Network DNS/WINS settings, mobile VPN clients use 10.0.2.53 as a DNS server.

By default, the Assign the Network DNS/WINS Server settings to mobile clients setting is selected for new mobile VPN configurations.

Do not assign DNS or WINS settings to mobile clients

If you select this option, mobile clients do not receive DNS or WINS settings from the Firebox.

If your Mobile VPN with SSL configuration does not specify DNS settings, when you upgrade to Fireware v12.2.1, the Do not assign DNS or WINS settings to mobile clients option is selected.

Assign these settings to mobile clients

If you select this option, mobile clients receive the domain name, DNS server, and WINS server settings you specify in this section. For example, if you specify example.com as the domain name and 10.0.2.53 as the DNS server, mobile clients use example.com for unqualified domain names and 10.0.2.53 as the DNS server.

You can specify one domain name, up to two DNS server IP addresses, and up to two WINS server IP addresses.

For more information on DNS and WINS, go to Name Resolution for Mobile VPN with SSL.

In Fireware v12.2 or lower, you can specify a domain name, DNS server settings, and WINS server settings, but you cannot select to assign or not assign the Network (global) DNS/WINS settings to Mobile VPN with SSL clients.

1. Select VPN > Mobile VPN > SSL.
   The Mobile VPN with SSL Configuration dialog box opens.

2. Select the Advanced tab.
3. Configure the authentication, encryption, port, and timeout settings:

Authentication

Select an authentication method for the connection: SHA-1, SHA-256, and SHA-512. We recommend the SHA-2 variants, SHA-256 and SHA-512, which are stronger than SHA-1.

Encryption

Select an algorithm to encrypt the traffic: 3DES, AES (128-bit), AES (192-bit), or AES (256-bit). In Fireware v12.2 or higher, you can also select AES-GCM (128-bit), AES-GCM (192-bit), or AES-GCM (256-bit). We recommend AES encryption. For the best performance, choose a 128-bit AES variant. For the strongest encryption, choose a 256-bit AES variant.

If you select 3DES, be aware of a potential, but unlikely, security attack. For more information, go to Sweet32 Vulnerability in the WatchGuard Knowledge Base.

Data channel

Select the protocol and port that Mobile VPN with SSL uses to send data after a VPN connection is established. You can use the TCP or UDP protocol. The default protocol and port for Mobile VPN with SSL is TCP port 443. This is also the standard protocol and port for HTTPS traffic. You can use port 443 for Mobile VPN with SSL as long as you do not use the same external IP address in an incoming HTTPS policy.

If you change the data channel to use a port other than 443, users must manually type this port in the Mobile VPN with SSL connection dialog box. For example, if you change the data channel port to 444, and the Firebox IP address is 203.0.113.2, users must type 203.0.113.2:444 instead of 203.0.113.2.

If the port is set to the default 443, users must only type the IP address of the Firebox. It is not necessary to type :443 after the IP address.

For more information, go to Choose the Port and Protocol for Mobile VPN with SSL.

Mobile VPN with SSL does not support a UDP data channel for VPN connections to a secondary external interface IP address.

Configuration channel

The Configuration Channel specifies the channel where Mobile VPN with SSL users can download SSL client software.

Select the protocol and port that Mobile VPN with SSL uses to negotiate the data channel and to download configuration files. If you set the data channel protocol to TCP, the configuration channel automatically uses the same port and protocol. If you set the data channel protocol to UDP, you can set the configuration channel protocol to TCP or UDP, and you can use a different port than the data channel.

In Fireware v12.1.x, the Configuration Channel shows in the VPN Portal settings and is named the VPN Portal port. For configuration instructions that apply to Fireware v12.1.x, go to Configure the VPN Portal settings in Fireware v12.1.x in the WatchGuard Knowledge Base.

Keep-alive Interval

Specify how often the Firebox sends traffic through the tunnel to keep the tunnel active when there is no other traffic sent through the tunnel.

Keep-alive Timeout

Specify how long the Firebox waits for a response. If there is no response before the timeout value, the tunnel is closed and the client must reconnect.

Renegotiate Data Channel

If a Mobile VPN with SSL connection has been active for the amount of time specified in the Renegotiate Data Channel text box, the Mobile VPN with SSL client must create a new tunnel. The minimum value is 60 minutes.

Restore Defaults

Click to reset the Advanced tab settings to their default values. All DNS and WINS server information on the Advanced tab is deleted.

4. Configure the DNS settings:

Assign the network DNS/WINS settings to mobile clients

If you select this option, mobile clients receive the DNS and WINS settings you specify at Network > Interfaces > DNS/WINS. For example, if you specify the DNS server 10.0.2.53 in the Network DNS/WINS settings, mobile VPN clients use 10.0.2.53 as a DNS server.

By default, the Assign the Network DNS/WINS Server settings to mobile clients setting is selected for new mobile VPN configurations.

Do not assign DNS or WINS settings to mobile clients

If you select this option, mobile clients do not receive DNS or WINS settings from the Firebox.

If your Mobile VPN with SSL configuration does not specify DNS settings, when you upgrade to Fireware v12.2.1, the Do not assign DNS or WINS settings to mobile clients option is selected.

Assign these settings to mobile clients

If you select this option, mobile clients receive the domain name, DNS server, and WINS server settings you specify in this section. For example, if you specify example.com as the domain name and 10.0.2.53 as the DNS server, mobile clients use example.com for unqualified domain names and 10.0.2.53 as the DNS server.

You can specify one domain name, up to two DNS server IP addresses, and up to two WINS server IP addresses.

For more information on DNS and WINS, go to Name Resolution for Mobile VPN with SSL.

In Fireware v12.2 or lower, you can specify a domain name, DNS server settings, and WINS server settings, but you cannot select to assign or not assign the Network (global) DNS/WINS settings to Mobile VPN with SSL clients.

1. Select Firewall > Firewall Policies.
   The Policies page opens.

2. Click Add Policy.

3. From the Packet Filter drop-down list, select Any.

4. In the Name text box, type a descriptive name for the policy.

5. Click Add Policy.

6. On the Settings tab, in the From section, select Any-Trusted. Click Remove.

7. In the From section, click Add.
   The Add Member dialog box opens.

8. From the Member Type drop-down list, select SSLVPN Group.

9. Select SSLVPN-Users.

10. To close the Add Member dialog box, click OK.

11. In the To section, select Any-External. Click Remove.

12. In the To section, click Add.
    The Add Member dialog box opens.

13. From the member list, select Any-Trusted.

14. Click OK.

15. Click Save.

1. Click .
   Or, select Edit > Add Policies.
   The Add Policies dialog box opens.

2. Expand the Packet Filters folder.
   A list of templates for packet filters opens.

3. Select Any.

4. Click Add.
   The New Policy Properties dialog box opens.
   

5. In the Name text box, type a descriptive name for the policy.

6. On the Policy tab, in the From section, select Any-Trusted. Click Remove.

7. In the From section, click Add.
   The Add Address dialog box opens.

8. Click Add User.

9. From the two Type drop-down lists, select SSL VPN for the first list and Group for the second list.

10. Select SSLVPN-Users. Click Select.
    The name of the authentication method shows in parentheses after SSLVPN-Users.

11. To close the Add Address dialog box, click OK.

12. In the To section, select Any-External. Click Remove.

13. In the To section, click Add.
    The Add Address dialog box opens.

14. From the Available Members list, select Any-Trusted. Click Add.

15. Click OK twice. Click Close.

16. Save the changes to the Firebox.

1. Select Authentication > Users and Groups.
2. Add users and groups, as described in Use Users and Groups in Policies.

After you add users or groups from the Mobile VPN with SSL configuration to the Users and Groups list, you can edit the automatically generated Allow SSLVPN-Users policy to apply to a specific group or user.

In this example, we modify the Allow SSLVPN-Users policy to apply to only the user group LDAP-Users1:

1. Select Authentication > Users and Groups.

2. Add the LDAP-Users1 group that you added to the Mobile VPN with SSL configuration.
   Make sure to set the Auth Server to LDAP.

3. Edit the Allow SSLVPN-Users policy.

4. In the From section, select the SSLVPN-Users group. Click Remove.

5. In the From section, click Add.
   The Add Member dialog box opens.

6. From the Member Type drop-down list, select SSLVPN Group.
   A list of groups opens.

7. Select the LDAP-Users1 group. Click OK.
   The LDAP-Users1 group shows in the From list.

8. Click OK.
   The Allow SSLVPN-Users policy now applies only to the LDAP-Users1 group.

1. Select Setup > Authentication > Users and Groups.
2. Add users and groups, as described in Use Users and Groups in Policies.

After you add users or groups from the Mobile VPN with SSL configuration to the Users and Groups list, you can edit the automatically generated Allow SSLVPN-Users policy to apply to a specific group or user.

In this example, we modify the Allow SSLVPN-Users policy to apply to only the user group LDAP-Users1:

1. Select Setup > Authentication > Users and Groups.

2. Add the LDAP-Users1 group that you added to the Mobile VPN with SSL configuration.
   Make sure you set the Auth Server to LDAP.

3. Edit the Allow SSLVPN-Users policy.

4. In the From section, select the SSLVPN-Users group. Click Remove.

5. In the From section, click Add.
   The Add Address dialog box opens.

6. Select Add Other.
   The Add Member dialog box opens.

7. From the Choose Type drop-down list, select Custom Address.

8. From the User/Group drop-down list, select the LDAP-Users1 group. Click OK.
   The LDAP-Users1 group shows in the Selected Members and Addresses list.

9. Click OK.
   The Allow SSLVPN-Users policy now applies only to the LDAP-Users1 group.