Environment
Novell ZENworks Configuration Management 11.3
Novell ZENworks Configuration Management 11.2.4
Novell ZENworks Configuration Management 11.2.4
Situation
ZCM zone is attached to an LDAP user source.
Changes to username and password field in the user source general configuration do not get effective.
ZCC appears to accept the new proxy user credentials but to old one stays effective.
Error message in debug level zcc.log from ZCM 11.3 Primary Server:
"...
[DEBUG] [05/20/2014 17:52:50.738] [17900] [ZENServer] [102] [zenworks] [ZCC] [] [com.novell.zenworks.datamodel.exceptions.DataModelUsageException: Must supply certificates if using SSL.
at com.novell.zenworks.datamodel.services.users.BasicUserAdminImpl.update(BasicUserAdminImpl.java:311)
at com.novell.zenworks.datamodel.services.users.UserAdminImpl.update(UserAdminImpl.java:423)
at com.novell.zenworks.core.web.internal.pages.users.UserSourceDetailsGeneral.usernamePasswordDialog_close(UserSourceDetailsGeneral.java:321)
...
] [Must supply certificates if using SSL.] [] [com.novell.zenworks.datamodel.exceptions.DataModelUsageException] [ZENServer]
..."
Changes to username and password field in the user source general configuration do not get effective.
ZCC appears to accept the new proxy user credentials but to old one stays effective.
Error message in debug level zcc.log from ZCM 11.3 Primary Server:
"...
[DEBUG] [05/20/2014 17:52:50.738] [17900] [ZENServer] [102] [zenworks] [ZCC] [] [com.novell.zenworks.datamodel.exceptions.DataModelUsageException: Must supply certificates if using SSL.
at com.novell.zenworks.datamodel.services.users.BasicUserAdminImpl.update(BasicUserAdminImpl.java:311)
at com.novell.zenworks.datamodel.services.users.UserAdminImpl.update(UserAdminImpl.java:423)
at com.novell.zenworks.core.web.internal.pages.users.UserSourceDetailsGeneral.usernamePasswordDialog_close(UserSourceDetailsGeneral.java:321)
...
] [Must supply certificates if using SSL.] [] [com.novell.zenworks.datamodel.exceptions.DataModelUsageException] [ZENServer]
..."
Resolution
Workaround:
- Temporarily disable SSL on the user source configuration
- Change username and/or password
- Re-enable SSL