IdentityServer4.Contrib.RedisStore icon indicating copy to clipboard operation
IdentityServer4.Contrib.RedisStore copied to clipboard

A persistence layer using Redis DB for operational data and for caching capability for Identity Server 4

Results 8 IdentityServer4.Contrib.RedisStore issues
Sort by recently updated
recently updated
newest added

Hi, I am getting the following exception while trying to perform the `Authorization code` flow with IdentityServer4 configured to use the Redis as an operational store: ``` RedisCommandException: Multi-key operations...

We are planning to migrate to [Duende IdentityServer](https://github.com/DuendeSoftware/IdentityServer). Is IdentityServer4.Contrib.RedisStore going to be supported?

Updates the requirements on [StackExchange.Redis](https://github.com/StackExchange/StackExchange.Redis) to permit the latest version. Changelog Sourced from StackExchange.Redis's changelog. 2.2.50 performance optimization for PING accuracy (#1714 via eduardobr) improvement to reconnect logic (exponential backoff)...

dependencies

_Dependabot Preview will be shut down on August 3rd, 2021. In order to keep getting Dependabot updates, please merge this PR and migrate to GitHub-native Dependabot before then._ Dependabot has...

dependencies

Updates the requirements on [Microsoft.AspNetCore.TestHost](https://github.com/dotnet/aspnetcore) to permit the latest version. Release notes Sourced from Microsoft.AspNetCore.TestHost's releases. .NET 5.0.6 Release Commits dc5e11a Merged PR 14467: [internal/release/5.0] Update dependencies from dnceng/inter... f3eeec8...

dependencies

ASP.NET Core uses the IOptions pattern to inject configurable dependencies. Is it possible for this library to also support that?

Hi @AliBazzi We've seen some instances while running in Azure Redis when a Redis failover has caused the ConnectionMultiplexer to not retry the connection (instead requiring a restart of the...

Hi, When **ConnectionMultiplexer** is initialized and fails to connect to Redis will fail next times because the exception is cached and thrown again on subsequent calls to the Value property....