MicrosoftEdge / MicrosoftEdge/WebView2Feedback

[Problem/Bug]: When accessing a client authentication site with a C++ app using WebView2, the client certificate selection UI is not displayed and a 403 error is returned.

Open
#4,093 7 comments 0 reactions 1 assignee View on GitHub

@monica-ch is already working on this.

Since Oct 24, 2023.

bug
Dominant language
PowerShell
Stars
526
Forks
67
PR merge metrics
No merged PRs in 30d

Description

What happened?

In a C++ native application using WebView2, when accessing a URL that requires client authentication at startup, the client certificate selection UI is not displayed and a 403 error is returned.
WebView2 runtime version: 99.0.1150.39

[Error message]
403 - Forbidden: Access is denied.
You do not have permission to view this directory or page using the credentials that you supplied.

A similar phenomenon occurs in the publicly available sample app when ``accessing a URL that requires client authentication at startup''.
https://github.com/MicrosoftEdge/WebView2Browser

that's all.

Importance

Important. My app's user experience is significantly compromised.

Runtime Channel

Stable release (WebView2 Runtime)

Runtime Version

99.0.1150.39

SDK Version

1.0.1150.38

Framework

Win32

Operating System

Windows 10

OS Version

19045

Repro steps

Reproduction steps

  1. Download and open the sample project published below.
    https://github.com/MicrosoftEdge/WebView2Browser
  2. Rewrite the connection destination URL in the sample source to a server that requires client authentication.
  3. Build the sample.
  4. Start the sample.

Remarks
This phenomenon may or may not be reproduced depending on the environment.

Regression

Don't know

Last working version (if regression)

No response

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.