Troubles with Active Directory Authentication
Posted: Wed Oct 04, 2006 5:46 am
Hi,
I also posted the same questions on
http://www.scalix.com/community/viewtopic.php?t=3154
(but here there are more details so please answer here.)
I am having troubles with AD integration and Scalix.
My setup scenario is:
1 Domain Controller Windows 2003 Std R2 english, FQDN = w2k3std01.test.int
1 SLES 9 SP3 with Scalix 10.0.1
DNS (on the DC)
zone test.int contains:
w2k3std01 A record = 10.1.2.25
sca01 A record = 10.1.2.30
scalix-default-mail CNAME record = sca01.test.int
scalixdc CNAME record = w2k3std01.test.int
zone 10.1.2.x (reverse):
10.1.2.30 PTR record = sca01.test.int
Scalix Server installation went fine, I used these parameters:
hostname --fqdn = sca01.test.int
mailnode = sca01,test
domain = test.it (not test.int)
Schema Extension went fine (can see correct attributes in AD Schema Management ).
ADUC GUI Extension went fine
I created some Scalix Users from the SAC and tested them with SWA and with the Outlook connector... just fine.
I then created some AD users and set up Synchronization Agreement for omldapsync:
After some trial and errors, omldapsync -u AD_SX1 now correctly updates the users (I can see them with SAC (where they are greyed out) and with any LDAP Browser).
The problem is with AD *AUTHENTICATION*.
As far as I understood, the synchronization agreement cannot (nor should try to) synchronize the user passwords.
1st question: is it correct that, if I don't modify the default pam rules, AD users can log in WITHOUT a password in outlook and in webmail ?
In fact omshowu tells me that password is *unset* for the imported AD users.
Next, I tried to use Kerberos auth and single sign on, but had many troubles.
Here's what I did:
1. Created an AD user "scalix-ual" (FirstName, DisplayName and User Logon Name are "scalix-ual").
2. Tried ktpass with the sintax indicated in the Admin Guide:
But... I think there are some problems: pType is not 1 and etype is RC4-HMAC instead of DES.
In fact, in the docs (Scalix Administration Guide v10.0.1) the output for the ktpass command should be (page 119):
2.b.:
I tried to manually force the correct parameters with:
Is it correct?
Note that this is a Windows 2003 Std R2 domain controller and that the AD domain name ("test.int") is the *same* of the "hostname --fqdn" scalix server (test.int)... may these be source of problems?
---
3.
I merged the keytab files and modified krb5.conf:
-- I used the CNAME scalixdc in a first test ... but then I tried also with the A record (w2k3std01.test.int), by modifying /etc/krb5.conf ... any issues here?
4.
Tested Authentication with SWA and outlook.... users can login WITHOUT a password.
5.
I modified the 4 files (ual.remote, pop3, omslapdeng, smtpd.auth) under /var/opt/scalix/sys/pam.d/
They contain:
as indicated in http://www.scalix.com/community/viewtopic.php?t=3154, but it does not work.
That is, users now are not allowed to login, with using their AD password or a blank password.
In the login name I tried user, user@test.int, user@TEST.INT, User Surname.... none worked.
EDIT: another issue: after the mod. to the pam rules (specifically, omslapdeng), the SAC refuses my scalix administrator (it was sxadmin@sca01.test.int).
I copied back the pam rules for omslapdeng and the SCA worked again.
What did I do wrong?
Should I restart scalix services (which ones?) after every modification?
May you elaborate on the whole setup? Is that correct?
Thank you in advance.
Davide DG.
I also posted the same questions on
http://www.scalix.com/community/viewtopic.php?t=3154
(but here there are more details so please answer here.)
I am having troubles with AD integration and Scalix.
My setup scenario is:
1 Domain Controller Windows 2003 Std R2 english, FQDN = w2k3std01.test.int
1 SLES 9 SP3 with Scalix 10.0.1
DNS (on the DC)
zone test.int contains:
w2k3std01 A record = 10.1.2.25
sca01 A record = 10.1.2.30
scalix-default-mail CNAME record = sca01.test.int
scalixdc CNAME record = w2k3std01.test.int
zone 10.1.2.x (reverse):
10.1.2.30 PTR record = sca01.test.int
Scalix Server installation went fine, I used these parameters:
hostname --fqdn = sca01.test.int
mailnode = sca01,test
domain = test.it (not test.int)
Schema Extension went fine (can see correct attributes in AD Schema Management ).
ADUC GUI Extension went fine
I created some Scalix Users from the SAC and tested them with SWA and with the Outlook connector... just fine.
I then created some AD users and set up Synchronization Agreement for omldapsync:
After some trial and errors, omldapsync -u AD_SX1 now correctly updates the users (I can see them with SAC (where they are greyed out) and with any LDAP Browser).
The problem is with AD *AUTHENTICATION*.
As far as I understood, the synchronization agreement cannot (nor should try to) synchronize the user passwords.
1st question: is it correct that, if I don't modify the default pam rules, AD users can log in WITHOUT a password in outlook and in webmail ?
In fact omshowu tells me that password is *unset* for the imported AD users.
Next, I tried to use Kerberos auth and single sign on, but had many troubles.
Here's what I did:
1. Created an AD user "scalix-ual" (FirstName, DisplayName and User Logon Name are "scalix-ual").
2. Tried ktpass with the sintax indicated in the Admin Guide:
Code: Select all
C:\Program Files\Support Tools>ktpass -princ scalix-ual/sca01.test.int@TEST.INT
-mapuser scalix-ual -pass password -out scalix-ual.keytab -kvno 3
Targeting domain controller: w2k3std01.test.int
Using legacy password setting method
Successfully mapped scalix-ual/sca01.test.int to scalix-ual.
WARNING: pType and account type do not match. This might cause problems.
Key created.
Output keytab to scalix-ual.keytab:
Keytab version: 0x502
keysize 69 scalix-ual/sca01.test.int@TEST.INT ptype 0 (KRB5_NT_UNKNOWN) vno 3 et
ype 0x17 (RC4-HMAC) keylength 16 (0x1aa2b5c696504e29baab22f3a2118473)
But... I think there are some problems: pType is not 1 and etype is RC4-HMAC instead of DES.
In fact, in the docs (Scalix Administration Guide v10.0.1) the output for the ktpass command should be (page 119):
Successfully mapped scalix-ual/scalixserver.acme.net to scalixual.
Key created.
Output keytab to scalix-ual.keytab:
Keytab version: 0x502
keysize 68 scalix-ual/scalixserver.acme.net@ACME.NET ptype 1
(KRB5_NT_PRINCIPAL)
vno 3 etype 0x1 (DES-CBC-CRC) keylength 8 (0xe6fb762ad01f8a9b)
Account has been set for DES-only encryption.
2.b.:
I tried to manually force the correct parameters with:
Code: Select all
C:\Program Files\Support Tools>ktpass.exe -princ scalix-ual/sca01.test.int@TEST.INT -mapuser scalix-ual -pass password -out scalix-ual.keytab -kvno 3 -crypto DES-CBC-MD5 -desonly -ptype KRB5_NT_PRINCIPAL
Targeting domain controller: w2k3std01.test.int
Using legacy password setting method
Successfully mapped scalix-ual/sca01.test.int to scalix-ual.
Key created.
Output keytab to scalix-ual.keytab:
Keytab version: 0x502
keysize 61 scalix-ual/sca01.test.int@TEST.INT ptype 1 (KRB5_NT_PRINCIPAL) vno 3
etype 0x3 (DES-CBC-MD5) keylength 8 (0xc4eaba894fda2554)
Is it correct?
Note that this is a Windows 2003 Std R2 domain controller and that the AD domain name ("test.int") is the *same* of the "hostname --fqdn" scalix server (test.int)... may these be source of problems?
---
3.
I merged the keytab files and modified krb5.conf:
Code: Select all
# ommergekeys /var/opt/scalix/scalix-ual.keytab
# omkrbconf -r TEST.INT -s scalixdc.test.int
-- I used the CNAME scalixdc in a first test ... but then I tried also with the A record (w2k3std01.test.int), by modifying /etc/krb5.conf ... any issues here?
4.
Tested Authentication with SWA and outlook.... users can login WITHOUT a password.
5.
I modified the 4 files (ual.remote, pop3, omslapdeng, smtpd.auth) under /var/opt/scalix/sys/pam.d/
They contain:
Code: Select all
auth required om_krb5 user_unknown=ignore
auth optional om_auth use_first_pass
account required om_auth
password required om_auth
as indicated in http://www.scalix.com/community/viewtopic.php?t=3154, but it does not work.
That is, users now are not allowed to login, with using their AD password or a blank password.
In the login name I tried user, user@test.int, user@TEST.INT, User Surname.... none worked.
EDIT: another issue: after the mod. to the pam rules (specifically, omslapdeng), the SAC refuses my scalix administrator (it was sxadmin@sca01.test.int).
I copied back the pam rules for omslapdeng and the SCA worked again.
What did I do wrong?

Should I restart scalix services (which ones?) after every modification?
May you elaborate on the whole setup? Is that correct?
Thank you in advance.
Davide DG.