Hi, We currently don’t have access to the environment and are awaiting their response on whether it can be excluded.
Hi,
It is blocked from Azure Front Door in our client environment with the following error.
Hi,
This should be reproducible in a sample project created from abp studio, with separate auth server. We are using blazor server for front end. Just need to click on the login button in blazor and it should redirect to the auth server, with the double encoded redirect uri.
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 getting the following error after adding this.
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);
The Microsoft.Azure.StackExchangeRedis package supports authentication via Managed Identity. Is there a way to override ABP.IO’s default cache connection configuration to leverage this package and connect securely to Azure Redis?
So how can we test this in our microservice project? Do we need to upgrade the packages to v9.3?
