>>> On 13/03/2008 at 16:27, in message <[log in to unmask]>,
Colin Farrow <[log in to unmask]> wrote:
> Bruce,
>
> This is what I do. Similar to Andy's in Dundee but determine the
> staff student part from the container the person object resides in.
> Basically the dn has ... ,ou=staff, ... or ... ,ou=student, ...
>
> <!-- generate eduPersonAffiliation -->
> ScriptletAttributeDefinition
> id="urn:mace:dir:attribute-def:eduPersonAffiliation">
> <DataConnectorDependency requires="directory"/>
> <Scriptlet>
> Attributes
> attributes=dependencies.getConnectorResolution("directory");
> Attribute dn = attributes.get("dn");
> s = dn.get();
Smart! I wasn't sure if you could get dn as a an attribute that could be read like that - I'll be making use of that.
This kind of configuration snippet is what we should put into a configuration sample repository on one of the central federation sites. I've learned so much (almost everything I know!) from seeing other peoples resolver configurations, we need a central repository that people can go to for "ideas".
Cheers
Andy
--
*********
Andy Swiffin
Senior Network Specialist, Corporate Information systems
Information & Communications Services (ICS)
University of Dundee, Computing Centre, Park Place, Dundee, DD1 4HN
Direct: 01382 388000 (Service Desk)
Visit our website at: www.dundee.ac.uk/ics
*********
|