[prev in list] [next in list] [prev in thread] [next in thread] 

List:       novell
Subject:    Re: PAM, LDAP (eDir ?)
From:       Randy Grein <randygrein () comcast ! net>
Date:       2006-05-30 4:25:40
Message-ID: 46F9C44F-7A7E-4A5D-9A67-9712B9A79427 () comcast ! net
[Download RAW message or body]

So why not use the webmanagement widget in eDir? Y'know, the one that  
allows creation and management of linux users in eDIR.
Randy Grein, Master CNE, CCNA

On May 27, 2006, at 10:53 AM, joea wrote:

>> . . .
>>
>>> An app still can communicate with an auth-source directly,  
>>> without using
>>> PAM, even if PAM exists on that system. A Mailserver with Postfix  
>>> using
>>> the SASL-framework (and there the saslauthd) for example can  
>>> communicate
>>> directly with (among others) shadow, LDAP, Kerberos and PAM. And  
>>> if PAM
>>> is configured so and you chossing this, the communication is then
>>> possible via PAM->shadow, PAM->LDAP, PAM->Kerberos and so on.  
>>> Using PAM
>>> would then be one more step.
>>
>> Ok, well you were right, now the confusion is perfect.   Are you  
>> saying
>> that all these
>> methods can exist (and work??) at the same time?  If so, does "the
>> system" try each
>> in some sequence?  If two users are defined identically, what  
>> happens?
>>  . . .
>
> It appears that is is not possible to create a local LDAP user when  
> one of the same
> name already exists in shadow.  At least in YAST, it complains and  
> will not allow it.
>
> Now, I was astonished to learn the reverse is also true, adduser  
> will return message
> that the user already exists, if it was created using LDAP, yet  
> does not show in shadow.
>
> There is more to this magick than we mortals can see.  The wizzards  
> have been busy.
>
> joea
> _______________________________________________
> Novell mailing list
> Novell@netlab1.usu.edu
> http://netlab1.usu.edu/mailman/listinfo/novell

_______________________________________________
Novell mailing list
Novell@netlab1.usu.edu
http://netlab1.usu.edu/mailman/listinfo/novell
[prev in list] [next in list] [prev in thread] [next in thread]