George, I think your going about that a bit backwards....
You want to build a "web application" that lets the end user authentication to ARS. (No impersonation needed. Just a username/password.) IF (and I can not say that any more clearly .... IF ) your trying to build a "web application" that would not rely on ARS user Float/Fixed licensing (but make multiple people look like 'Login Name'= "bob" to ARS), then I think you might be breaking their license agreement. -- 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 2/19/07, George Jungle <[EMAIL PROTECTED]> wrote:
** Howdy list, This is the first time that I'm having to look into the use of the .net Remedy API and was wondering if anyone can help me. Basically due to company standards we are NOT able to use the OOB mid tier for one particular organisational group. What we're doing is developing some custom .net pages for the Requesters within this group to log in and create/update dockets. What's the resource for finding out how to 'impersonate' the requester logging the case such that it makes them the submitter (and calls upon the "Submitter locked mode" functionality)? I've started to trawl through the Dev AR Apps basic and advanced guides but any help (or potential gotchas) from those that have tried this would be appreciated. Thanks. george. __20060125_______________________This posting was submitted with HTML in it___
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
