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
Dear Yann,
The virtual server im trying to access is configured with HTTP, i really dont want to create any access restrictions, im testing without an ACL in APM. I need to understand why i can access the nodes in DMZ (Red, Green, Blue, Hackit) but i cant access the internal Virtual Server 10.128.20.10 of this nodes.
Its this a problem related to routes? Or maybe its works like that because of F5 design, since im connecting to and Virtual Server (VPN SSL) and im trying to coonnect to another Virtual Server (Internal DMZ).
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