Skip to content

Update troubleshooting documentation for WAF rules #1010

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
maartenba merged 1 commit into from
Feb 13, 2026
Merged

Update troubleshooting documentation for WAF rules #1010

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 4 additions & 5 deletions src/content/docs/identityserver/troubleshooting/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,8 +93,8 @@ Log.Logger = new LoggerConfiguration()

## WAF Rules

Data protected data can contain '--' (two dashes) and some firewalls disallow that because it looks like a sql
comment/injection. This is not an IdentityServer issue but something that should be fixed on the firewall.
Data protected data can contain `--` (two dashes), which some firewalls disallow that because it looks like a SQL
comment/injection. This is not an IdentityServer issue but something that should be fixed on the web application firewall.

## IdentityServerOptions.EmitStaticAudienceClaim and Token Validation

Expand Down Expand Up @@ -124,8 +124,7 @@ Microsoft.IdentityModel set of libraries. These libraries provide token and conf

The `Microsoft.IdentityModel.*` libraries used by Duende IdentityServer all have to be of exactly the same version
However, this is not enforced by NuGet so it is common to end up with an application that brings in different versions
of
`Microsoft.IdentityModel.*` through transitive dependencies.
of `Microsoft.IdentityModel.*` through transitive dependencies.

Version conflicts can cause unexpected issues reading configuration data and tokens, i.e. **IDX10500: Signature
validation
Expand Down Expand Up @@ -505,4 +504,4 @@ Even loading a certificate can fail, since the load operation could attempt to s

[1]: https://learn.microsoft.com/en-us/dotnet/api/system.security.cryptography.x509certificates.x509keystorageflags
[2]: /identityserver/ui/server-side-sessions
[3]: https://github.com/DuendeSoftware/products/blob/main/identity-server/src/IdentityServer/Configuration/DependencyInjection/PostConfigureApplicationCookieTicketStore.cs
[3]: https://github.com/DuendeSoftware/products/blob/main/identity-server/src/IdentityServer/Configuration/DependencyInjection/PostConfigureApplicationCookieTicketStore.cs