Hi, We currently don’t have access to the environment and are awaiting their response on whether it can be excluded.
We have not encoded it in our code. It is getting encoded from the package.
It would be better if we had a configuration option rather than overriding the connection pool.
Hi,
We are trying to connect to Azure Service Bus using managed identity.
We tried configuring the following as mentioned in https://abp.io/support/questions/9853/Connect-to-Azure-Redis-Cache-and-Azure-Service-Bus-using-Azure-managed-Identity
However, it appears that the ConnectionPool implementation is still attempting to use a connection string, which results in an error since no connection string is provided.
https://github.com/abpframework/abp/blob/270c458fe426e831b0568e533e125c9321cb78b7/framework/src/Volo.Abp.AzureServiceBus/Volo/Abp/AzureServiceBus/ConnectionPool.cs#L14
To work around this, we've overridden the ConnectionPool to fall back to DefaultAzureCredential when a connection string is not available. Would it be possible to introduce a configuration option to support this scenario?
Can you please provide an example of how to configure DefaultAzureCredential?
Hi, We want to use managed identity to connect to redis not password.
configurationOptions = await ConfigurationOptions.Parse($"{cacheHostName}:6380").ConfigureForAzureWithUserAssignedManagedIdentityAsync(managedIdentityId!);
connectionMultiplexer = await ConnectionMultiplexer.ConnectAsync(configurationOptions);