> On Tue, 2003-08-12 at 11:47, Michael Fair wrote:
>> I've never used pam for virtual domains but the general idea
>> is that the user provides the fully qualified [EMAIL PROTECTED]
>> as their userid. SASL splits that up into a "realm" and a
>> user so in terms of SASL, creating the user looks so
On Tue, 2003-08-12 at 11:47, Michael Fair wrote:
> I've never used pam for virtual domains but the general idea
> is that the user provides the fully qualified [EMAIL PROTECTED]
> as their userid. SASL splits that up into a "realm" and a
> user so in terms of SASL, creating the user looks somethin
I've never used pam for virtual domains but the general idea
is that the user provides the fully qualified [EMAIL PROTECTED]
as their userid. SASL splits that up into a "realm" and a
user so in terms of SASL, creating the user looks something
like this:
saslpasswd -c -U domain.dom userid
I really
On Tue, 2003-08-12 at 14:18, Simon Matter wrote:
> > On Tue, 2003-08-12 at 11:47, Michael Fair wrote:
> >> I've never used pam for virtual domains but the general idea
> >> is that the user provides the fully qualified [EMAIL PROTECTED]
> >> as their userid. SASL splits that up into a "realm" and
I'm having a lot of difficulty wrapping my mind around authentication for a
virtual domain configuration. I would like to use PAM for auth, but I don't see
how to get around the '@' in the usernames. I see nothing in the docs that
address how to setup auth for virtual domain support.
Do any of you
