Can't use numbers in password

[GoogleCodeExporter]

Regardless of the settings in the number of numeric characters, ect, PWM will 
not allow numbersin password, "New password has too many numbers". This happens 
regardless of whether the password policy is "Merged", "Local" or "LDAP" (even 
though my LDAP allows numbers.) Tried reducing Min Password Strength to 1.

What steps will reproduce the problem?
1. Set password complexity settings to any value
2. Type password twice
3.

What is the expected output? What do you see instead?

Password is not accepted, "New password has too many numbers"

What version of PWM are you using?

pwmVersion="1.7.1" pwmBuild="1232" pwmBuildType="Release"

What ldap directory and version are you using?

OpenLDAP

Please paste any error log messages below:

Tue May 05 16:59:01 PDT 2015, TRACE, password.pwm.util.Helper, 
externalJudgeMethod 'password.pwm.PwmPasswordJudge' returned a value of 24
Tue May 05 16:59:01 PDT 2015, TRACE, 
password.pwm.ws.server.rest.RestCheckPasswordServer, 
{uid=wsanders,ou=People,dc=technorati,dc=com} real-time password validator 
called for uid=wsanders,ou=People,dc=technorati,dc=com
  process time: 2ms
  passwordCheckInfo string: {"version":2,"strength":24,"match":"MATCH","message":"New password has too many numbers","passed":false,"errorCode":4016} [172.16.101.73]
Tue May 05 16:59:01 PDT 2015, DEBUG, password.pwm.ws.server.RestServerHelper, 
{uid=wsanders,ou=People,dc=technorati,dc=com} REST WebService Request: POST 
request for: /pwm/public/rest/checkpassword 
  pwmFormID='3Pre108PWV11H6gD2Xw5EBevYiC2UVjG14d267b42a3u7v73f' [172.16.101.73]
Tue May 05 16:59:01 PDT 2015, TRACE, 
password.pwm.ws.server.rest.RestCheckPasswordServer, 
{uid=wsanders,ou=People,dc=technorati,dc=com} real-time password validator 
called for uid=wsanders,ou=People,dc=technorati,dc=com
  process time: 1ms

Original issue reported on code.google.com by wsand...@technoratimedia.com on 6 May 2015 at 12:11

[GoogleCodeExporter]

Somehow "password.policy.allowNumeric" was still "false" in the config XML even 
though it was enabled in the UI.

I say close this out as "unable to reproduce" and blame it on browser caching.

If any other users see this, check to see if the configuration XML matches the 
UI settings.

Original comment by wsand...@technoratimedia.com on 6 May 2015 at 12:30

[GoogleCodeExporter]

Original comment by jrivard on 8 May 2015 at 2:58

• Changed state: Invalid