Hi,

On Sunday, 11. September 2005 10:35, Hirmke Michael wrote:
> this seems to be my weekend of unanswered questions :)
>
> I have a few questions regarding Authen::SASL:
>
> 1. Is there any way to find out in a Perl script, what SASL mechanisms
>    are supported in my installation?

What do you mean exactly by "my installation" ?

Currently authen::SASL supports 2 backends:
- Authen::SASL::Cyrus
- Authen::SASL::Perl (i.e. Authen::SASL itself)
The default order in which authen::SASL tries to find backends
is the same as listed above.
Alternatively you can explicitely coose one of the backends
in the 'use' statement. I.e.
        use Authen::SASL qw(Perl)
selects Authen::SASL::Perl.

The mechanisms supproted depend on the backend:
Authen::SASL::Perl supports EXTERNAL, LOGIN, PLAIN, ANONYMOUS, DIGEST-MD5, and 
CRAM-MD5 (each one referenced by its own Perl module and documented).
The menchanisms supported by Authen::SASL::Cyrus should be in the 
documentation of Authen:SASL::Cyrus resp. cyrus-sasl2.

Of course having client support for a mech is only one necessary part.
When you connect to a server the server needs to support SASL as well and the 
mechanisms given in Authen::SASL->new() needs to have a non-emtpy 
intersection with the server mechanisms for the authentication to be able to 
succeed.

> 2. If not - how can I avoid, that Authen::SASL->new dies, if it is
> called
>    without any valid mechansims? I'd prefer the resulting object to be
>    undefined or something like that.

Hmm, Authen::SASL->new() really died ? 
Would you mind to send the code and the error it generated.

> 3. It seems, that $sals->mechanism does not return the actual choosen
>    mechanism - instead it returns the list I gave the constructor.
>    Is this a known bug or am I doing something wrong?

The selection of the mech used for authentication does not happen in the 
client (i.e. Authen::SASL does not decide)
The mach gets selected when the connection is made to the server
and then the server chooses the mech (AFAIK).

hope it helps
Peter
-- 
Peter Marschall
eMail: [EMAIL PROTECTED]

Reply via email to