forced authentication attribute not being used

Cantor, Scott cantor.2 at osu.edu
Fri Mar 11 17:07:54 UTC 2022


On 3/11/22, 11:40 AM, "users on behalf of Jeff McCullough" <users-bounces at shibboleth.net on behalf of jeffmc at berkeley.edu> wrote:

>    Thank you for your suggestions. I stopped using the general-authn.xml when converting to 4.1.x from 4.0.1.
> The documentation seems clear that the forced authentication property is available. By default it is set to
> false, and can be set to true in the authn.properties file. Either the property is being ignored or there is
> somewhere else it is again being set to false.

If it's honoring anything in authn.properties then it should work, yes. But you also can't just stop using general-authn.xml, you have to remove any flow descriptor beans from that list that would overlay the property-based ones.

-- Scott




More information about the users mailing list