I5osdrv: adding attributes to the publisher channel


I have built quite a few drivers over the years using DirXML (IDM). I
have been recently tasked with attaching our identity vault to our main
frame. The issue I have is in finding any documentation on how to add
attributes to the publisher channel on the mainframe. Any direction
would be greatly appreciated. An example would be even better.

I am specifically wanting to get out intruder attempts and last login.


--
stuartbyrnes
------------------------------------------------------------------------
stuartbyrnes's Profile: https://forums.netiq.com/member.php?userid=1312
View this thread: https://forums.netiq.com/showthread.php?t=51760

Parents

  • stuartbyrnes;248740 Wrote:
    > I have built quite a few drivers over the years using DirXML (IDM). I
    > have been recently tasked with attaching our identity vault to our main
    > frame. The issue I have is in finding any documentation on how to add
    > attributes to the publisher channel on the mainframe. Any direction
    > would be greatly appreciated. An example would be even better.
    >
    > I am specifically wanting to get out intruder attempts and last login.


    Hi,

    The i5os Driver leverages the QIDM_QSY_CHG_PROFILE exit point to capture
    i5os Profile changes for the Publisher channel. Unfortunately, the
    driver's implementation has a hard-coded list of attributes that it
    listens for, and Last Login and Intruder Attempts are not in that list.
    The list was chosen for attributes that can be synchronized
    bidirectionally. There wouldn't be any scripts that you could modify to
    plug-in to this process and the changelog functionality does not have a
    public interface.

    I would recommend you open an enhancement request at bugzilla.novell.com
    and request additional attributes be added to the Exit implementation.

    Thanks,
    -Jeremy


    --
    jgrieshop
    ------------------------------------------------------------------------
    jgrieshop's Profile: https://forums.netiq.com/member.php?userid=483
    View this thread: https://forums.netiq.com/showthread.php?t=51760

  • On 9/17/14, 9:57 PM, jgrieshop wrote:
    >
    > stuartbyrnes;248740 Wrote:
    >> I have built quite a few drivers over the years using DirXML (IDM). I
    >> have been recently tasked with attaching our identity vault to our main
    >> frame. The issue I have is in finding any documentation on how to add
    >> attributes to the publisher channel on the mainframe. Any direction
    >> would be greatly appreciated. An example would be even better.
    >>
    >> I am specifically wanting to get out intruder attempts and last login.

    >
    > Hi,
    >
    > The i5os Driver leverages the QIDM_QSY_CHG_PROFILE exit point to capture
    > i5os Profile changes for the Publisher channel. Unfortunately, the
    > driver's implementation has a hard-coded list of attributes that it
    > listens for, and Last Login and Intruder Attempts are not in that list.
    > The list was chosen for attributes that can be synchronized
    > bidirectionally. There wouldn't be any scripts that you could modify to
    > plug-in to this process and the changelog functionality does not have a
    > public interface.
    >
    > I would recommend you open an enhancement request at bugzilla.novell.com
    > and request additional attributes be added to the Exit implementation.
    >
    > Thanks,
    > -Jeremy


    For enhancement requests please use https://www.novell.com/rms

    Casper

Reply
  • On 9/17/14, 9:57 PM, jgrieshop wrote:
    >
    > stuartbyrnes;248740 Wrote:
    >> I have built quite a few drivers over the years using DirXML (IDM). I
    >> have been recently tasked with attaching our identity vault to our main
    >> frame. The issue I have is in finding any documentation on how to add
    >> attributes to the publisher channel on the mainframe. Any direction
    >> would be greatly appreciated. An example would be even better.
    >>
    >> I am specifically wanting to get out intruder attempts and last login.

    >
    > Hi,
    >
    > The i5os Driver leverages the QIDM_QSY_CHG_PROFILE exit point to capture
    > i5os Profile changes for the Publisher channel. Unfortunately, the
    > driver's implementation has a hard-coded list of attributes that it
    > listens for, and Last Login and Intruder Attempts are not in that list.
    > The list was chosen for attributes that can be synchronized
    > bidirectionally. There wouldn't be any scripts that you could modify to
    > plug-in to this process and the changelog functionality does not have a
    > public interface.
    >
    > I would recommend you open an enhancement request at bugzilla.novell.com
    > and request additional attributes be added to the Exit implementation.
    >
    > Thanks,
    > -Jeremy


    For enhancement requests please use https://www.novell.com/rms

    Casper

Children
No Data