Forum Discussion

Dev_56330's avatar
Dev_56330
Icon for Cirrus rankCirrus
Feb 09, 2018

session.server.landinguri not found in variables

If APM sets session.server.landinguri by default, why am I not able to view this variable within APM logs? Currently Access Policy and SSO are configured to debug logging.

 

3 Replies

  • I wasn't sure if is really any case that has that variable. However, even a network access with edge client shows that, so I guess is all accesses.

    [root@LABBIGIP1:Standby:Changes Pending] local  sessiondump --sid b860e3d3 | grep session.server.landinguri
    b860e3d3.session.server.landinguri 1 /
    [root@LABBIGIP1:Standby:Changes Pending] local 
    

    Do you see the variable using the sessiondump as in the example above?

  • Apparently it is being added to cache. The scenario is idp selection is made off of session.server.landinguri . Upon the IdP returning the assertion an iRule must then make another decision based on the returned uri.

     

    Feb 9 08:12:54 bigip-ve1 debug apmd[12944]: 01490000:7: ./AccessPolicyProcessor/Session.h func: "getSessionVar()" line: 571 Msg: variable found, lets add it to the local cache "session.server.landinguri"="/myexampleuri"(length=39) Feb 9 08:13:38 bigip-ve1 debug apmd[12944]: 01490000:7: ./AccessPolicyProcessor/Session.h func: "getSessionVar()" line: 542 Msg: variable "session.server.landinguri" was not found in the local cache for session "c7b2fd89"

     

  • Now I am very confused. When watching active sessions I see 2. One that shows my initial login attempt and the 2nd with the SAML assertion from the IdP. However, later when going to all sessions I see 1 that does not contain session.server.landinguri . The sessions above and below have nothing to do with this login attempt.