Shibboleth Developers

[Etan Weintraub <>]

I guess I'm one of the lucky ones then, as I manage both the IdP and the LDAP 
servers....

-Etan E. Weintraub
Team Leader - Enterprise Authentication
Senior Systems Engineer - Enterprise Directory
IT@Johns
 Hopkins Johns Hopkins at Mt. Washington
5801 Smith Ave.
Suite 3110B
Baltimore, MD 21209
Phone: 410-735-7945
E-mail: 


-----Original Message-----
From: Chad La Joie 
[mailto:]
 
Sent: Wednesday, June 09, 2010 1:22 PM
To: 

Subject: Re: [Shib-Dev] [IdPv3] Consent Engine Work

You'll be able to write any persistence plugin you want, but I've always 
be very reticent to provide plugins that would persist to LDAP because 
people seems to have a lot more issues with extending their LDAP schemas 
than with setting up a new DB table.

On 6/9/10 12:52 PM, Etan Weintraub wrote:
> Or will it be possible to use the same user store (i.e. LDAP) to store this 
> information?
>
> -Etan E. Weintraub
> Team Leader - Enterprise Authentication
> Senior Systems Engineer - Enterprise Directory
> IT@Johns
>  Hopkins Johns Hopkins at Mt. Washington
> 5801 Smith Ave.
> Suite 3110B
> Baltimore, MD 21209
> Phone: 410-735-7945
> E-mail: 
> 
>
>
> -----Original Message-----
> From: Scott Cantor 
> [mailto:]
> Sent: Wednesday, June 09, 2010 12:45 PM
> To: 
> 
> Subject: RE: [Shib-Dev] [IdPv3] Consent Engine Work
>
>> Features I am considering but not yet committed:
>>
>> - A uApprove DB ->  IdP consent engine migration script.  It's possible
>> that the consent engine may track enough new/differing data that this
>> wouldn't possible.  I won't know for a while.
>
> Is the consent from the user tracked in a database or in the client
> (cookies)?
>
> I'm really asking, will this be deployable without a database?
>
> -- Scott
>
>
>

-- 
Chad La Joie
http://itumi.biz
trusted identities, delivered