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 15, 2015

OK, I get it working that if configured start URI and requested URI are matching the correct POST-request will be send towards the server. But I still get a 403 Forbidden response. We are currently checking this in the access logs of the Exchange servers.

 

But what I still don't understand, how can I guarantee that the client is always entering the correct start URI (maybe they have a favorit to just /owa/)? I would expect, that Exchange is then doing a redirect to the correct login URI (same as configured for the start URI) and APM will catch this then. But that's not the case.

 

So is there still something wrong on the F5 or is this an issue on Exchange side? Or can this be adjusted with an iRule doing the redirect to the correct start URI in case the session Cookie is not available?

 

Thank you!

 

Ciao Stefan :)