In an SP initiated authentication to a third party federated IDP (ADFS
2.0), I get the following AuthnRequest Generated by NAM when I approach
a protected resource:
======
<samlp:AuthnRequest xmlns:samlp="urnasis:names:tc:SAML:2.0rotocol"
xmlns:saml="urnasis:names:tc:SAML:2.0:assertion"
AssertionConsumerServiceIndex="0"
Consent="urnasis:names:tc:SAML:2.0:consent:unavailable"
ForceAuthn="false" ID="idTMCiBc4zNk7Qlm43gP0SBPeqrxs"
IsPassive="false" IssueInstant="2013-10-11T22:20:02Z"
ProtocolBinding="urnasis:names:tc:SAML:2.0:bindings:HTTP-POST"
Version="2.0"><saml:Issuer>https://audience.domain.com/nidp/uri/example</saml:Issuer><samlp:NameIDPolicy
AllowCreate="true"
Format="urnasis:names:tc:SAML:2.0:nameid-format:transient"/></samlp:AuthnRequest>
======

The observed bug is that this AuthnRequest includes a ForceAuthn=False
and IsPassive=False, after they both have been enabled by checkmark in
the NAM SAML 2.0 AuthCard configuration for my ADFS Federation.

If NEVER checked, they don't appear in the authnRequest.
If checked, they appear FALSE (Shouldn't they appear "true" ?)
If unchecked, they CONTINUE TO APPEAR as False.

Should be easy to replicate. Yes, I restarted Tomcat, I restarted the
IDP, I restarted the Gateway. I did "Update All" after every change.

The Windows IDP is on 2008 R2, MAG Gateway,NAM v 3.2.2 77 Anyone else
seen anything like this?