During installation, the administrative login account was created in tomcat-users.xml. You can add more accounts to this file, to allow other users to log in.
Note: CA recommends that you use this method for a test or demonstration system only. For a production system, use an existing directory or database for authentication.
Every login account in tomcat-users.xml must correspond to a user in the warehouse. The User ID must match the user name that you specify in the XML file.
Note: Before you begin, stop the Tomcat service: CA Directory Webserver. This disconnects any currently open sessions.
To add a new login account in Tomcat
DXHOME/../dxwebserver/conf/tomcat-users.xml
<user username="" password="" roles=""/>
Specifies the name that the user enters when they log in to DXmanager. Make sure that this value corresponds to the User ID of a user in the warehouse.
Specifies the password for this user. If you have enabled hashed passwords, include the hashed value here.
Specifies the roles for this user. This is a comma-separated list, so you can specify more than one role.
A user can now use this account to log in to DXmanager. The account's roles define what tasks they can do.
Example: Assign Two Roles to a User
The following snippet of tomcat-users.xml shows the details for two users:
<tomcat-users> <user name="Jenny Watts" password="5460cdf0d7c4370224eb2be031b7c7eb724fa583" roles="dxmanagerMonitor" /> <user name="Terry Morrow" password="5baa61e4c9b93f3f0682250b6cf8331b7ee68fd8" roles="dxmanagerSuperUser" /> </tomcat-users>
In this example, Jenny Watts has the Monitor role, and Terry Morrow has the Superuser role. This means that Jenny can only monitor DSAs and customize monitoring functionality. Terry can perform all DXmanager tasks as he has Superuser access.
Note: The passwords in this example are hashed, which means that hashed passwords must be enabled in Tomcat.
Copyright © 2009 CA. All rights reserved. | Email CA about this topic |