Honor the caller's CancellationToken during MONGODB-AWS credential resolution

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Unknown
    • 4.0.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Dotnet Drivers
    • None
    • None
    • None
    • None
    • None
    • None

      After CSHARP-5696, `AWSFallbackCredentialsSource` resolves credentials via the static `DefaultAWSCredentialsIdentityResolver.GetCredentials/GetCredentialsAsync`, which ignore the caller's CancellationToken (the SDK applies its own 35s timeout). We could instead use the instance methods ResolveIdentity(IClientConfig, CancellationToken) / ResolveIdentityAsync(...), holding a single long-lived resolver instance.

            Assignee:
            Unassigned
            Reporter:
            Ferdinando Papale
            None
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: