Pros and cons of various Consent storage methods
Mark.McCoy at utsa.edu
Wed May 1 11:19:25 EDT 2019
This is the first I'm hearing about an LDAP storage service implementation. I can't find documentation on that anywhere. Can you point me in the right direction?
OIT Manager, Platform Application Services
Office of Information Technology
The University of Texas at San Antonio
From: users <users-bounces at shibboleth.net> on behalf of Cantor, Scott <cantor.2 at osu.edu>
Sent: Friday, April 26, 2019 09:53
To: Shib Users
Subject: Re: Pros and cons of various Consent storage methods
On 4/26/19, 10:33 AM, "users on behalf of Mark McCoy" <users-bounces at shibboleth.net on behalf of Mark.McCoy at utsa.edu> wrote:
> Have there been any thoughts around adding a write-back capability to the LDAP attribute store so that the consent
> records could be stored in an LDAP in a single multivalued attribute?
There's already an LDAP storage service implementation, have at it.
The advantage of the database use case with consent is that it's not important. The worst case with an error is you ask again. That's very different than using a database for identifiers or data.
For Consortium Member technical support, see https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwiki.shibboleth.net%2Fconfluence%2Fx%2FcoFAAg&data=02%7C01%7Cmark.mccoy%40utsa.edu%7Cf90c1ef284364d0cf16408d6ca56f098%7C3a228dfbc64744cb88357b20617fc906%7C0%7C0%7C636918872092970413&sdata=ISEWuqE5A4oiDZ%2BdAUl8NrLdIAipisTZ4Ocp1GKOKM4%3D&reserved=0
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the users