Skip to Content.
Sympa Menu

grouper-users - Re: [grouper-users] PSPNG and user-defined attributes

Subject: Grouper Users - Open Discussion List

List archive

Re: [grouper-users] PSPNG and user-defined attributes


Chronological Thread 
  • From: Michael R Gettes <>
  • To: Paul Engle <>
  • Cc:
  • Subject: Re: [grouper-users] PSPNG and user-defined attributes
  • Date: Thu, 16 Feb 2017 15:21:46 -0500
  • Ironport-phdr: 9a23:bdiv2BKvdbWi6KpTVNmcpTZWNBhigK39O0sv0rFitYgRLPjxwZ3uMQTl6Ol3ixeRBMOAuq8C07ad6vu7EUU7or+5+EgYd5JNUxJXwe43pCcHRPC/NEvgMfTxZDY7FskRHHVs/nW8LFQHUJ2mPw6arXK99yMdFQviPgRpOOv1BpTSj8Oq3Oyu5pHfeQtFiT69bL9oMBm7ogrdutQYjIZsN6081gbHrnxUdupM2GhmP0iTnxHy5sex+J5s7SFdsO8/+sBDTKv3Yb02QaRXAzo6PW814tbrtQTYQguU+nQcSGQWnQFWDAXD8Rr3Q43+sir+tup6xSmaIcj7Rq06VDi+86tmTgLjhTwZPDAl7m7Yls1wjLpaoB2/oRx/35XUa5yROPZnY6/RYc8WSW9HU81MVSJOH5m8YpMTAOUOIOhWr4vyqVUBoxW9CwmiGuThxyRUhn/v2K02z+QhHR3E0QEmAtkAsG7UrNLwNKoKVu61zbXHzTXZYPxI3Tf29ZTGeQ0gr/6SQbJwbdTeyVIyHA7Ci1WQs4PlMj2J2ukWq2ib9PdgWfixhGE6tgF8uz6izdovhInRno8Z107I+CZjzIooONG1S1R3bcOrHZZRrS2WKoV7T8IkTmp1oig10KcGtoS+fCUSyJQo2Rrfa/uffoiU+BLvSvidITFliH54Yr2znQy98VO+xe3gTMW0yE1KrjdfntbSq38NygTf6smBSvRj4keswSuD2x7Q5+1ePEw4iKnWJ4Q8zrM/l5cfq1nPEyH3lUnuia+ZbEQk+uym6+T9ZbXmo4eRN4puigHxPKkihteyAfwjMggTRWSU5/mz1KD78U3jXLpKluE2krXesJ3CKsQbvKm5AxJN0ok98RazFiqm0M8GknkdN1JIYxaHj4nyO1HSO/D0E+2zg1WqkDd32f/GJLvhDYvRLnTdirvuY6ty61MPgDY0mOhW+pYcJ7cOJP+7Dlf8stPcAzcjMge5hevrFYMu+JkZXDeqA6SZOa7W+WXAye8zP+SXLNsQojmmc9A9/OOogHMkzwxONZK11IcaPSjrVs9tJF+UND+12o8M

Have tried something like ${ldapUser.getStringValue(“ATTRNAME”)} where
ATTRNAME is the name of the LDAP attribute? Make sure ATTRNAME is also
in the userSearchAttrbiutes list. I haven’t tested this yet but based on some
other stuff done I think this should work. You could do
ou=${ldapUser.getStringValue(“ATTRNAME”)}
I’d be interested in your results.

/mrg

> On Feb 16, 2017, at 11:34 AM, Paul Engle
> <>
> wrote:
>
> All,
>
> I'm finally making some headway on trying to port our provisioning from
> psp to pspng in preparation for the move to 2.3.0. I've got a pretty
> good feel for how things work in the new config, but I'm hitting a wall.
>
> The scenario: We have groups with user-defined attributes on them. What
> I would like is to have the value of that attribute be populated as an
> LDAP attribute on the members' LDAP entries. But I'm having trouble
> figuring out the magic to use for the provisionedAttributeValueFormat
> property that will access a user-defined group attribute instead of the
> built-ins, like ${group.name}. Has anyone done anything similar and can
> offer any pointers?
>
> -paul
>
> --
> Paul Engle
> Office of Information Technology
>
> 713-348-4702




Archive powered by MHonArc 2.6.19.

Top of Page