You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I submit a WWW-Authenticate header back with the 401 response using Basic authentication, I still see the browser window pop-up. Any idea as to how I could block the browser's pop-up? I need to be able to authenticate users in the browser for other scenarios.
The text was updated successfully, but these errors were encountered:
I believe the only way to avoid this is to change the response header from the server-side. So you could change it from WWW-Authenticate Basic ... to WWW-Authenticate xBasic ... or something.
@Rykus0, that is what I found, as well. It is unfortunate, since I have other pages on the site I would like to protect in the same way that are not part of the Angular app. So I'm broken in one form or another. :(
If I submit a
WWW-Authenticate
header back with the 401 response using Basic authentication, I still see the browser window pop-up. Any idea as to how I could block the browser's pop-up? I need to be able to authenticate users in the browser for other scenarios.The text was updated successfully, but these errors were encountered: