Skip to Content.
Sympa Menu

grouper-dev - Re: ldappc-ng status, bending spml ?

Subject: Grouper Developers Forum

List archive

Re: ldappc-ng status, bending spml ?


Chronological Thread 
  • From: Tom Zeller <>
  • To: Grouper Dev <>
  • Subject: Re: ldappc-ng status, bending spml ?
  • Date: Mon, 22 Mar 2010 13:47:32 -0500
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type; b=QSwzxMShPFbi73ALCte0ltOjQBzWZkmnAJewqTOsEwa8WxYhl+pTJEoHmh/eOQZuD0 cWo3tqBTWccirdBetRApDVVnamhjXOmzBZ9ajyaT1emNutgSkEkgrLSu+5teOSxj1e9V eSz8N+NJqRGMhsh1+jbiSPs46n5AOEOYjHAF0=

> So, there are a couple of options. One is to handle the MUST member
> attribute in a subclass of the spml-to-ldap-connector
> (LdapTargetProvider, ala OpenLdapTargetProvider extends
> LdapTargetProvider). I was thinking of avoiding this kind of
> customization in the spml-to-ldap-connector, since it would be sort of
> hidden away. Another option is for the PSP to handle this (like ldappc
> does now). The second option would be bending spml, in that when
> ReturnData is set to "data", we'll still return an empty reference
> which should really only be present when ReturnData is set to
> "everything". We could define a custom ReturnData value, for example,
> "required", but this might be too much for a first release.
>
> Thoughts on bending spml ?

For the archives, I opted for extending the spml-to-ldap-connector to
handle the groupOfNames objectclass which requires (MUST) the member
attribute. The spml spec says that <capabilityData> elements
(references) MUST NOT be returned if returnData="data".

So, we will behave properly, as far as spml is concerned.



Archive powered by MHonArc 2.6.16.

Top of Page