Bug 1008536 - Incorrect user information
Summary: Incorrect user information
Keywords:
Status: CLOSED DUPLICATE of bug 986211
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ipa
Version: 6.3
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Martin Kosek
QA Contact: Namita Soman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-16 14:43 UTC by cbulist
Modified: 2013-10-01 08:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-01 08:11:22 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description cbulist 2013-09-16 14:43:02 UTC
Description of problem:

We have a freeipa server working in our test scenario without further problems. We are able to use SUDO, HBAC etc.
Our problem is when we change a user info (Name or Last Name) and check it using the command: getent passwd id_user it showed us the older user information


Version-Release number of selected component (if applicable):

RedHat 6.3 (freeipa server:3.0.0-26) and RedHat 5.9 (freeipa client 2.1.3.-5)


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

You can find more information/description/testing about this problem at:

https://www.redhat.com/archives/freeipa-users/2013-September/msg00030.html

Comment 2 Martin Kosek 2013-09-17 06:19:33 UTC
User name shown in "getent passwd USER" is read from GECOS attribute. Can you please try changing it instead and then checking the getent passwd output?

Note that if the user is already cached in SSSD, it won't show unless you clear the cache as indicated in the referred freeipa-users list.

FYI, Bug 986211 which adds this field also to UI (currently it is available only in CLI) will be fixed in RHEL-6.5.

Comment 4 Martin Kosek 2013-09-25 11:03:06 UTC
Hello cbulist, did my advise in Comment 2 help?

My current plan is to close the bug as duplicate to Bug 986211 as then the GECOS field will be better visible and editable in UI and should thus solve your issue.

Comment 5 Martin Kosek 2013-10-01 08:11:22 UTC
I received no response, closing as duplicate to 986211. Please feel free to reopen this bug if your issue is not fixed.

*** This bug has been marked as a duplicate of bug 986211 ***


Note You need to log in before you can comment on or make changes to this bug.