CLM - converting "clm created accounts" to LDAP accounts
CLM 502
We are using full CLM and the following accounts were created by a previous admin during setup: jazzrational etl_user ccm_user dcc_user ... Only ccm_user is an actual LDAP user. We found that jazzrational is being used as a replacement for "rm_user" and "qm_user". My questions: If I create dcc_user or etl_user in LDAP, will there be a problem with the current dcc_user/etl_user? Will I lose some type of connection? Does the server require a restart or configuration post change? |
2 answers
Check out some old posts and hopefully it will bring some clarity to you, such as this one.
https://jazz.net/forum/questions/207208/can-we-remove-functional-users-from-ldap Some more comments regarding your particular case. 1. The "jazzrational" account may be used in some other places (interactively), so you may need to create such account on LDAP. But (see below for more details). 2. As I mentioned in the other post, these functional users (in a form <app>_user) do not need to exist in any external user repository. The fact the a "ccm_user" was created on the LDAP server can just be the result of misunderstanding the requirement. You can actually remove this user from LDAP. 3. Each functional user can be assigned one or more internal licenses by default. For example, the "rm_user" has the internal license "RM Application - Internal" by default. If a different user is used in place of a default functional user, make sure that such user is assigned with the corresponding internal license. 4. If you create these functional users on the LDAP server, and make them behave like normal users, you may not have any problems, but it's not recommended. If you're not sure about the implication of modifying or replacing built-in functional users, you'd better keep them as default. |
There is no need to create these users in LDAP.
These application users do not need interactive login capabilities, but leave them active. |
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.