By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 2549 - Users created in KUser don't appear in TDM
Summary: Users created in KUser don't appear in TDM
Status: RESOLVED INVALID
Alias: None
Product: TDE
Classification: Unclassified
Component: tdeadmin (show other bugs)
Version: R14.0.x [Trinity]
Hardware: Other Linux
: P5 minor
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2015-11-22 07:50 CST by Kristopher
Modified: 2018-08-03 22:53 CDT (History)
3 users (show)

See Also:
Compiler Version:
TDE Version String:
Application Version:
Application Name:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kristopher 2015-11-22 07:50:20 CST 
Normally when I create as user, I do so from command line using the useradd command. Users added this way always appear in the TDM user list.

Recently I decided to give KUser a try. I was able to successfully add a user, but it does not appear in the TDM user list. I _can_ log in with the user if I manually type the user name, it just does not appear in the user list for me to click.

I queried passwd for the status of two accounts. The user 'guest' was created with useradd and appears in the user list, 'guest1' was created by KUser and does *not* appear in the user list:

root@dell:~# passwd -S guest
guest P 11/22/2015 0 99999 7 -1
root@dell:~# passwd -S guest1
guest1 P 11/22/2015 0 -1 -1 -1

Also, the users created by useradd have UIDs in the 1000+ range while KUser seems to use 500+ range. It would seem that KUser ignores the setting under Control Center -> System Administration -> Login Manager -> Users -> System UIDs that says that UIDs *below* 1000 are system accounts (this is the default setting). Creating a new user with KUser and having it force the UID to somewhere within the range UIDs specified as non-system users in the Login Manager *does* cause the newly created user to appear in TDM's user list, meaning that the issue is not in the way KUser is creating accounts, but instead the issue is that KUser is ignoring the Systerm UIDs setting for the Login Manager.

KUser should honor the System UIDs setting by default, and have an option added for creating "system accounts".
Comment 1 Francois Andriot 2015-12-15 14:12:14 CST 
Hello, it looks like there are build-time options in tdeadmin to change the first UID and GID for kuser.

--with-first-uid        first normal user ID [default=500]
--with-first-gid        first normal group ID [default=500]

It's probably just a matter of building the package with these options set to 1000.
Comment 2 Michele Calgaro 2018-08-03 22:53:38 CDT 
Verified that a new user appears in TDM. As described in comment 1, this was probably a mistake on user configuration.