About "directory service that is not writable" pro
I hoped to migrate Tomcat to WAS, after following the insturction to change the configuration, I got the following message in the user management view for my admin user, which caused there is no admin user in my RTC and can't do anything there. Does anyone have some ideas about this problem? Thanks.
You are using a directory service that is not writable. User roles cannot be modified. |
5 answers
When you migrated from Tomcat to WAS, did you also change your user
registry settings to LDAP? When you move your RTC user registry away from the Tomcat user registry, the default ADMIN/ADMIN account is not available. You would need to make sure that your new user registry has a user in the JazzAdmin group, and you should log in with that user. If you provide a little more detail about how you have reconfigured your server, perhaps we can give some suggestions. - Matt Lavin Jazz Server Team On Fri, 2008-11-21 at 10:18 +0000, mattcui wrote: I hoped to migrate Tomcat to WAS, after following the insturction to |
When you migrated from Tomcat to WAS, did you also change your user I hoped to migrate Tomcat to WAS, after following the insturction to Thanks for the response. When I installed and ocnfigured RTC of Tomcat edition, I chose "Non-LDAP External Registry", I created an admin user "mattcui" and seemed "ADMIN" user was diabled accordingly. As you pointed out, after migration to WAS, seems it can't find that user registry, and only can login with "Guest", do you have some ideas of how to make it find the previous user registry or re-enable "ADMIN" user? Thanks for your help! - Matt Cui |
|
It sounds like the simplest solution is to continue to use Tomcat rather
than go to WAS. For small installations, using Tomcat is easier to manage and configure than a WAS install, especially if you are trying to no use a LDAP user registry. Is it possible to use Tomcat? - Matt Lavin Jazz Server Team On Sat, 2008-11-22 at 09:48 +0000, mattcui wrote: lavinmwrote: Thanks for the response. When I installed and ocnfigured RTC of Tomcat edition, I chose "Non-LDAP External Registry", I created an admin user "mattcui" and seemed "ADMIN" user was diabled accordingly. As you pointed out, after migration to WAS, seems it can't find that user registry, and only can login with "Guest", do you have some ideas of how to make it find the previous user registry or re-enable "ADMIN" user? Thanks for your help! - Matt Cui |
|
There is no way to re-enable ADMIN user? I used "Non-LDAP External Registry" for RTC of tomcat edtion, RTC of WAS edtion can't use this kind of user registry? Thanks. I hoped to change it to use IBM bluegroup LDAP, then anyone of company can login my RTC...
It sounds like the simplest solution is to continue to use Tomcat rather lavinmwrote: Thanks for the response. When I installed and ocnfigured RTC of Tomcat edition, I chose "Non-LDAP External Registry", I created an admin user "mattcui" and seemed "ADMIN" user was diabled accordingly. As you pointed out, after migration to WAS, seems it can't find that user registry, and only can login with "Guest", do you have some ideas of how to make it find the previous user registry or re-enable "ADMIN" user? Thanks for your help! - Matt Cui |
|
There is nothing magic about the 'ADMIN' user other than we pre-create
it in the Tomcat user registry and put them in the JazzAdmin group. If you are using a non-Tomcat registry, then you would need to create a user and put him in the JazzAdmin group. Perhaps we could work through the problems you are having creating that new admin user. - Matt Lavin Jazz Server Team On Mon, 2008-11-24 at 14:38 +0000, mattcui wrote: There is no way to re-enable ADMIN user? I used "Non-LDAP |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.