Highlighted
Absent Member.. Absent Member..
Absent Member..
761 views

Where does the account _system_user_ come from?

Jump to solution

I'm looking at data in the td.sessions_history table of the site admin database. there is repeated entries of access by user name _system_user_  this is not an account I'm aware of. does anyone know what that account represents, where is comes from and more importantly what it is doing? It seems to be in most of not all our projects

 

We are using ALM 12.01

 

 

David

0 Likes
1 Solution

Accepted Solutions
Highlighted
Honored Contributor.. Honored Contributor..
Honored Contributor..

Re: Where does the account _system_user_ come from?

Jump to solution

Hi there,

 

I too have just found this "user" after upgrading to v12.01 and which I notice randomly logs in to projects. My query on the sessions_history DB show that there have been almost 5000 logins by this "user" in the past 30 days. As I couldn’t work out what this "user" was doing I asked HP.

 

HP's reply is:

 

The _system_user_ account is an internal user used to perform internal operations. It was introduced in ALM 11. Any operations on ALM entities are monitored by the permissions granted to the user performing them and thus an internal user is needed. For example, QPM Calculation engine needs to access to different projects and entities.

Here are some characteristics for this user:

1.       It does not have a password and it is internal thus preventing login using this user.
2.       It does not consume a license. This is a user created for internal server jobs proposes.
3.       This user is created upon installation/upgrade process
4.       It enables automatically on project creation, as part of the TDAmin group. This indicates that the user's  permissions are equal to regular admin user.
5.       The user is hidden from the Site Administrator's users list and it does not appear as one of the users enabled on  the projects. This is done to prevent deleting the user or changing its properties.
6.       The records on the user are stored inside the qcsiteadmin_db. If the user list is managed using LDAP, the user is  not defined in it. Its scope is only inside ALM since it is not representing a normal user.

 

Regards,

 

 

 

View solution in original post

1 Reply
Highlighted
Honored Contributor.. Honored Contributor..
Honored Contributor..

Re: Where does the account _system_user_ come from?

Jump to solution

Hi there,

 

I too have just found this "user" after upgrading to v12.01 and which I notice randomly logs in to projects. My query on the sessions_history DB show that there have been almost 5000 logins by this "user" in the past 30 days. As I couldn’t work out what this "user" was doing I asked HP.

 

HP's reply is:

 

The _system_user_ account is an internal user used to perform internal operations. It was introduced in ALM 11. Any operations on ALM entities are monitored by the permissions granted to the user performing them and thus an internal user is needed. For example, QPM Calculation engine needs to access to different projects and entities.

Here are some characteristics for this user:

1.       It does not have a password and it is internal thus preventing login using this user.
2.       It does not consume a license. This is a user created for internal server jobs proposes.
3.       This user is created upon installation/upgrade process
4.       It enables automatically on project creation, as part of the TDAmin group. This indicates that the user's  permissions are equal to regular admin user.
5.       The user is hidden from the Site Administrator's users list and it does not appear as one of the users enabled on  the projects. This is done to prevent deleting the user or changing its properties.
6.       The records on the user are stored inside the qcsiteadmin_db. If the user list is managed using LDAP, the user is  not defined in it. Its scope is only inside ALM since it is not representing a normal user.

 

Regards,

 

 

 

View solution in original post

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.