We have ADFS Proxy servers (Web Application Proxy servers) in our perimeter network and have MFA configured.
We also have configured a very strict ADFS Extranet Account Lockout policy (3 bad passwords, 1 hour lockout) but we see this as unsustainable for bruce force attack.
We need to ensure at least one of the following solutions are available for ADFS 3.0 infrastructure. Both of these are available through ADFS 2.0 infrastructure since the login pages are customisable.
For Extranet authentication, perform MFA authentication first. Then, if successful, perform the AD authentication. Ideally, present one login page with AD and MFA login details instead of presenting two login pages for the users.
Allow the customising of the ADFS login page to add CAPTCHA authentication. Microsoft adds CAPTCHA to its other sites so it shouldn’t be too difficult to integrate this to the ADFS 3.0 web forms, or at least allow us to use the reCaptcha API within the ADFS 3.0 infrastructure.
Either way, the work flow should be that, if the claim is being passed through a Web Application Proxy (ms-proxy), then present MFA page or CAPTCHA page before AD authentication page... or present them all in the first page but authenticate AD account only after MFA and/or CAPTCHA is authenticated successfully.
Can you please advise if these features are already available in ADFS 3.0? Or do you know if they will become available in upcoming updates?
We are currently experiencing frequent account lockouts from our ADFS servers. We have tracked the offending authentication attemps to other countries. We have tried working with MS portal support, but did not get any where.
We also have adjusted out ADFS Extranet lockout settings to no availe.
We too are wondering about:
MFA first for external authentication (having it second still allows multiple bad attempts)
Possible use of CAPTCHA (or something similar)
Setting some kind of geo-location limits to authentication