Or if the app is going to keep its own connection table as mentioned it doesn't need to be in Remedy. The app does a direct db query instead of going though the the AR api to maintain it's connection info. It might be better for the custom app to not completely depend on Remedy so some functionality can be provided if Remedy is down; even if it is to just log the failed attempts while Remedy is down.
There is still the issue of possibly needing an admin account to use the api to read truly active sessions system-wide and check if the person is already logged in. That could be done server-side with an admin account also maintaining records in the custom app's session table. Probably have some flag if the session is direct AR or via custom app and then logic to do the appropriate thing. Of course using this to allow multiple users to use a single account is a violation of the license agreement but if it is truly to allow the same person to use their own account it *might* be ok (check with the proper legal/BMC representatives to verify). Jason On Dec 21, 2013 9:52 AM, "LJ LongWing" <[email protected]> wrote: > ** > > Yes, you can certainly do that, but it would require logging on with a > different user to perform the check, then log on as the actual user of > available, and this user would likely need to be an admin to avoid the > problem being faced > On Dec 21, 2013 10:48 AM, "Brent Goodman" <[email protected]> wrote: > >> ** >> To check if a user is already connected, you just need to pole the user >> list if connected sessions. The server maintains this in memory and you can >> use an API call to retrieve the list and compare. >> >> From all the questions an answers, were still only getting part of the >> picture, but I think your trying to get away with multiple users using a >> limited number of accounts, hence the need for override. >> >> I have a number of .net apps that are used by multiple of people and have >> never needed to worry about collisions from another computer. >> >> Some of my apps have built in times that will actually log themselves out >> when not used after a period of time. >> >> If your an admin, one could also have a control table in remedy so when >> your app logs in, it records itself and the user. >> >> This way you can always know who's logged in and which app version and >> name it is. In my table I have set it up so I can block certain versions >> from logging in. >> >> >> Sent from my iPhone >> >> On Dec 21, 2013, at 7:12 AM, LJ LongWing <[email protected]> wrote: >> >> ** >> >> I'm not sure, but you may find that you need to burn two licenses, one >> for their desktop and one for their mobile. >> On Dec 21, 2013 8:09 AM, "Sweety" <[email protected]> wrote: >> >>> If yes then below are my questions; >>> >>> 1) How can I check if a user is already connected from another machine >>> 2) After that how can I override the user - I think, I got the answer >>> for this from Misi >>> >>> >>> _______________________________________________________________________________ >>> 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_ > > _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"
