title: Windows Credential Provider Implementation
body: <p>This is a question related to Windows Credential Provider Implementation</p>
  
  <p>I want to follow up to this question. We have a custom MFA solution that prompts for sms/pin after windows has finished authentication before letting the user in. Unfortunately on windows 2016 and windows 10,winLogon.exe does not wait for the custom mfa solution prompt to close if there is no activity, it just happens to log the user in, defeating the purpose of having a mfa prompt.</p>
  
  <p>I have deployed a custom credential provider using the Windows Credential Provider framework. I know windows calls ReportResult function (<a href="https://msdn.microsoft.com/en-us/library/windows/desktop/bb776030(v=vs.85).aspx" rel="nofollow noreferrer">https://msdn.microsoft.com/en-us/library/windows/desktop/bb776030(v=vs.85).aspx</a>) after finishing the authentication to report the status back, but at this juncture i expected WinLogon.exe to wait (at this point my custom mfa prompts for challenge) for this function to return, instead it seems to just wait for ~2 mins and logs the user in.</p>
  
  <p>Can anyone help me control this behaviour.</p>