vaultuser Absent Member.
Absent Member.
199 views

Documentation of Loop Driver...?


Hello friends,

Where I can find the documentation of Loop Driver for Novell Identity
Manager 4.0.1 and examples of the functionality and configuration of
this driver.

thanks


--
vaultuser
------------------------------------------------------------------------
vaultuser's Profile: http://forums.novell.com/member.php?userid=103574
View this thread: http://forums.novell.com/showthread.php?t=453931

Labels (1)
0 Likes
6 Replies
Knowledge Partner
Knowledge Partner

Re: Documentation of Loop Driver...?

On 3/26/2012 5:46 PM, vaultuser wrote:
>
> Hello friends,
>
> Where I can find the documentation of Loop Driver for Novell Identity
> Manager 4.0.1 and examples of the functionality and configuration of
> this driver.


Not much to write about it.

It does not do much. An event comes down teh Sub channle out of eDir.
Then it loops back and comes out the Pub channel back to eDir.

Everything else is up to you.

By default, not much happens.

Probably examples will teach you more. Look at how Lothar uses it in
his very public Password Notification Driver:

http://www.novell.com/communities/node/2277/idm-35-password-notification-service-driver
http://www.brummelhook.com/dirxml.html

I discuss a way to use the SUb-Event of any driver, but loopback/Null
drivers are nice for this, as what I call Toolkit rules:

http://www.novell.com/communities/node/6308/toolkit-rules-identity-manager-part-1
http://www.novell.com/communities/node/6310/toolkit-rules-identity-manager-part-2
http://www.novell.com/communities/node/6316/toolkit-rules-identity-manager-part-3
http://www.novell.com/communities/node/6440/toolkit-rules-identity-manager-part-4
http://www.novell.com/communities/node/6441/example-use-toolkit-rule-identity-manager
http://www.novell.com/communities/node/6514/another-toolkit-rule-use-example-bad-attribute-value-cleanup




0 Likes
vaultuser Absent Member.
Absent Member.

Re: Documentation of Loop Driver...?


Geoffc friend,
The idea of ​​using the BACK LOOP driver is sent as input
an XML NDS directory data through the channel subscription for a JAVA
class receives these parameters to perform some action.

I hope any suggestions, Thanks


--
vaultuser
------------------------------------------------------------------------
vaultuser's Profile: http://forums.novell.com/member.php?userid=103574
View this thread: http://forums.novell.com/showthread.php?t=453931

0 Likes
Knowledge Partner
Knowledge Partner

Re: Documentation of Loop Driver...?

On 3/26/2012 7:06 PM, vaultuser wrote:
>
> Geoffc friend,
> The idea of​​using the BACK LOOP driver is sent as input
> an XML NDS directory data through the channel subscription for a JAVA
> class receives these parameters to perform some action.
>
> I hope any suggestions, Thanks


That does not make much sense to me, but I think you are suggesting a
way to build your own driver from a base or skeleton or sample?




0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Documentation of Loop Driver...?

0 Likes
vaultuser Absent Member.
Absent Member.

Re: Documentation of Loop Driver...?


Friend,

HTTP Not Found


--
vaultuser
------------------------------------------------------------------------
vaultuser's Profile: http://forums.novell.com/member.php?userid=103574
View this thread: http://forums.novell.com/showthread.php?t=453931

0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: Documentation of Loop Driver...?

On 3/27/12 8:46 AM, vaultuser wrote:
>
> Friend,
>
> HTTP Not Found
>
>

Make sure you add the .html that got inadvertantly wrapped to the next
line and therefore didn't get included in the link.

--
Shon
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.