-
Notifications
You must be signed in to change notification settings - Fork 232
Wrong current password sends multiple login attempts #677
Comments
Log information: Hosting environment: Production Content root path: C:\inetpub\wwwroot\PassCore Now listening on: http://reset.server.local:80/ Now listening on: https://reset.server.local:443/ Application started. Press Ctrl+C to shut down. info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
info: Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware[6]
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
info: Microsoft.AspNetCore.Routing.EndpointMiddleware[0]
info: Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker[3]
info: Microsoft.AspNetCore.Mvc.Infrastructure.SystemTextJsonResultExecutor[1]
info: Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker[2]
info: Microsoft.AspNetCore.Routing.EndpointMiddleware[1]
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
info: Microsoft.AspNetCore.Routing.EndpointMiddleware[0]
info: Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker[3]
warn: Unosquare.PassCore.PasswordProvider.PasswordChangeProvider[0]
info: Unosquare.PassCore.PasswordProvider.PasswordChangeProvider[0]
fail: Unosquare.PassCore.PasswordProvider.PasswordChangeProvider[888]
System.NullReferenceException: Object reference not set to an instance of an object. at Unosquare.PassCore.PasswordProvider.PasswordChangeProvider.b__7_0(Principal x) in C:\Unosquare\passcore\src\Unosquare.PassCore.PasswordProvider\PasswordChangeProvider.cs:line 167 at System.Linq.Enumerable.Any[TSource](IEnumerable at Unosquare.PassCore.PasswordProvider.PasswordChangeProvider.ValidateGroups(UserPrincipal userPrincipal) in C:\Unosquare\passcore\src\Unosquare.PassCore.PasswordProvider\PasswordChangeProvider.cs:line 167 dbug: Unosquare.PassCore.PasswordProvider.PasswordChangeProvider[0]
warn: Unosquare.PassCore.PasswordProvider.PasswordChangeProvider[0]
info: Microsoft.AspNetCore.Mvc.Infrastructure.ObjectResultExecutor[1]
info: Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker[2]
inf |
PassCore Server
OS: Windows
PassCore version: 4.2.3 (We had some issues with 4.2.4 version)
Provider: Active Directory
Settings file (without sensitive information):
"Logging": {
"IncludeScopes": false,
"LogLevel": {
"Default": "Debug",
"System": "Information",
"Microsoft": "Information"
}
},
"WebSettings": {
"EnableHttpsRedirect": true
},
"AppSettings": {
// The following options for AD Provider (remove if you don't use this Provider)
"UseAutomaticContext": true
"RestrictedADGroups": []
"AllowedADGroups": []
"IdTypeForUser": "UPN"
"UpdateLastPassword": true
// The following options are for LDAP Provider (remove if you don't use this Provider)
//"LdapSearchBase": "",
//"LdapSecureSocketLayer": false
//"LdapStartTls": true
//"LdapChangePasswordWithDelAdd": true,
//"LdapSearchFilter": "(sAMAccountName={Username})"
// General options (valid for both providers)
"LdapHostnames": [ "my.domain" ]
"LdapPort": 389
"LdapUsername": ""
"LdapPassword": ""
"DefaultDomain": "my.domain" // Set your default AD domain here, or non "@" logins will not work! Use empty value to allow user to set the domain. This option is ONLY available with UPN.
},
"ClientSettings": {
"ValidationRegex": {
"EmailRegex": "^[a-zA-Z0-9.!#$%&’+/=?^_`{|}~-]+@[a-zA-Z0-9-]+(?:\.[a-zA-Z0-9-]+)$",
"UsernameRegex": "^[a-zA-Z0-9._-]{3,20}$"
},
"UsePasswordGeneration": false
"MinimumDistance": 0
"PasswordEntropy": 16
"ShowPasswordMeter": true,
"MinimumScore": 0
"Recaptcha": {
"SiteKey": ""
"PrivateKey": ""
"LanguageCode": "en"
},
Log file (without sensitive information):
Describe the bug
When I intentionally enter wrong password in order to test PassCore since it's new installation, badPwdCount attribute value increments by 2, 3, or even 4 on every attempt. Problem is that it also automatically locks account.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
badPwdCount attribute value should increment by 1.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: