PAPI Archivos

The PAPI authentication and authorization framework

PAPI@LISTSERV.REDIRIS.ES

Opciones: Vista Forum

Use Monospaced Font
Por defecto enseñar Text Part
Esconda cabeceras de correo

Mensaje: [<< Primero] [< Prev] [Siguiente >] [Último >>]
Tema: [<< Primero] [< Prev] [Siguiente >] [Último >>]
Autor: [<< Primero] [< Prev] [Siguiente >] [Último >>]

Print Responder
Received:
by LISTSERV.REDIRIS.ES (LISTSERV-TCP/IP release 14.5) with spool id 6049404 for [log in para visualizar]; Sat, 16 May 2009 20:59:12 +0200 from abel.rediris.es (abel.rediris.es [130.206.24.2]) by listserv.rediris.es (Postfix) with ESMTP id 2AA135C201 for <[log in para visualizar]>; Sat, 16 May 2009 20:59:12 +0200 (CEST) from bismuto.unileon.es ([193.146.96.36]) by abel.rediris.es with ESMTP; 16 May 2009 20:59:15 +0200 from [10.18.8.66] ([10.18.8.66]) by bismuto.unileon.es (@(#)Sendmail version 8.13.3 - Revision 1.005 - 15 November 2007/8.13.3) with ESMTP id n4GIxB5A003370 for <[log in para visualizar]>; Sat, 16 May 2009 20:59:11 +0200 (METDST)
Content-Type:
text/plain; charset=ISO-8859-1
X-Enigmail-Version:
0.95.7
References:
Date:
Sat, 16 May 2009 20:59:07 +0200
Reply-To:
The PAPI authentication and authorization framework <[log in para visualizar]>
Message-ID:
Content-Transfer-Encoding:
7bit
X-Original-To:
X-IronPort-Anti-Spam-Filtered:
true
Sender:
The PAPI authentication and authorization framework <[log in para visualizar]>
Subject:
Received-SPF:
Pass identity=mailfrom; client-ip=193.146.96.36; receiver=lsv.rediris.es; envelope-from="[log in para visualizar]"; x-sender="[log in para visualizar]"; x-conformance=spf_only; x-record-type="v=spf1" Pass identity=helo; client-ip=193.146.96.36; receiver=lsv.rediris.es; envelope-from="[log in para visualizar]"; x-sender="[log in para visualizar]"; x-conformance=spf_only; x-record-type="v=spf1"
Delivered-To:
Emisor:
"Roberto S. G." <[log in para visualizar]>
User-Agent:
Thunderbird 2.0.0.21 (Windows/20090302)
In-Reply-To:
X-IronPort-Anti-Spam-Result:
AqcBAA6qDkrBkmAkmWdsb2JhbACXVAEBAQEBCAsKBxG4eoQBBQ
MIME-Version:
1.0
Parts/Attachments:
text/plain (23 lines)
Hi,

I've been using this "strange" ldap conf in AuthServer.cf for a while
(with also a little modification in LDAPAuth.pm):
   $$cfg{authenticationHook} = \&PAPI::LDAPAuth::VerifyUser;
   $$cfg{credentialHook} = \&PAPI::BasicAuth::DefCredentials;
   $$cfg{attrRequestHook} = \&PAPI::BasicAuth::DefAttributes;
so I could authenticate ldap users, without including PAPI objectclasses
in my ldap schema.

Now, I'd need to use two different assertions depending on the site
accessed... Is it possible to use $$cfg{basicAuthDB} at the same time,
in order to generate different defAssertions depending on site?

I'd check it myself, but actually I have v1.4.0, and assertions in DB
were included in 1.4.1 (afaik). I tried to use the LDAP and DB, but the
latter seems to be ignored...
As I'm in the process of adding papi to my schema, I would only upgrade
to 1.4.1 before that, if using the db is possible...
maybe this doesn't worth the time... not sure.

greets

ATOM RSS1 RSS2