I typically run my API apps as admin because I'm doing things like
exporting/importing workflow and such, which requires admin....but yea...any
user should work...:)

  _____  

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Susan Palmer
Sent: Friday, November 14, 2008 9:26 AM
To: [email protected]
Subject: Re: API User Access - Can it be limited?


** 
Carey and LJ,
 
Thanks for the help.  As I look back through my notes from earlier this year
I'm not sure where I got that idea ... lol   
 
It's even better than they can have only Read license.  I can put them in
the general permission group that does have Change permissions but since the
account will have only a Read license I don't have to worry about them
updating existing records.  With the Read license they can submit to the
staging form.  
 
That's much better.
 
Thanks again,
Susan


On Thu, Nov 13, 2008 at 11:26 PM, LJ Longwing <[EMAIL PROTECTED]> wrote:


** 
Susan,
I'm not familiar with the requirement that you are talking about that
requires the user to be an Admin.  From my understanding, any API tool can
use any user that's valid in the system for the function they are trying to
do, and due to the fact that the user tool is nothing more than a vendor
provided api client...I'm wondering where you got that information.  If my
understanding is correct you could have the user account in question be a
read only user account that had permissions only to pull the information it
needs, and create records in the staging table.

  _____  

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Susan Palmer
Sent: Thursday, November 13, 2008 8:22 PM
To: [email protected]
Subject: API User Access - Can it be limited?


** 
Hi Everyone,
 
This will be our first plunge into the world of Remedy API creation.  We
have a portal page through a java application that we're going to let our
external customers submit Help Tickets on.  We'll be using the API to take
the info on that portal page and submit to a staging form in Remedy.  From
there it's all covered with regular filters to create the HT and retrieve
all other required field information to complete the record properly.  The
API will also be retrieving information from various forms for menu type
fields and to show open HTs.  
 
My question is:  I know I have to create a Remedy User account and from what
I've researched I have to give the account admin rights.  That makes me very
nervous.  That means I'll be giving an outside group power within Remedy and
they have a history of over utilizing rights.  Is there a way for me to
limit their 'write' permissions to just that staging form?  I haven't used
subadmin permissions either.  I lead a sheltered life as a one-person shop,
all powerful Remedy Queen.  Could I create a separate permission group with
only that API User in it and give that group change rights on all the fields
on the form.  Then give the form subadmin rights for that group also.  Would
that satisfy the API's requirements?
 
The API will be getting information from several forms, does it require more
than Read rights to obtain the info.  The API will only be submitting to the
one staging form.
 
I appreciate your help.
 
Thanks,
Susan
 
ARS v7.0.1P3  platform, user, admin
Oracle 10g
Windows 2003 server
API - I provided them with the 7.1 API documentation
 
Susan Palmer
Enterprise Remedy Developer and Administrator
ShopperTrak RCT Corporation
200 W Monroe St  11th Floor
Chicago, IL  60606
Office  312-529-5325
Cell     312-502-7687

__Platinum Sponsor: www.rmsportal.com <http://www.rmsportal.com/>  ARSlist:
"Where the Answers Are" html___ 
__Platinum Sponsor: www.rmsportal.com <http://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"

Reply via email to