search

SpacyNG / pwm

Automatically exported from code.google.com/p/pwm
0 stars 0 forks source link

Doesn't seem to be updating the configuration from disk? #43

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.  Finalize config file (change ldap server)
2.  Check config in memory and ldap servers are still 127.0.0.1
3.  Check PwmConfiguration.xml and all setting are as we set them
4.  On admin/config.jsp we see the correct values
5.  On config/ConfigManager we see incorrect values (defaults??)

What is the expected output? What do you see instead?
It is authenticating us and writing the responses to the correct tree but at 
every checkresponses hit, you are asked for you responses again.  Why is this 
happening??

What version of the product are you using? On what operating system?
PwmConfiguration pwmVersion="1.5.2" pwmBuild="996" createTime="2011-02-24 
18:18:12 +0000" modifyTime="2011-03-08 19:26:33 +0000"

Please provide any additional information below.

Original issue reported on code.google.com by james.sp...@gmail.com on 8 Mar 2011 at 7:36

GoogleCodeExporter commented 9 years ago 
1. Once Pwm is configured and "finalized", ConfigManager no longer shows the 
current configuration.  You can edit the PwmConfiguration.xml and set the 
property "configIsEditable" to true to be able to edit the configuration using 
the ConfigManager url once again.  The as yet unreleased v1.5.3 will make this 
situation a little more obvious.

2. If your still experiencing the checkresponse issue, can you set the log 
level to "TRACE" and share the log of the problem occuring?  The most likely 
cause is the logged in user needs permission to read the pwmResponseSet 
attribute, but the logs should show what is happening.

Original comment by jrivard on 9 Mar 2011 at 6:02

GoogleCodeExporter commented 9 years ago 
We did put the log level into DEBUG and TRACE but only the login is show.  
Nothing shows up to say they were sent to the set responses page.  I have 
included the log.  Look at entries for 2011-03-08.  We have not launched 1.5.2 
yet so this in only our testing.

Original comment by james.sp...@gmail.com on 9 Mar 2011 at 12:08

Attachments:

GoogleCodeExporter commented 9 years ago 
Any update you can share?  We have been testing for days now and cannot get 
past this issue.

Original comment by james.sp...@gmail.com on 15 Mar 2011 at 11:09

GoogleCodeExporter commented 9 years ago 
I've looked through the log, and I can't find any issues as to why this would 
be the case.  I've tested with the latest code, and can't reproduce.  It may be 
a bug in v1.5.2.  Can you please download the latest build just posted (v1022) 
and try again?  If it happens again, please post the trace file here again as 
there are additional logging statements that may shed light on the problem.

Original comment by jrivard on 16 Mar 2011 at 5:50

GoogleCodeExporter commented 9 years ago 
That worked!  The problem does not exist in b1022.  How long before that 
version is considered stable?  The real question is, should I go live with this 
version?

Original comment by james.sp...@gmail.com on 16 Mar 2011 at 6:05

GoogleCodeExporter commented 9 years ago 
I wanted to add this comment to comment #5.  Everything is working but in the 
logs we are getting the following warning.  Doesn't seem to be hurting us but I 
wanted to share it with you.

2011-03-16 15:20:23, WARN , util.Helper, {p,santa_claus} unexpected error while 
searching GUID attribute pwmGUID for uniqueness: [LDAP: error code 17 - 
Undefined Attribute Type], cannot write GUID value to user 
[172.20.201.11/cerberus1.owens.edu]

This is a real user in our test environment.

Original comment by james.sp...@gmail.com on 16 Mar 2011 at 7:43

GoogleCodeExporter commented 9 years ago

Original comment by jrivard on 16 Mar 2011 at 11:01