#3823 A Windows username with uppercase letter become a username with lowercase in Linux
Closed: Invalid 5 years ago Opened 5 years ago by numopen.

I created a user named "Jean" with J and not j, on a Windows 2008 SP2 server.

On a Linux computer, I joined the Active Directory (domain = "2008-standard.numopen") and now, I can login as a Windows user on my Linux computer.
With LightDM, I can open a session as Jean@2008-standard.numopen or as jean@2008-standard.numopen.
But when I want to mount a Windows shared folder with pam_mount, the option <volume user="Jean@2008-standard.numopen" ... /> doesn't work, I must use <volume user="jean@2008-standard.numopen" ... />

Is it a problem with sssd or with Windows server or something else ?


How does your sssd.conf looks like? Are you using the AD or the plain LDAP provider?

Maybe setting 'case_sensitive = Preserving' in the [domain/...] section helps.

I join here my sssd.conf.

sssd.conf-1.png

I'm using sssd like here : http://www.numopen.fr/Integrer-un-ordinateur-Linux-Mint-MATE-dans-un-domaine-Active-Directory

I will try this case_sensitive option but in the sssd help says :
"True
Case sensitive. This value is invalid for AD provider."

I tried with the option case_sensitive = Preserving and it works, the same user ('Jean' and not 'jean' is used both on Windows server and in Linux ! Thank you very much.
But now if I write 'id jean@2008-standard', Linux shows me the uid and gid of Jean instead of saying that this user doesn't exist. it's not important for me but it is wrong, isn't it ?

Capture_du_2018-09-10_12-10-08.png

I think it's actually expected, this is how the preserving option should work - the input is matched regardless of the case, but the case is preserved as it was on the server.

So if everything works, I hope this ticket can be closed?

Yes, you can close this ticket. Thank you for your help.

Metadata Update from @jhrozek:
- Issue close_status updated to: Invalid
- Issue status updated to: Closed (was: Open)

5 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/4817

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata
Attachments 5