For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Stefan_Klotz's avatar
Stefan_Klotz
Icon for Cumulonimbus rankCumulonimbus
Jun 12, 2014

BIG-IP WebGUI via APM Portal Access

Hi,   We have built up a LAB with a APM in front of it. As of now we just have Network Access configured to have our internal LAB networks available to the outside and several Weblinks to our BIG-...
BIG-IP Access Policy Manager (APM)
deployment
security
Matt_Dierick's avatar
Matt_Dierick
Icon for Employee rankEmployee
Jun 12, 2014

Stefan,

 

First of all, if the bigip is able to resolve the DNS, it's a good news. A portal access is a reverse proxy. Portal access rewrite content from the back end to the front end. I mean, if the Virtual Server has https://external.mysite.com and your internal ressource (the application URI) has http://internal.mydomain.local, then the BIGIP will rewrite like that https://external.mysite.com/f5-w-5435636546345xxxxxxx

 

So, the link type is your internal URL. Can you confirm bigip3.f5-lab.local is a Web Service (on internal BIGIP or a Web Server) ???

 

The ressources items, at the bottom, are not mandatory. You can use it if you want to specify specific SSO or compression for a specific/dedicated path. Keep them empty at the moment.

 

To finish, in your VPE, assign your portal access and a Full Webtop. Last point : did you assign a Server SSL profile on your VS ? It seems your portal access is on 443.

 

Let me know the result. Do you see the rewrite (f5-w-3242345435) ???