dotnet/maui

WebAuthenticator custom headers for http client

Open

#23,633 创建于 2024年7月16日

在 GitHub 查看
 (4 评论) (1 反应) (0 负责人)C# (23,245 star) (1,951 fork)batch import
area-essentialsgood first issueplatform/androids/triagedt/enhancement ☀️

描述

Description

Is there an option or workaround for passing custom headers using WebAuthenticator?

Steps to Reproduce

  1. Create MAUI project
  2. Invoke WebAuthenticator.AuthenticateAsync()

Link to public reproduction project repository

No response

Version with bug

8.0.40 SR5

Is this a regression from previous behavior?

No, this is something new

Last version that worked well

Unknown/Other

Affected platforms

Android, I was not able test on other platforms (but the basic problem is the same for all other platforms)

Affected platform versions

No response

Did you find any workaround?

No response

Relevant log output

No response

贡献者指南

技术栈
csharpandroid
领域
mobileauthentication
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
fresh
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Basic understanding of .NET MAUIFamiliarity with WebAuthenticator API
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
60
研究方向
Start by examining the WebAuthenticator implementation in the MAUI source code, likely in src/Core/src/Platform/Android/Authentication/WebAuthenticator.cs. Investigate how the HTTP client is constructed and whether custom headers can be added via AuthenticationProperties or a new parameter. Look at linked issues or comments for prior discussion (e.g., comment #23633-1234). Consider adding a new overload to AuthenticateAsync that accepts headers, or extending the existing options. Test on Android first, then other platforms.