We currently have a VIP configured for external ADFS that is doing SSL passthrough. We are trying to utilize the X Forwarded for header with SSL bridging however during our change neither the SSL bridging or the x forwarded for option was sucessfull. When applying either or both config that traffic would fail and the web page would show page unreachable. Does anyone have any expereience with this type of change
@Thomson_Thomas This can be acheived by enabling F5 ADFS proxy function, you might want to check this doc. to enable trust between F5 and ADFS behind it to allow F5 to act as ADFS proxy.
in case you want to enable only HTTP(S) loadbalancing and SSL bridging, you should check your serverside SSL profile for ServerName and SNI settings. AD FS servers expects the ServerName to be correct.
Thanks dont have APM licensed or installed in our environment. Was thinking there was a way to get this working with just LTM but im assuming there isnt.
For this you do not need APM but as @Daniel_Wolf mentioned it is great to do it with APM guided config as then you can use the F5 as a portal not only for ADFS but your internal web apps, Exchange , Azure AD sync between F5 and the Azure AD using SAML, Oauth etc.
