[Bug] Support library-agnostic HTTP clients for Service Fabric managed identity

Aberta
#965 0 comentários 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
48/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
python

Direção de pesquisa

Start by reading the Service Fabric managed identity credential and its certificate-pinning transport code, along with the Azure Core integration affected during MSAL 1.38 uptake. Define a library-neutral capability that validates the certificate before sending the Secret header, keeps Requests as the default, and rejects transports that cannot enforce validation. Done when contract tests cover Requests, a non-Requests backend, and Azure Identity’s public Service Fabric credential APIs.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

AzureSDK bug P1
Context

The certificate-pinning change in #952 tied Service Fabric authentication to requests.Session, affecting Azure Identity’s Azure Core integration during MSAL 1.38 uptake for [Azure/azure-sdk-for-python#48708](https://github.com/Azure/azure-sdk-for-python/issues/48708).

PR #964 fixes adapter-subclass rejection, but the broader Requests-specific API restriction remains.

Request

Provide a library-neutral transport capability for certificate pinning so Azure Identity can retain its pipeline without importing Requests, and other HTTP libraries can integrate.

Keep Requests as the default backend, preserve certificate validation before sending the Secret header, and explicitly reject transports that cannot enforce it. Verify the contract with Requests and a non-Requests backend, including Azure Identity’s public Service Fabric credential APIs.

Linguagem predominante
Python
Estrelas
971
Forks
223
Merge médio
1d 32min
PRs com merge (30d)
1

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de AzureAD/microsoft-authentication-library-for-python

Todas as issues de AzureAD/microsoft-authentication-library-for-python

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.