[SSSD-users] Login with Enterprise Principal Name with AD backend
ferrao at if.ufrj.br
Sun May 25 22:57:00 UTC 2014
On May 25, 2014, at 19:51, steve <steve at steve-ss.com> wrote:
> On Sun, 2014-05-25 at 22:31 +0000, Vinícius Ferrão wrote:
>> Hello guys,
>> I’m running sssd version 1.11 in Ubuntu 14.04 LTS (1.11.5-1ubuntu3) to authenticate users from Active Directory from WIndows Server 2012 R2, and I’m trying to achieve logins with the User Principal Name for all users of the domain. But the UPN are always Enterprise Principal Names.
>> Let-me illustrate the problem with my user account:
>> Domain: local.example.com
>> sAMAccountName: ferrao
>> UPN: ferrao at example.com (there’s no local in the UPN)
>> I can successfully login with the sAMAccount atribute, which is fine, but I can’t login with ferrao at example.com which is my UPN. The optimum solution for me is to allow logins from sAMAccount and the UPN. If’s not possible, the UPN should be the right way instead of the sAMAccountName.
>> Another annoyance is the homedir pattern with those options in sssd.conf:
>> default_shell = /bin/bash
>> fallback_homedir = /home/%d/%u
>> What I would like to achieve is separated home directories from the EPN. For example:
>> But with this pattern I can’t map the way I would like to do.
>> I’ve looked through man pages and was unable to find any answers for this issues.
>> Thanks in advance,
> Not sure about the accountname bit but the 2012 schema has full support
> for rfc2307 out of the box. Store whatever home directory you like on a
> per user basis under their DN as:
> with whatever shell they need.
> The 1.11.5 ad backend will automatically grab them with no further
> configuration needed.
Hello Steve, thank you for the fast reply. I was aware of the AD ldap schema.
I’m avoiding to mess with Unix specific atributes inside AD because Microsoft started the decommissioning of Unix Services. Today still exists hacks to enable the UNIX Attributes tab in the User Preferences, but they can only be enabled activating Services for NIS from the Powershell.
I know it’s an option, but the whole point of using SSSD is to avoid messing with AD. If it’s impossible to achieve in the SSSD side, that will be the solution for the second issue.
> sssd-users mailing list
> sssd-users at lists.fedorahosted.org
More information about the sssd-users