Skip to Content.
Sympa Menu

grouper-users - Re: [grouper-users] PSP Ldap provisioning

Subject: Grouper Users - Open Discussion List

List archive

Re: [grouper-users] PSP Ldap provisioning

Chronological Thread 
  • From: Jeffrey Crawford <>
  • To: David Langenberg <>
  • Cc: Gouper Users List <>
  • Subject: Re: [grouper-users] PSP Ldap provisioning
  • Date: Wed, 19 Nov 2014 14:12:02 -0800

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)

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.


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 configurations like:


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 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 file to it. Is there a way to separate out files out so I can have two completely independent LDAP provisioning targets?


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

David Langenberg
Identity & Access Management
The University of Chicago

Archive powered by MHonArc 2.6.16.

Top of Page