Grouper Users - Open Discussion List

[David Langenberg <>]

The replacement for the PSP should be able to do this just fine.

Dave

On Wed, Nov 19, 2014 at 3:12 PM, Jeffrey Crawford <> wrote:

Fair enough, I have to ask though, when you say at present, does that imply there is a desire to get that level of separation?

Jeffrey E. Crawford
ITS Application Administrator (IdM)
831-459-4365

Both pilots and IT professionals require training and currency before charging into clouds!

---------------------------------------

On Wed, Nov 19, 2014 at 1:28 PM, David Langenberg <> wrote:

At present, no, to provision multiple targets you'll need to either go with the hard-coding route.

Dave

On Wed, Nov 19, 2014 at 1:59 PM, Jeffrey Crawford <> wrote:

I'm looking for a way to get a little more psp configuration separation for the LDAP psp. I based my configuration on the work from the example psp-example-grouper-to-openldap-multiple, however I don't see a great way to separate things in ldap.properties configurations like:

edu.internet2.middleware.psp.baseStem
edu.internet2.middleware.psp.structure
edu.internet2.middleware.psp.cnSourceAttributeID

The problem it seems is that the psp-service.xml file can only define one service with the name "psp" that actually works. As such I can only define one psp.AttributeAuthority which can call one psp.AttributeResolver. and that gets the ldap.properties config.

So far what I've had to do is copy and hard code content in the psp-resolver.xml file for the different types of configs since It seems like I can only apply one ldap.properties file to it. Is there a way to separate out ldap.properties files out so I can have two completely independent LDAP provisioning targets?

Jeffrey

​C.
​

Both pilots and IT professionals require training and currency before charging into clouds!

---------------------------------------

--

David Langenberg

Identity & Access Management

The University of Chicago

--

David Langenberg

Identity & Access Management

The University of Chicago