Forum Discussion
Access internal DMZ virtual server in SSL VPN
- Aug 17, 2017
Hi,
If the internal Virtual Server is HTTP or HTTPs, you may assign an SSO Access profile that allow you to get the username and password of the main Network Access policy.
Then, you can define an LDAP query to filter who can access the VS or not.
Or you can use an irule to control who can access the Virtual Server.
Alternatively, you can define several Lease pool based on different user populatiion and attach an irule to the DNZ Virtual Server allowing access to some lease IP addresses and reject or drop access for some others.
Hope it helps
Yann
Hi,
If the internal Virtual Server is HTTP or HTTPs, you may assign an SSO Access profile that allow you to get the username and password of the main Network Access policy.
Then, you can define an LDAP query to filter who can access the VS or not.
Or you can use an irule to control who can access the Virtual Server.
Alternatively, you can define several Lease pool based on different user populatiion and attach an irule to the DNZ Virtual Server allowing access to some lease IP addresses and reject or drop access for some others.
Hope it helps
Yann
I think the main problem is related to the vlans selected for your internal VS. You must add the Connectivity profile to the list of vlans allowed in your internal VS configuration to allow vpn users to access this VS
hope it helps
Yann
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com