Forum Discussion

JD1's avatar
JD1
Icon for Altostratus rankAltostratus
Dec 15, 2014

APM - Hometab appears, despite checkbox cleared in portal access.

Hi All,

I'm using 11.6.0 HF3 and have the following (and only) portal access configured.

apm resource portal-access XenApp_WebInterface {
    customization-group XenApp_WebInterface_resource_web_app_customization
    items {
        item {
            home-tab false
            order 1
            paths /*
            port https
            scheme https
            subnet /32
        }
    }
    scheme-patching true
}

There are no other ACLs/Portal Accesses configured.

Scenario: APM Evaluated and a Portal Webtop + This resource is provided to client. They see the Citrix Web Interface as intended and are able to fully use Citrix. If they are to click the Citrix WI 'Logout' button, or the Web interface session expires, SSO (as I would prefer currently) logs them back in but this time the Hometab is suddenly displayed.

It's an odd one, don't know if it's something cropped up in latest HF or seen before?

Thanks,

JD

BIG-IP Access Policy Manager (APM)
citrix
security
  • amolari's avatar
    amolari
    Icon for Cirrostratus rankCirrostratus
    Dec 16, 2014

    no such issue in v11.4.1 latest HFs (we have multiple Access Policies with/without this functionality). Probably a bug in v11.6. I would suggest to open a case. If you get a BugID, could you please let us know?

     

  • JD1's avatar
    JD1
    Icon for Altostratus rankAltostratus
    Feb 04, 2015
    The Answer!

    Quick update for the community. The answer has been discovered by F5 Support, this wasn't a bug but an issue with the resource items and the back end servers.

     

    Say the resource items were as follows: https://10.10.10.1 - Hometab Disabled, SSO added.

     

    This initially works, when a certain link was clicked on the backend server it used an absolute url which changed the requested resource from 10.10.10.1 to an internal DNS (or other IP).

     

    This then meant, as there is only one resource item, that there was no resource item to match the newly requested resource and disable hometab.

     

    So back end application, technically at fault, but I found it a little tricky to spot.