Home
%3CLINGO-SUB%20id%3D%22lingo-sub-311346%22%20slang%3D%22en-US%22%3E401%20and%20infinite%20loop%20of%20user%20credentials%20prompt%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-311346%22%20slang%3D%22en-US%22%3E%3CP%3EIf%20you%20are%20using%20NTLM%20provider%20only%20for%20Windows%20Integrated%20Authentication%20for%20your%20web%20app%2C%20and%20the%20web%20app%20web.config%20has%20401%20custom%20handler%2C%20you%20may%20run%20into%26nbsp%3B401%20and%20infinite%20loop%20of%20user%20credentials%20prompt.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ETo%20address%20the%20issue%2C%20check%20the%20web.config%20and%20see%20if%20you%20have%20the%20following%20and%20comment%20it%20out.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3C!--error%20statusCode%3D%26quot%3B401%26quot%3B%20path%3D%26quot%3B%2Ferror.html%26quot%3B%20responseMode%3D%26quot%3BExecuteURL%26quot%3B%20%2F--%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20problem%20is%20when%20401%20is%20detected%2C%20it%20is%20routed%20to%20the%20custom%20handling%20page%20but%20the%20custom%20error%20handling%20page%20will%20get%20401%20too%20so%20you%20may%20run%20into%26nbsp%3B%3CSPAN%3Einfinite%20loop%20of%20user%20credentials%20prompt%20and%20401.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-311346%22%20slang%3D%22en-US%22%3E%3CP%3EIf%20you%20are%20using%20NTLM%20provider%20only%20for%20Windows%20Integrated%20Authentication%20for%20your%20web%20app%2C%20and%20the%20web%20app%20web.config%20has%20401%20custom%20handler%2C%20you%20may%20run%20into%26nbsp%3B401%20and%20infinite%20loop%20of%20user%20credentials%20prompt.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ETo%20address%20the%20issue%2C%20check%20the%20web.config%20and%20see%20if%20you%20have%20the%20following%20and%20comment%20it%20out.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3C!--error%20statusCode%3D%26quot%3B401%26quot%3B%20path%3D%26quot%3B%2Ferror.html%26quot%3B%20responseMode%3D%26quot%3BExecuteURL%26quot%3B%20%2F--%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20problem%20is%20when%20401%20is%20detected%2C%20it%20is%20routed%20to%20the%20custom%20handling%20page%20but%20the%20custom%20error%20handling%20page%20will%20get%20401%20too%20so%20you%20may%20run%20into%26nbsp%3B%3CSPAN%3Einfinite%20loop%20of%20user%20credentials%20prompt%20and%20401.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-311346%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Ehuanchix%40microsoft.com%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Microsoft

If you are using NTLM provider only for Windows Integrated Authentication for your web app, and the web app web.config has 401 custom handler, you may run into 401 and infinite loop of user credentials prompt.

 

To address the issue, check the web.config and see if you have the following and comment it out.

 

<!--error statusCode="401" path="/error.html" responseMode="ExecuteURL" /-->

 

The problem is when 401 is detected, it is routed to the custom handling page but the custom error handling page will get 401 too so you may run into infinite loop of user credentials prompt and 401.