Technical Forum
Ask questions. Discover Answers.
Showing results for 
Search instead for 
Did you mean: 

Help with APM irule to append URI and URL to call to kill individual sessions


Hi I'm trying to figure out the best way to get this to work.  I need to take the incoming http request and append a URI.  Part of it is static URL/static/static/static/apm session variable value.  The variable value will be different for each of the services being called and that is how openshift will redirect the traffic.  After this policy the traffic has to be forwarded to another VIP on the F5 that is created by OpenShift.  I also wanted to see if i could get help with the URL I need to call to kill any sessions.  We have the URL from our external IDP provider but also need to kill the session on the APM.


Community Manager
Community Manager

a couple questions for clarification:

  1. do you need to append the URI before/during/after APM processes the request?
  2. Can you diagram in text or pic the workflow through BIG-IP, is this one or more devices?



Request comes in on URL and hits one VIP a the common partition which has the access policy tied to it.  The access policy looks at the SAML XML to authenticate then if it is allowed it is sent to another VIP on the same pair of LTMs but a different partition (doesn't have its own DNS record).  The application configured behind the second VIP runs in Openshift and requires seeing that /static/static/static/ in order to route the traffic correctly.  I've been able to add a redirect at the end of the access policy instead of an allow but not using the same DNS record that points to the VIP.  I'm assuming this just sends it in a loop when it is the same?  Hopefully that makes sense

What is the URL the final application is expecting?

is it = apm vip

forward session variables and continue request to on vip 2 or is it expecting another url all together?

The openshift container is expecting one of 3.  Either the oringal URL, the IP or the openshift proxy URL.  We just obviously don't want to expose the IP or the proxy.  So sending it through with the original URL with the added URI would be fine.  It just seemed like redirecting to the original would send it back through the entire process hitting the VIP the DNS resolves to with the access policy attached.

To avoid loop, may want to use ‘MRHSession and LastMRH_Session’ cookies in your irule while sending it through with the original URL with added URI. And use ‘STREAM::disable’ then for return traffic ‘STREAM::enable’

So when it comes with the session ID inside the query parameters, disable the Access.


If you want to redirect first request after authentication, you can use a variable assign with:

session.server.landinguri = expression expr{ "/static/static/static/[mcget {}]" }

It will force to redirect the user to this url after succeded authentication

If you want to redirect for any request on / URL, you can use following irule

  if { [HTTP::path] == "/" } {
    ACCESS::respond 302 noserver Location "/static/static/static[ACCESS::session data get ""]"

Thanks Stan.  When I try adding the variable assign I get a page can't be found and I don't see the URI appended in my browser.  When I use the Irule i see the redirect in the browser but I still get a page can't be found.  I'm thinking because of the DNS loop and the URL being tied to VIP #1.

You will have to apply the select virtual after the apm policy processing. Since the VIP #2 does not have a dns entry, you will need to force it through via an irule to select the virtual after processing. Personally I'd recommend adding a dns entry, and make it simple, but you can do it in an irule to forcefully select the virtual.