INVALID_CONFIG error on New User Registration Module

[GoogleCodeExporter]

When New User Registration Module is activated and used, the following error 
occurs:

The PWM configuration is invalid or corrupt. Please correct the error, or 
remove the configuration file. { 5033 ERROR_INVALID_CONFIG (ldap naming 
attribute 'cn' is not in form configuration, but is required) fields: [cn] } 

My config is attached.

What steps will reproduce the problem?
1.Activate New User Registration Module
2.Browse to pwm/public/NewUser
3.

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

What version of PWM are you using?
1.5.5

What ldap directory and version are you using?
openldap 2.4.23

Please paste any error log messages below:
2011-07-09 01:41:48, ERROR, servlet.TopServlet, {0~} pwm error during page 
generation: 5033 ERROR_INVALID_CONFIG (ldap naming attribute 'cn' is not in 
form configuration, but is required) fields: [cn] [192.168.122.1]

Original issue reported on code.google.com by erdem.ba...@gmail.com on 8 Jul 2011 at 10:43

• Blocked on: #84

Attachments:

• PwmConfiguration.xml

[GoogleCodeExporter]

Running pwm 1.5.5 on tomcat 6.0.32 with sun-jdk 1.6.0_p26

Original comment by erdem.ba...@gmail.com on 8 Jul 2011 at 10:44

[GoogleCodeExporter]

I can also verify this issue on your demo server on 
http://pwmdemo.weisberg.net/pwm/public/NewUser

Original comment by erdem.ba...@gmail.com on 8 Jul 2011 at 10:53

[GoogleCodeExporter]

I'm not able to reproduce this..  I do see the error in the log on the demo 
server, but I can create a new user without issue.  What values are you putting 
into the new user form?

What browser are you using?

Original comment by jrivard on 8 Jul 2011 at 11:00

• Changed state: Accepted

[GoogleCodeExporter]

Then how do you create a new user on the demo server? When I click the continue 
button I am redirected to the main page.

I am using the default values, with firefox 3.6.16

Original comment by erdem.ba...@gmail.com on 8 Jul 2011 at 11:40

[GoogleCodeExporter]

catalina.out and PwmConfiguration.xml attached

Original comment by erdem.ba...@gmail.com on 9 Jul 2011 at 12:07

Attachments:

• PwmConfiguration.xml
• catalina.out.newuser

[GoogleCodeExporter]

The sequence I see when accessing /pwm/public/NewUser

1. Captcha screen.
  a. enter data.
  b. click verify.
2. New user screen
  a. enter data
  b. click create user
3. Success screen.
  a. click continue.
4. Change Password screen.
  a. enter passwords
  b. click change password
5. Please Wait screen
6. Success screen

Where in the sequence is it breaking for you?

Also, what is the locale string of your operating system and browser set to?

Original comment by jrivard on 9 Jul 2011 at 8:06

[GoogleCodeExporter]

$ locale
LANG=tr_TR.UTF-8
LANGUAGE=
LC_CTYPE="tr_TR.UTF-8"
LC_NUMERIC="tr_TR.UTF-8"
LC_TIME="tr_TR.UTF-8"
LC_COLLATE="tr_TR.UTF-8"
LC_MONETARY="tr_TR.UTF-8"
LC_MESSAGES="tr_TR.UTF-8"
LC_PAPER="tr_TR.UTF-8"
LC_NAME="tr_TR.UTF-8"
LC_ADDRESS="tr_TR.UTF-8"
LC_TELEPHONE="tr_TR.UTF-8"
LC_MEASUREMENT="tr_TR.UTF-8"
LC_IDENTIFICATION="tr_TR.UTF-8"
LC_ALL=tr_TR.UTF-8

My firefox language settings are (in order) tr, en-us, en

I changed the firefox language settings order and now I see the sequence on 
demo server like you mentioned.

Is there a way to fix this problem without changing firefox settings, ie. can 
we display in "en" when user reported locale not found?

Original comment by erdem.ba...@gmail.com on 11 Jul 2011 at 10:35

[GoogleCodeExporter]

Issue 82 has been merged into this issue.

Original comment by jrivard on 11 Jul 2011 at 3:50

[GoogleCodeExporter]

Thanks for testing.  The behavior your asking for is what we should expect, 
crashing with weird errors for new locales is definitely a bug :)

See issue 84.  I think the fix there may resolve this issue as well.  Can you 
build from latest svn revision and test?  If your not familiar with how to do 
that I can post an updated build.

Original comment by jrivard on 11 Jul 2011 at 3:53

• Changed state: Started

[GoogleCodeExporter]

Building from svn r196 fixes the issue, thanks.

Original comment by erdem.ba...@gmail.com on 12 Jul 2011 at 5:08

[GoogleCodeExporter]

Issue 88 has been merged into this issue.

Original comment by jrivard on 14 Jul 2011 at 9:00

[GoogleCodeExporter]

Build #1066 and later has this fix.  Closing.

Original comment by jrivard on 2 Aug 2011 at 8:56

• Changed state: Fixed