I'll take a stab at this ... I believe what the user is looking for is a way to ensure a user has logged out of Remedy, or possible a way to actually force a logout of a user through workflow.
As understand it the only way to actually force the logout of a user is to use the Admin tool and clear the user from "Managed User Licenses" list. This can only be done once every few hours (or something like that ). I do not believe there is a call (API, JScript) you can make that allows you to specify which user to logout. The next way to log a user out is to run PERFORM-ACTION-EXIT-APP on the web which will log the user out. However, when to do this is on the web is the tricky part. If you do this on window close, and the user has many Remedy web windows open, they will lose their sessions on those windows. If your web application runs in only one window then this could be a solution. Note: some an interesting test I performed on Firefox using tabs. Open a control panel form. Double click a record from a table field on that form which opens a record in a new tab. Go back to control panel and double click another table record which opens another record in a new tab. Go back to the control panel and click a logout button which does a PERFORM-ACTION-EXIT-APP. The two new tabs that had opened get closed and the user is sent to a logout.jsp page. This only seems to work if the new tabs are opened from a Remedy form. No, we do not have any custom code that knows which tabs are opened. Frank On Tue, Mar 18, 2008 at 7:16 AM, Carey Matthew Black <[EMAIL PROTECTED]> wrote: > Prashant, > > The LogoutServlet is the right way to go. It however will not violate > the BMC license agreement for how licenses are to be used. ( There are > restrictions on the number of IP addresses, how long the license/token > will be held to a give IP, and other conditions that can not be > circumvented without breaking the EULA.) > > So far I think your description of how you are using ARS is vague, and > the exact nature of the problem has also not been described. > > Can you quantify/qualify what the actual problem is that your having > after the "session is not closed"? > Can you explain what you mean by "transparent login"? ( Is a generic > ARS user account being used or is the individuals personal credentials > being used?) > Are you using a load balancer design in your portal that might be > changing IP addresses when it is talking to ARS for the user? > > I can see a possibility that any or all of the above would lead to > complications in using ARS connectivity from a portal. > > Also please know that the exact version of ARS (server and client) may > also play into this discussion due to bugs and the alike in the > specific ARS API's your using. ( So knowing that kind of detail can > also be helpful to the discussion.) > > -- > 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 Tue, Mar 18, 2008 at 3:39 AM, Prashant Patil <[EMAIL PROTECTED]> wrote: > > ** Hi Carey, > > > > Using LogoutServlet I did the following test. Our portal has this scenario > > as explained below for performing remedy logout process. > > > > Browser 1 (Main portal window) - Click on remedy link which will perform > > transparent login and show remedy form to user. > > > > Browser 2 (child portal window) - User clicks on portal logout link. Portal > > logout process steps are : > > a) Perform logout for remedy user (by calling logout servlet) > > b) logout user from portal. > > > > Result : Remedy session will still remain active for that user. > > > > How can i be sure that user logout has been performed for that user. > > > > > > Thanks > > Prashant > > > > > > > > > > > > On Mon, Mar 17, 2008 at 2:30 PM, Carey Matthew Black <[EMAIL PROTECTED]> > > wrote: > > > > > Prashant, > > > > > > This is the wrong URL. http://<server>/arsys/shared/logout.jsp > > > That jsp is just the "ok, we are done with the logout process... now > > > what do we show the user?" output file. > > > > > > You need to make a call to the LogoutServlet. You can pass it a goto > > > value of the logout.jsp, or any other file you want to. > > > > > > See BasicGuide-630.2006.05.09.pdf pages 452 and 453 for details. > > > > > > http://<server>/arsys/servlet/LogoutServlet > > > > > > Keep in mind that this may not totally free the users session, but it > > > will at least have a shot at not requiring a one hour timeout. > > > > > > -- > > > Carey Matthew Black > > > Remedy Skilled Professional (RSP) > > > ARS = Action Request System(Remedy) > > > > > > Love, then teach > > > Solution = People + Process + Tools > > > Fast, Accurate, Cheap.... Pick two. > > > > > > > > > > __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" > _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
