I agree it it is either workflow or a BMC provided option baked into the product.
On Fri, Sep 6, 2013 at 1:17 PM, Joe D'Souza <jdso...@shyle.net> wrote: > ** > > Na.. those were beautiful! I wish I get to see them at least once again > before I don’t have to travel to Alaska no more.. My next trip is scheduled > to be my last..**** > > ** ** > > I like the DNS spoofing idea from Tauf – only that these days most IT > employees are smart enough to realize what’s happening, and if they have > access to edit their own host file, could revert it back.**** > > ** ** > > I really don’t think there is a fool proof non workflow mechanism that > can’t get in legal trouble to do what needs to be done. Workflow seems to > be the safest bet.**** > > ** ** > > Joe**** > > ** ** > ------------------------------ > > *From:* Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] *On Behalf Of *Jason Miller > *Sent:* Friday, September 06, 2013 4:11 PM > *To:* arslist@ARSLIST.ORG > *Subject:* Re: Prevent MT Login**** > > ** ** > > ** **** > > Wow Joe, wow 8-) I wonder if there is some radiation coming off the > Aurora and soaking into your brain...**** > > ** ** > > On Fri, Sep 6, 2013 at 1:02 PM, Joe D'Souza <jdso...@shyle.net> wrote:**** > > PERFORM-APPLICATION-LOGOUT from the home page or any other page that the > user might have access too if the $CLIEMT-TYPE$ = 9.. > > Why would you have such a requirement though when the future versions does > not support access through the native User client? > > This is a workflow mechanism - it will be impossible to do it with a non > workflow mechanism. Unless you are free to employ a security guard to stand > besides that employee and beat the crap out of him if he tries to log in > through the mid tier.. That would be a non workflow mechanism :) - > primitive > - but will work.. :) > > Joe**** > > > -----Original Message----- > From: Action Request System discussion list(ARSList) > [mailto:arslist@ARSLIST.ORG] On Behalf Of SUBSCRIBE arslist Aditya Sharma > Sent: Friday, September 06, 2013 3:59 PM > To: arslist@ARSLIST.ORG > Subject: Prevent MT Login > > > Hi Listers, > > I have a requirement to prevent a particular user to be able login through > mid tier but same user should be able to login to client tools. Has anyone > implemented such requirement? What can be the best way to achieve this? > > Specifically looking for a non-workflow mechanism. > > Regards, > Aditya**** > > Sent from my BlackBerryR smartphone from !DEA**** > > > > _______________________________________________________________________________ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > "Where the Answers Are, and have been for 20 years"**** > > ** ** > > _ARSlist: "Where the Answers Are" and have been for 20 years_ **** > _ARSlist: "Where the Answers Are" and have been for 20 years_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
