Create More than Remote access in VPN community

[yeruel]

Hi Checkmates,

I am planning to create users for a traffic SSL VPN client to access internal resources from the internet. A remote access VPN has been created. When users log in to the SSL VPN client using their username and password, and authentication is successful, the client receives a remote IP pool address and attempts to access the resources. My goal is to create different remote access VPN communities for different user groups, and mapped each remote access vpn to the users group, and with each group having its own access control policy.

Is it possible to create different remote access VPNs in VPN communities for this purpose?

For example:

• Rule 1: Source - Usergroup1, Destination - Network1, VPN - RemoteAccessVPN1

• Rule 2: Source - Usergroup2, Destination - Network2, VPN - RemoteAccessVPN2

  

[Tal_Paz-Fridman · Accepted solution]

No.

Multiple Remote Access communities Issue:

https://support.checkpoint.com/results/sk/sk160892 

[the_rock · Accepted solution]

Cant do, sorry, definitely not possible, as @Tal_Paz-Fridman indicated. Below is what happens if you try.

Andy

[Chris_Atkinson · Accepted solution]

You would likely need to explore combinations of the following to achieve similar logic

- Identity Awareness + Remote Access 

- Multi-domain Management + VSX 

Otherwise please consult with your local CP SE about a possible RFE.