Question about key rotation & AuthenticationFailure

Hello team,

I have 'ssl=True,abortConnect=False' in the connection string. I have a few questions regarding the key rotation:

1. I was told that when the key getting rotated, a RedisConnectionException with FailureType equals to 'AuthenticationFailure' would get thrown. But in my case the failure type is alwasy 'SocketClosed' for a original connected mux.

2. I was told that the 'the ConfigurationOptions will be respected after the initial connection, updating User and Password at any point will be observed when reconnecting' , but that doesn't seem to be the case if the key was rotated before any connection was established successfully - I have the following code:

    private readonly IConnectionMultiplexer mux;
    private readonly ConfigurationOptions options;
    private readonly Lazy<LoadedLuaScript> lazyLoadedLua = new Lazy<LoadedLuaScript>(() => "#somescript#".Load(this.mux.GetServer(this.mux.GetDatabase().IdentifyEndpoint());

    mux = ConnectionMultiplexer.Connect(options);
    try
    {
        lazyLoadedLua.Value;
    }
    catch (RedisConnectionException redisConnectionException) when (redisConnectionException.FailureType == ConnectionFailureType.AuthenticationFailure)
    {
        this.options.Password = "#RotatedPassword#"
    }

When calling lazyLoadedLua.Value, the RedisConnectionException with FailureType equals to 'AuthenticationFailure' does get thrown, but changing the key on the fly doesn't seem to be respected by the mux as all the subsequent 'Lazy#Value' calls still failed with RedisConnectionException(AuthenticationFailure) - I did reset the Password to the right one.

3. regarding the setter of ConfigurationOptions#Password - the implementation seems to have bugs as the value set by one thread isn't guaranteed to be seen by other threads - don't we need some memory fence for it?

Start with ConfigurationOptions.Password, ConnectionMultiplexer.Connect, and the reconnect and authentication-failure paths exercised by the provided LazyLoadedLua flow. Reproduce key rotation before and after a successful connection, then inspect the setter's cross-thread behavior. Done means the expected failure type, updated password handling, and visibility across threads are documented or covered by a confirmed fix.