MicrosoftEdge / MicrosoftEdge/WebView2Feedback
Authentification error
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 526
- Forks
- 67
- PR merge metrics
- No merged PRs in 30d
Description
What happened?
Hello,
I want to access a webserver inside a company network. The frontend is also inside the company network.
The webserver provides two websites, one for normal use and a test website.
The access to both websites is possible with MS Edge without any uppopping authentification windows.
In fact, for both website the windows authentification ist used.
When I access the normal website by webview2, everything works as expected.
But when I try to access the test website, there is allways an identification necessary.
Any ideas what causes this strange behaviour?
Manfred
Importance
Moderate. My app's user experience is affected, but still usable.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
latest
SDK Version
No response
Framework
Winforms
Operating System
Windows 11
OS Version
latest
Repro steps
Repros in Edge Browser
No, issue does not reproduce in the corresponding Edge version
Regression
No, this never worked
Last working version (if regression)
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository file, test, SDK version, or reproducible steps are provided. Start by reviewing the WinForms WebView2 authentication behavior against the two internal websites and the corresponding Edge behavior, then gather enough details to reproduce the difference. Done means identifying the cause and documenting or fixing the differing authentication behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- authentication, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100