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


  • jgrieshop;248822 Wrote:
    > 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


    Thanks for the info. I will figure out a work around for now and put in
    an enhancement request.


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

Reply

  • jgrieshop;248822 Wrote:
    > 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


    Thanks for the info. I will figure out a work around for now and put in
    an enhancement request.


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

Children
  • On 9/18/2014 1:55 PM, stuartbyrnes wrote:
    >
    > jgrieshop;248822 Wrote:
    >> 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

    >
    > Thanks for the info. I will figure out a work around for now and put in
    > an enhancement request.


    Do let us know if you do figure out a way.

    Perhaps the developers could consider the case of 'reading' the
    attribute on demand, versus 'eventing' on the change of the attribute.
    If that would be of value. You could poll for it, if that was important
    as a workaround?