You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
By company policy all of our AD account's display name are formatted like ", "
When the user sees there login in the list of users on the workstation they only see their last name. There seems to be a issue with the comma in the display name.
Then I would suggest asking the GDM developers (or accountsservice which IIRC feeds the info into GDM). SSSD is only more or less responsible for delivering the data. In your case the GECOS attribute is already displayed as "West, Michal R" so I would expect GDM to display that as well.
I'm fine with leaving this ticket open against SSSD, but so far I think SSSD is behaving correctly, can you ask GDM people what do they think?
_comment0: The comma is used as a separator in the GECOS field by some older applications like finger, see https://en.wikipedia.org/wiki/Gecos_field fir details. => 1463664420565562
Where would I go to submit a ticket for GDM? What looks to be needed is the support of wrapping the content in the gecos field with quotes, similar to CSV files. So that the comma doesn't get confused with an actual field separator.
Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/3011
By company policy all of our AD account's display name are formatted like ", "
When the user sees there login in the list of users on the workstation they only see their last name. There seems to be a issue with the comma in the display name.
Comments
Comment from johnwcarew at 2016-05-11 20:58:35
Fields changed
priority: major => minor
Comment from jhrozek at 2016-05-18 18:41:26
I'm not sure this is an sssd issue. What is the output of getent passwd $username for that user? What display manager is that?
Comment from johnwcarew at 2016-05-18 19:21:20
We are using gnome.[[BR]]
This is the output of the getent command.[[BR]]
westmr1:*:12083:57282:West, Mikal R:/home/westmr1:/bin/csh
Comment from jhrozek at 2016-05-19 09:42:16
Then I would suggest asking the GDM developers (or accountsservice which IIRC feeds the info into GDM). SSSD is only more or less responsible for delivering the data. In your case the GECOS attribute is already displayed as "West, Michal R" so I would expect GDM to display that as well.
I'm fine with leaving this ticket open against SSSD, but so far I think SSSD is behaving correctly, can you ask GDM people what do they think?
Comment from sbose at 2016-05-19 15:26:40
The comma is used as a separator in the GECOS field by some older applications like finger, see https://en.wikipedia.org/wiki/Gecos_field for details.
_comment0: The comma is used as a separator in the GECOS field by some older applications like finger, see https://en.wikipedia.org/wiki/Gecos_field fir details. => 1463664420565562
Comment from johnwcarew at 2016-05-19 16:59:20
Where would I go to submit a ticket for GDM? What looks to be needed is the support of wrapping the content in the gecos field with quotes, similar to CSV files. So that the comma doesn't get confused with an actual field separator.
Comment from jhrozek at 2016-05-19 17:08:10
I would say https://bugzilla.gnome.org/ or the bug tracker for your distribution.
Comment from jhrozek at 2016-05-26 10:41:04
Since this is not an issue in sssd, I'm closing this ticket.
resolution: => invalid
status: new => closed
Comment from johnwcarew at 2017-02-24 14:49:14
Metadata Update from @johnwcarew:
The text was updated successfully, but these errors were encountered: