isPassive option would break non-SAML2 Initiator handlers
Basics
Technical
Logistics
Basics
Technical
Logistics
Description
The non-2.0 handlers probably ignore isPassive, which means using it with those handlers in place would break. Since it's a known feature, the handlers should check for it and refuse to run if its set. But that needs some additional thought, since the end result should be to just fail silently rather than hard.
Includes behavior change to treat initiator errors silently when run as a handler so that isPassive use returns control to the originating target if it fails instead of putting an error in front of the user.
Handlers are now obligated to advertise in code if they support isPassive, and without more substantial API changes, getting the right logic to run currently required a small change to each one.
The non-2.0 handlers probably ignore isPassive, which means using it with those handlers in place would break. Since it's a known feature, the handlers should check for it and refuse to run if its set. But that needs some additional thought, since the end result should be to just fail silently rather than hard.