Forum Discussion
Windows Integrated Authentication - Not Working - Canary & Dev
Great, Dev just updated and now it's broken there as well!
Hi,
Have you tried checking out these flags?
sometimes some features of Edge insider get turned off, shipping to flags, disabled by default and so on.
Hi HotCakeX,
Thank you for the tip.
How would you go about deploying a change in experimental features to a group of people?
Just wondering.
BR,
Radko- I wouldn't use the current system of controlled feature rollouts. I mean, having 4 channels of Edge browser is already a form of controlled feature rollouts, because folks in Canary channel have access to features that folks in Dev channel don't. same thing applies to Beta and Stable channels as well.
so it doesn't make any sense to apply yet another control layer to people in the Same channel. which is what currently is happening.
even people using Canary channel don't have access to the same set of features. it causes confusion.
- Hi HotCakeX, where can I find these "Experiments" settings ? As I cannot find them. I have release 79.0.309.18 and I have same issue
- Eric_Lawrence
Microsoft
The first two "Web Auth" flags shown here are not related.
However, **Disabling** the "Sign in to intranet websites with your profile" might have an impact. edge://flags/#edge-identity-based-http-auth
It worked - makes zero sense.
Eric_Lawrence wrote:
The first three flags shown here are not related. **Disabling** the "Sign in to intranet websites with your profile" might have an impact.Yes, that did fix the issue. Right now, we have only a couple of users testing (Dev and Beta channel), so we can flip that flag once this starts to happen for them until the actual fix is deployed. Thanks!
HotCakeX Thanks for the input, but I don't believe any of those flags are related to this issue (except maybe the profile one), still I tried enabling manually all 3, no effect. Also, I'm 99.9% sure that this feature is not classified as "experimental". 🙂
Keith Davis You should not *enable* it, but *disable* the first. Peculiar, but working.
- Edge insider at its current state is constantly changing, flags specially, are being added/removed in every few builds.
I think if there is a problem of that much importance, it must be fixed by default rather than by a flag.
- The whole browser is experimental and beta for now and judging by the version I think you are using Canary
- We are testing both Dev and Canary. This issue began in Canary about a week ago and the issue was pushed to Dev today.
