Outlook.com/Live.com OAuth2 login for PQ email retrieval
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 18/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 冷清
- 技术栈
- python
调研方向
This depends on #443's EmailProvider interface and fetch/parse/DB-match pipeline, so check first whether #443 has merged and read the interface there, along with the Gmail OAuth issue it mirrors. The payload names no existing source files, so locate the current login and credential-storage code before writing anything. Done means an OutlookOAuthProvider that implements EmailProvider, completes a loopback OAuth2 login, and fetches mail over IMAP with XOAUTH2, with tokens stored and refreshed via keyring.
由索引模型根据 Issue 内容生成。
描述
Problem Statement
Unlike Gmail, Outlook.com/Live.com has fully deprecated Basic
Authentication for consumer IMAP — this is disabled server-side by
Microsoft, with no app-password fallback. #443's generic IMAP +
app-password approach cannot support Outlook/Live accounts at all.
OAuth2 is the only way to support this provider.
Proposed Solution
Add Outlook.com/Live.com as an OAuth2 login option.
- Use Microsoft's official
msal(Microsoft Authentication Library) SDK - Local loopback browser flow, same pattern as the Gmail OAuth issue —
reuse that implementation's structure where possible - IMAP with XOAUTH2 authentication mechanism (Microsoft has not
deprecated IMAP itself, only Basic Auth for accessing it) — or
consider Microsoft Graph API mail access as an alternative if XOAUTH2
IMAP proves troublesome in testing - Token storage/refresh via
keyring, same credential store as #443 - Implements the shared
EmailProviderinterface from #443
(OutlookOAuthProvider), so it plugs into the same fetch/parse/
DB-match pipeline without changes there
Notes / constraints
- Azure app registration required (separate from Google's setup) —
redirect URI configuration for a desktop/loopback flow - Microsoft's Basic Auth deprecation has been rolled out in phases
before (2024 for IMAP, SMTP AUTH phased through March–April 2026) —
expect this to keep shifting; isolating this behind the
EmailProviderinterface from #443 limits the blast radius when it
does - Expect roughly one maintenance session per year for Microsoft-side
auth/API changes, same as the Gmail OAuth issue - This issue is not optional if Outlook/Live support is wanted at
all — unlike the Gmail OAuth issue, there's no working fallback via
#443's generic IMAP path
Depends on
- #443 (EmailProvider interface, fetch/parse/DB-match pipeline)
Expected Benefits
Enables PQ-from-email support for Outlook.com/Live.com users, which is
otherwise fully blocked by Microsoft's Basic Auth deprecation.
- 主要语言
- Python
- 星标
- 37
- 派生
- 17
- 平均合并
- 21 小时 5 分钟
- 30 天内合并 PR
- 131
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
OpenSAK-Org/OpenSAK 的其他 Issue
-
area: documentation documentation good first issue OS: windows
难度 2/5 半天 新手友好度 78/100
OpenSAK-Org/OpenSAK#1289 ·
维护者通常 1 天内回复
-
area: geo-data improvement
难度 2/5 1-3 小时 新手友好度 65/100
OpenSAK-Org/OpenSAK#1285 ·
维护者通常 1 天内回复
-
area: geo-data good first issue improvement
难度 2/5 1-3 小时 新手友好度 80/100
OpenSAK-Org/OpenSAK#789 · 1 条评论 ·
维护者通常 1 天内回复
-
area: UI improvement
难度 2/5 1-3 小时 新手友好度 62/100
OpenSAK-Org/OpenSAK#729 ·
维护者通常 1 天内回复
-
area: import improvement
难度 2/5 1-3 小时 新手友好度 78/100
OpenSAK-Org/OpenSAK#648 ·
维护者通常 1 天内回复
查看 OpenSAK-Org/OpenSAK 的全部 Issue
相似的 Issue
-
enhancement good first issue help wanted
难度 2/5 1-3 小时 新手友好度 88/100
-
Community
难度 2/5 1-3 小时 新手友好度 82/100
kedro-org/kedro-plugins#1575 ·
维护者通常 1 天内回复
-
hive size:simple
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 77/100
Significant-Gravitas/AutoGPT#16733 ·
维护者通常 1 天内回复
-
changelog investigate
难度 1/5 1 小时以内 新手友好度 74/100
ramnes/notion-sdk-py#444 ·