Hi,
On Monday, 12. September 2005 11:09, Hirmke Michael wrote:
> > What do you mean exactly by "my installation" ?
>
> my scripts have to run on about 150.000 computers. Normally they should
> have the same software and same versions installed - but who knows 8-<
> So I'd like to check within the script, what backends are installed and
> if they provide the mechanisms my scripts depend on.
Wow 150.000 !!!
May I ask for the company/institution you create this installation ?
> > 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.
>
> Yes, ok. That already works for me.
>
> > > 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.
>
> The code looks like this:
>
> $oSASL = Authen::SASL->new(
> mechanism => "GSSAPI",
> callback => {
> user => ' ',
> },
> );
>
> Error message is:
>
> No SASL mechanism found
> at /usr/lib/perl5/site_perl/5.8.1/Authen/SASL.pm line 73
>
> This is on a Linux machine with Perl 5.8.1 and Authen::SASL 2.09 and
> no Authen::SASL::Cyrus installed.
> As soon as I installed Authen::Cyrus::SASL everything worked as
> expected.
GSSAPI is currently only supported by Authen::SASL::Cyrus.
> But this is exactly the problem, that can happen on any of my clients.
You may use eval { ... } around the above piece of code to catch the error.
Peter
--
Peter Marschall
eMail: [EMAIL PROTECTED]
