VB, If you use the ARS server ar.conf setting: " Disable-Client-Operation "
Then you can establish ARS permission groups that "limit" what clients the users can use by time of day. Well, except for the FACT ( I know it can be done ) that the ARS API allows the client to "tell the server" which client it actually is. So an API program can "say" it is the UserTool. But I am not sure how hard it would be to write an ODBC driver for ARS that changes it's "Client Type" value. (See John Sundberg's post for other details on this part of the question.) I am disappointed that the "API" does not have built in identifiers (like public/private key identification features) so that the compiled API that BMC publishes for us can only be identified by the ARS server as one specific client type. But I guess BMC does not see "Client Type" as a valid security access control. (Well, maybe some day they can... So who is going to write up that RFE? :) ) -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. On Wed, Apr 23, 2008 at 6:42 PM, Easter, David <[EMAIL PROTECTED]> wrote: > ** > > Perhaps the AR_CLIENT_TYPE is what you're looking for: > > > AR_CLIENT_TYPE_* (integer) > > An integer value for the client type. For more information, see > AR_CLIENT_TYPE_* in the ar.h file. > You could then use workflow to limit a user's actions based on their client > type - in this case the User Tool. > > > > > > -David J. Easter > Sr. Product Manager, Solution Strategy and Development > BMC Software, Inc. > > The opinions, statements, and/or suggested courses of action expressed in > this E-mail do not necessarily reflect those of BMC Software, Inc. My > voluntary participation in this forum is not intended to convey a role as a > spokesperson, liaison or public relations representative for BMC Software, > Inc. > > > > ________________________________ > From: Action Request System discussion list(ARSList) > [mailto:[EMAIL PROTECTED] On Behalf Of Viswanathan Balakumar > Sent: Wednesday, April 23, 2008 2:01 PM > To: [email protected] > Subject: Locking the Remedy Login only to User Tool > > > > ** > > > HI, > > > > Is there a way to make some remedy logins (either by name / group > permission) to access ONLY User tool and Can not access Remedy data through > any other way like Remedy ODBC \ APIs. > > > > For Information security reasons, we want some logins to be used only with > in the User tool and throw an error when used in Crystal Reports \ Remedy > ODBC \ APIs. > > > > May be like using APIs \ monitoring the Logins \ any other way … > > > > Any related information will be helpful. > > > > Thanks, > > VB > > __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > html___ > > __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" > html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
