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.

BIG-IP iRulesLX FakeADFS - WS-Federation/SAML11

Details This was created as a solution to REPLACE the need for AD FS to tie APM into SharePoint.  The goal was originally to demonstrate the flexibility of iRulesLX and also to find a way to add WS-...
Published Jan 05, 2017
Version 1.0
application delivery
BIG-IP Access Policy Manager (APM)
federal
iRulesLX
saml
security
ws-fed
Shawn_Conway's avatar
Shawn_Conway
Icon for Cirrus rankCirrus
Aug 05, 2022

MichaelatF5  We resolved the issue after patch 17.0.0.1 by commenting out

# node 127.0.0.1

 

and the rest of the code continued to work.  the issue was related to the irule hardening in patch

006921-8 : iRules Hardening

Component: Local Traffic Manager

Symptoms:
Under certain conditions iRules do not follow current best practices.

Conditions:
Use of iRules with the pool or node commands.

Impact:
iRules do not follow current best practices.

Workaround:
N/A.

Fix:
iRules now follows current best practices.

Behavior Change:
Database variable 'tmm.tcl.rule.node.allow_loopback_addresses' was created to toggle whether or not to allow loopback addresses for iRule node command; "true" will restore previous behavior and enable loopback connections.

The default value is "false".

 

Thanks,

Shawn