A
Aditya_Contata
Guest
Our .Net WebAPI application is hosted on IIS 7.5 with anonymous and window authentication enabled. Client end application is hosted on same domain(lntranet) which is built up in Angular 6.
Front end application is hitting .Net WebAPI on same domain to read user details from AD on local server. This method is using window authentication to authorize the user access to AD.
Chrome is recursively prompting the window credentials for WebAPI server and is not accepting the correct credentials supplied manually.
This is working with IE/Edge when loopbackcheck is disabled but Chrome and Firefox are not accepting the credentials and recursively prompting for local server authentication.
We have already added the site url to trusted site and passed the current login username and password automatically. Providers on IIS for window authentication are NTLM and Negotiate. Their sequence is changed in order to check the effect but no luck so far.
Continue reading...
Front end application is hitting .Net WebAPI on same domain to read user details from AD on local server. This method is using window authentication to authorize the user access to AD.
Chrome is recursively prompting the window credentials for WebAPI server and is not accepting the correct credentials supplied manually.
This is working with IE/Edge when loopbackcheck is disabled but Chrome and Firefox are not accepting the credentials and recursively prompting for local server authentication.
We have already added the site url to trusted site and passed the current login username and password automatically. Providers on IIS for window authentication are NTLM and Negotiate. Their sequence is changed in order to check the effect but no luck so far.
Continue reading...