Sent you an email but maybe. Thanks.
I am actually just trying to search for the lack of sAS attributes. I
am not sure what you mean by Role Expiration. All I want to do is search
the users once a week for those attributes. If they don't exist; send an
email to the user. Or am I over simplifying it?
> And email me offline and i can send you a sample of the Package I built
> for Roles expiration. (I have not tested it yet, it is really
> My fullname, no spaces or periods at gmail.com
> On 5/1/2012 10:00 AM, Geoffrey Carman wrote:
> > I had just sent Lothar a message asking him for a Package to add
> > for Roles expiration.
> > So I figured, why am I wasting his time, I can do this myself just
> > fast. So I built a package to add support for Role expiration and
> > it to him.
> > Having read through the driver and how it works, I think it should
> > reasonable to do what you want.
> > Sub Channel, Event and Command I think you can ignore, since you do
> > wish to email when these sASxxxx attributes change, you can ignore
> > channels entirely.
> > I think it should all be Pub-Event.
> > What i did was easy. Do you have the Packaged version of his driver,
> > just the IDM 3.6.1 version as a single config file? Packaged version
> > actually easier, since he broke up functionality for Packages and
> thus I
> > copied all the Account Expires stuff, and modified it. So it was a
> > of cake.
> > I think you basically can look at the PwNoftifyAcct rules, and
> > copying them and using them for your work.
> > There are the following rules:
> > PwnoftifyAcct-pub-etp-CheckAccounts
> > PwnoftifyAcct-pub-etp-Reformatvalues is of no interest to you.
> > PwnoftifyAcct-pub-etp-SendAccountNotifications
> > So really just two places. Copy and modify to do what you want.
> > I made my own GCV object since Roles have a bunch of different
> > etc vs Users.
> >> Looks like it is a combination of four sASxxxxx attributes. I have
> >> rule set to search for the combination of the four and send an email
> >> they are not available. My problem now is where to put the rule. All
> >> password expiration rules in the driver seem to have a combination
> >> policies and rules on both the publisher and subscriber. I don't
> >> if it is as simple as check accounts for the missing attributes and
> >> an email to the user, or if I have to create other rules to set a
> >> of variables and such?
> >> geoffc;2188550 Wrote:
> >>> On 4/11/2012 3:26 PM, jpoisson wrote:
> >>>> Hi all, I am trying to find a way to have a driver, (possibly the
> >>>> SRV_PWNotify) check for users that haven't filled out their
> >>> Forgotten
> >>>> Password Profile for the User App and send them an email.
> >>>> check for the sASLoginSecret and sASLoginSecretKey attributes to
> >>>> present and if not, send an email to the user requesting that
> >>> file
> >>>> out their profile. Has anyone done this? Is it recommended to NOT
> >>> use
> >>>> the SRV_PWNotify?
> >>> Seems like a trivial change to the Password Notifier driver.
> >>> However, Simple password would also fill those attrs I think. You
> >>> MIGHT
> >>> be able to look at the values to figure out what is in it...
jpoisson's Profile: http://forums.novell.com/member.php?userid=14684
View this thread: http://forums.novell.com/showthread.php?t=454540