Forum Discussion

rache_262732's avatar
rache_262732
Icon for Nimbostratus rankNimbostratus
Sep 04, 2018

WSSE header missing when F5 redirects requests to different destination.

We have setup a F5 LTM redirect IRULE for our users who are trying to connect to any actional URLs to go to mulesoft based API as part of a project. Once this was put in place, the tests showed the redirect was successful but the WSSE security header was missing in the requests, need help understanding how the F5 will deal with WSSE header token, incase if F5 removes them from the headers when we setup such redirects asking clients to connect to other URLs. what could be causing the WSSE header missing from the request when they get redirected to different destinations as per F5 irules and how can this be fixed ?

 

application delivery
LTM
  • rache_262732's avatar
    rache_262732
    Icon for Nimbostratus rankNimbostratus
    Sep 04, 2018

    IRULE is setup to take anything comming in for

     

    dev.soamgmt.company.com/sst/runtime.asvc/com.actional... (actional)

     

    to be routed to

     

    dev.apigw.company.com/eis-acroutingiu.... (mulesoft proxy)

     

    and dev.apigw.company.com is seeing an error message saying "missing supporting tokens" under the message which says could not read wsse header token.