Hi Richard,
i also first tested to move SAML Logon up, but i end up with standard configuration at the moment.
SAML is active because from a superordinate node SAML 2.0 is inherited.
Image may be NSFW.
Clik here to view.
btw. did you add the "IntegratedWindowsAuthentication" alias i mentioned above?
3. Setup local SAML provider (SAML2)
Add Authentication context alias "IntegratedWindowsAuthentication" with name: "urn:federation:authentication:windows"
Because i removed it at the moment and its working fine.. (Screenshots of running config will come later)
Regards
Manuel
