We have a business-system that queries multiple apis from different servers in our Windows domain through javascript calls. These calls are authenticated with the current windows identity. It usually works fine, but sometimes something breaks (we haven't figured out yet when/why it happens) and the service reports http 401 errors. If that happens even clearing the cache won't solve the problem, but a co-worker discovered that deleting the edge profile works (edge://settings/profiles).
So the question is, what is saved in the edge-profile, that could break windows auth? And even better, how to fix it?
Example for service-call:
function callService() {
return new Promise(function (resolve, reject) {
$.ajax({
async: true,
url: apiConfig.appName,
type: "GET",
dataType: "json",
timeout: 10000,
xhrFields: {
withCredentials: true
},
success: function (result) {
resolve(result);
},
error: function (err) {
$("#errorPopUp").html(errorText);
}
}); });
Any insight would be appreciated :)
I think that might be related with Sign in automatically using saved passwords and Single sign-on across work or school sites.
If a user saves passwords in Microsoft Edge, they can enable a feature that automatically logs them into websites where they have saved credentials.
Once you’ve signed in to your organizational account in Microsoft Edge, we’ll use those credentials to authenticate you to websites and services that support Web Single Sign-On.
You can navigate to edge://settings/passwords to check if there's any saved passwords and navigate to edge://settings/profiles/multiProfileSettings to check if you have enabled Allow single sign-on for work or school sites using this profile. These data can't be cleared by clearing the cache. You can check if they're related with your authentication issue.