Anonymous_User Absent Member.
Absent Member.
791 views

Append attribute value


Using SSPR 3.2 from IDM 4.5, I am trying to append a value to the
Description attribute after user activation. I tried both Activation
Actions and Post-Activation Actions, but both replace the entire
Description attribute with what I want to append. Is there a way to
change this behavior so that I can keep what's already there?
Thanks
Russ


--
oyarsa
------------------------------------------------------------------------
oyarsa's Profile: https://forums.netiq.com/member.php?userid=193
View this thread: https://forums.netiq.com/showthread.php?t=52788

0 Likes
4 Replies
Knowledge Partner
Knowledge Partner

Re: Append attribute value

oyarsa wrote:

> Using SSPR 3.2 from IDM 4.5, I am trying to append a value to the
> Description attribute after user activation. I tried both Activation
> Actions and Post-Activation Actions, but both replace the entire
> Description attribute with what I want to append. Is there a way to
> change this behavior so that I can keep what's already there?


Seems like the LDAP action is missing an "operation type" selector and always
does a replace. The way to change this would be to open a SR about it or enter
an enhancement request at http://www.novell.com/rms. Both not want you want to
hear, probably.

Workarounds that come to mind would be to set a different attribute that is not
used otherwise. You could then use other tools like IDM or a cron'd shell
script utilizing ldapsearch/ldapmodify to update the Description attribute (and
clear the one initially set, if you wish).
______________________________________________
https://www.is4it.de/identity-access-management
0 Likes
Knowledge Partner
Knowledge Partner

Re: Append attribute value

Lothar Haeger wrote:

> Workarounds that come to mind would be to set a different attribute that is
> not used otherwise. You could then use other tools like IDM or a cron'd shell
> script utilizing ldapsearch/ldapmodify to update the Description attribute
> (and clear the one initially set, if you wish).


Oh, and since SSPR is open source, you could also fix it yourself, of course...
🙂
______________________________________________
https://www.is4it.de/identity-access-management
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Append attribute value

Lothar Haeger wrote:

>
> Oh, and since SSPR is open source, you could also fix it yourself, of
> course... 🙂


Is it 100%? PWM is open source, but aren't there bits in SSPR that are
not in PWM? It used to be just that SSPR was based on a less cutting
edge stable build of PWM. Don't know if that is always the case now.
0 Likes
Knowledge Partner
Knowledge Partner

Re: Append attribute value

Alex McHugh wrote:

> Is it 100%? PWM is open source, but aren't there bits in SSPR that are
> not in PWM? It used to be just that SSPR was based on a less cutting
> edge stable build of PWM. Don't know if that is always the case now.


I asked it's developer Jason Rivard at BrainShare about it and he said SSPR was
just some re-branded build of PWM (which does not necessarily correspond to a
released PWM version, though). Since PWM is GPLv2 licensed all derived work
must be as well and consequently all SSPR JARs contain the compiled and the
source code.
According to GPLv2 SSPR may contain additional, non-derived work licensed
differently, but I've not noticed any additional functionality over what's
available in PWM so far (OSP integration, maybe..?). In fact the early SSPR
releases were actually stripped down versions of PWM.
______________________________________________
https://www.is4it.de/identity-access-management
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.