Unknown error using "Update Attributes" module

[GoogleCodeExporter]

Hello, I can't seem to get the "Update User Info" feature to work.
have eDirectory 8.8 running on Server 2008 along with IDM 3.6, Java
1.5 and Tomcat 5.5. For troubleshooting purposes I have given the
PwmProxy and the actual user (user1) that I am trying to update full
Admin rights. If I use a 3rd party LDAP tool and authenticate as user1
(my test user with full admin rights) I don't have an issue. When I
use the PWM interface I keep getting the error "Unknown error. If this
error occurs repeatedly please contact your helpdesk." but the user in
eDirectory does get the update. I will include my Tomcat error below.

2010-09-10 13:58:56, INFO , pwm.AuthenticationFilter, {4-,user1}
successful ssl authentication for cn=user1,ou=TEST,o=IDMWO (69ms)
[192.168.0.99/ts99.portwinnipeg.ca]
2010-09-10 13:59:17, INFO , servlet.UpdateAttributesServlet, updating
attributes for cn=user1,ou=TEST,o=IDMWO
2010-09-10 13:59:17, INFO , pwm.Helper, {4-,user1} set attribute on
user cn=user1,ou=TEST,o=IDMWO (title=dfdff) [192.168.0.99/
tsc251.uwinnipeg.ca]
2010-09-10 13:59:17, WARN , servlet.TopServlet, {4-,user1} unexpected
exception during page generation: may not read STRING_ARRAY value for
setting: UPDATE_ATTRIBUTES_WRITE_ATTRIBUTES [192.168.0.99/pc.test.ca]
java.lang.IllegalArgumentException: may not read STRING_ARRAY value
for setting: UPDATE_ATTRIBUTES_WRITE_ATTRIBUTES
    at
password.pwm.config.StoredConfiguration.readStringArraySetting(StoredConfigurati
on.java:
171)
    at
password.pwm.config.Configuration.readStringArraySetting(Configuration.java:
68)
    at
password.pwm.servlet.UpdateAttributesServlet.handleUpdateRequest(UpdateAttribute
sServlet.java:
161)
    at
password.pwm.servlet.UpdateAttributesServlet.processRequest(UpdateAttributesServ
let.java:
84)
    at password.pwm.servlet.TopServlet.handleRequest(TopServlet.java:75)
    at password.pwm.servlet.TopServlet.doPost(TopServlet.java:117)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:647)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
    at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilt
erChain.java:
269)
    at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.
java:
188)
    at
password.pwm.AuthenticationFilter.processAuthenticatedSession(AuthenticationFilt
er.java:
133)
    at
password.pwm.AuthenticationFilter.doFilter(AuthenticationFilter.java:
83)
    at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilt
erChain.java:
215)
    at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.
java:
188)
    at password.pwm.SessionFilter.doFilter(SessionFilter.java:257)
    at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilt
erChain.java:
215)
    at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.
java:
188)
    at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:
213)
    at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:
172)
    at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:
127)
    at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:
117)
    at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:
108)
    at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:
174)
    at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:
873)
    at org.apache.coyote.http11.Http11BaseProtocol
$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:
665)
    at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:
528)
    at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorker
Thread.java:
81)
    at org.apache.tomcat.util.threads.ThreadPool
$ControlRunnable.run(ThreadPool.java:689)
    at java.lang.Thread.run(Thread.java:619)

Original issue reported on code.google.com by jrivard on 10 Sep 2010 at 9:05

[GoogleCodeExporter]

Looks like a PWM bug at first glance.  Will investigate.

Original comment by jrivard on 10 Sep 2010 at 9:05

[GoogleCodeExporter]

Thanks, please ignore the 192.168.0.99 dns names.

Original comment by dkarlows...@yahoo.com on 10 Sep 2010 at 9:55

[GoogleCodeExporter]

Should be resolved as of b982.  Please re-open this bug if the problem remains.

Original comment by jrivard on 21 Sep 2010 at 6:41

• Changed state: Fixed

[GoogleCodeExporter]

Thanks, seems fine now.

Original comment by dkarlows...@yahoo.com on 27 Sep 2010 at 1:49