Outlook.com/Live.com OAuth2 login for PQ email retrieval

Abierto
  • ¿Algo no está bien?
#698 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
18/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Tranquilo
Stack tecnológico
python
Área
authentication

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

area: import feature on hold
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 EmailProvider interface 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
    EmailProvider interface 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.

Lenguaje dominante
Python
Estrellas
37
Forks
17
Merge medio
16 h 7 min
PR fusionados (30 d)
128

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de OpenSAK-Org/OpenSAK

Todos los issues de OpenSAK-Org/OpenSAK

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.