Hi

I think I found an issue in LAM 4.9. I wish to get confirmation.

I compiled Samba 4 a few days ago to build a DC on a Debian Wheezy box.

I added LAM for account management, and I created a test user.

I had headache trying to configure sssd on an other Wheezy box, due to the
userPrincipalName attribute of the test user :

If I switch to sAMAcountName my setup work as expected. So I checked the
value of the userPrincipalName in my directory (from LAM, using the tree
view).

I noticed this attribute has the following form : user@dc=domain,dc=com .
I'm not used to se this syntax in a windows DC.

I checked how this attribute is set on a Windows 2008R2 DC, and it has a
different form : [email protected] (the one I'm used to find).

I then changed the attribute of my test user to the latest form, and
reconfigured sssd to use userPrincipalName. Now sssd works.

Of course, if I revert my changes un my directory, the test user is no
longer able to login.

Therefore I think LAM sets up a wrong value in userPrincipalName.

Am I right ?
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Lam-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lam-public

Reply via email to