Changes in Administration panel are ignored

[csat]

Hi All,

I have installed version 5.1.10 on Centos. My congratulations on an excellent product. I have been able to configure it to work with MySQL and Active Directory. I think everything is working as I want except for a couple of things because when I change them on the Administration > Configuration, they do not get changed:

1) The logos. I can see the new logos setup in the configuration but still the OpenKM logos are displayed.
2) The other one is more critical which is the default.admin.role and the default.user.role. I have change them because I have created in AD the groups OpenKM_Users and OpenKM_Admin. I have set this values in the configuration. I have check the MySQL and the values are correct but when I run OpenKM it ignores these values and uses the defaults AdminRole and UserRole. I have add them also to OpenKM.cfg but no change as I believe that on 5.1.x they get ignored.

Once I run the server I have grep for UserRole and I can see that the application have created temporary files with the defaults values:
/opt/openKM/jboss-4.2.3.GA/server/default/tmp/deploy/tmp4574301085175814966OpenKM-exp.war/WEB-INF/web.xml.org: <role-name>UserRole</role-name>

If I grep for my values (OpenKM_Users and OpenKM_Admin) and they are no where to be found.

This is annoying because it makes the login fail unless I set a defualtRole to AdminRole or UserRole in login-config.xml which allows everybody to login.

This sounds like a bug to me but would appreciate any feedback on how to sort it out or investigate further.

Thanks in advance
Carlos

[jllort]

- First do not change default UserRole and AdminRole name's there's no need for doing it. Your life will be more easy if you define in you ldap this role name. You decide for more hard option, then I suggest first login with this default rolesname and then try change ( not all at the same time ). Changin everything you do not know if your problem is in war file configuration, database or in login-config.xml ( go step by step ).
- Changing tmp files is not good idea, when server will be restarted will change xml files etc... you should make changes in OpenKM.war ( really is zip file ).
- Changes from version 5.1.X are done in administration not in OpenKM.cfg ( is only used for first time starting openkm, then is used configuration parameters stored in database ).

[csat]

Thanks for your reply and sorry I did not explain myself clearly. I setup the system and once things were working, I chnaged to LDAP authentication and went to the configuration in admin panel and change the values. The problem is that these new values are ignored. To try to diagnose the problem and arrive at the conclusion that the values in the admin panel are not used, I looked into the temp files but my intention is not to change them as I think this should be done automatically by the app. Samething happens with the logos.

I am going to follow your advise and change the names in LDAP eventhough this is going to mean a big argument with my system admin. Any way, I thin that if it is a bug, it should be fixed and if changes the default roles is not allowed, then the option should be taken out.

I have done some additional testing and by modifying the OpenKM.war it will work but then I do not know whay logo and roles need to be changed in Admin panel and also in the OpenKM.war. I take it to be work in progress.

Regards
Carlos

[jllort]

Bad diagnostic, changes in administration take effect at the moment except two that needs restarting application. Opnoffice path and the change of ldap principal adapter need restarting application, boths needs it because first starts soffice service happens only when openkm is started, the second because is class yet loaded during openkm starting process and can not be re-loaded on fly ( it's bindind users security etc... ).

Into web.xml file is where applications mandatory need to define authentication security roles, that can not be changed is architecture standard. About changing UserRole and AdminRole, during repository creation is set some security in parent okm:root nodes etc... that should be changed too or simply add in OpenKM.cfg the changes and rebuild the repository.
Logo in not needed to be changed on war file.