You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which version of Duende IdentityServer are you using?
IdentityServer 7.0.3
BFF 2.2.0
Which version of .NET are you using?
net8.0
Describe the bug
On a high volume public facing deployment our logs are spammed with IdentityServer Errors which are generated by security scans or wrong user input. The validators used in identityserver are logging all invalid requests as an Error, for example:
Expected behavior
We would like to request a change that the logging level for these kind of log statements can be configured from Error to Warning so error reporting would not give so much errors due to improper usage / url scanning.
The text was updated successfully, but these errors were encountered:
Which version of Duende IdentityServer are you using?
IdentityServer 7.0.3
BFF 2.2.0
Which version of .NET are you using?
net8.0
Describe the bug
On a high volume public facing deployment our logs are spammed with IdentityServer Errors which are generated by security scans or wrong user input. The validators used in identityserver are logging all invalid requests as an Error, for example:
AuthorizeRequestValidator
IdentityServer/src/IdentityServer/Validation/Default/AuthorizeRequestValidator.cs
Line 160 in 3527069
IdentityServer/src/IdentityServer/Validation/Default/AuthorizeRequestValidator.cs
Line 201 in 3527069
IdentityServer/src/IdentityServer/Validation/Default/AuthorizeRequestValidator.cs
Line 226 in 3527069
ProtectedDataMessageStore
IdentityServer/src/IdentityServer/Stores/Default/ProtectedDataMessageStore.cs
Line 62 in 3527069
Expected behavior
We would like to request a change that the logging level for these kind of log statements can be configured from Error to Warning so error reporting would not give so much errors due to improper usage / url scanning.
The text was updated successfully, but these errors were encountered: