It's all about the answers!

Ask a question

WAS user management for RTC

Mike Brouwers (341318) | asked Dec 19 '14, 11:31 a.m.

We currently are looking into migrating our current RTC infrastructure from Tomcat to WAS.

One of our concerns is that we need to migrate our users from Tomcat’s users xml file to WAS.

When using a Federated Realm we need to create the userID and password in WAS, assign it to the right application, then create the user in RTC.

For LDAP this is the same.

When a user wants it's password changed, an administrator needs to change that password for that user since changing the password through RTC is disabled.

Are there other options?

For us the ideal situation is that everything will be managed through the RTC user registry (like it is in Tomcat) so when a user wants to change his password, it is possible to do this through the RTC interface, 

We would like to have one single place where the user can login and manage it’s password, and everything get’s updated accordingly.

How can we achieve this?

Can we use WAS? Do we need to stick with Tomcat?


Accepted answer

permanent link
Donald Nong (14.5k414) | answered Dec 21 '14, 7:15 p.m.
If changing password within RTC is your main concern, you probably have to stick with Tomcat, since that's the only way that allows you to do so. Some LDAP servers, such as Microsoft AD, have some simple interface for changing passwords, but obviously that's outside of RTC. WebSphere federated "file based" user repository will require an admin to change a user's password.
I think you need to balance the pros and cons of using either WAS or Tomcat before making a decision.

Mike Brouwers selected this answer as the correct answer

Your answer

Register or to post 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.