PAPI Archivos

The PAPI authentication and authorization framework

PAPI@LISTSERV.REDIRIS.ES

Opciones: Vista Forum

Use Monospaced Font
Por defecto enseñar Text Part
Mostrar todas las cabeceras de correo

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

Print Responder
Subject:
Emisor:
"Roberto S. G." <[log in para visualizar]>
Reply To:
The PAPI authentication and authorization framework <[log in para visualizar]>
Fecha:
Sat, 16 May 2009 20:59:07 +0200
Content-Type:
text/plain
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