Using FallbackCredentialsFactory in a thead safe way

[DmitryLukyanov]

Continuation of this discussion: #2484

I'm using FallbackCredentialsFactory.GetCredentials to retrieve aws credentials. Additionally I want to clear a cached credentials generator (here), in case if the previously cached generator has failed, to run all retrieving creds logic from the beginning. All works fine other than FallbackCredentialsFactory is not thread safe. To solve it, I can add a lock on my side like:

lock (_lock)
{
     FallbackCredentialsFactory.Reset();
}

and

var creds = ..
lock (_lock)
{
        creds = FallbackCredentialsFactory.GetCredentials();
}
return creds.GetCredentials()

but I would like to avoid having full generators lookup (with fetching creds in some cases) under lock. Does anyone have suggestions?

[ashishdhingra]

but I would like to avoid having full generators lookup (with fetching creds in some cases) under lock.

@DmitryLukyanov FallbackCredentialsFactory.GetCredentials() would always go through all generators and return the first fetched credentials. I'm unsure what's your use case to avoid having full generator lookup under lock. Could you please elaborate?

[github-actions[bot]]

Hello! Reopening this discussion to make it searchable.