Skip to content

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

Description

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](Azure/azure-sdk-for-python#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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions