Timeout Does Not Require Logging Back In RQM v4.0
Hello, Currently when a user is logged into the application but is not active for 120 minutes, the user will loose the floating license. When the license is lost the Web app doesn't require the user to log back in all the time (sometimes it works, sometimes not). This makes the user think that they are still active and can continue working on artifacts, but nothing is actually saved because they have no license. This causes users to loose all of their work until they log back in. Any idea how to enforce login if the users licenses has timed out. Thanks, Kyle |
One answer
The user licenses are managed by JTS not QM so I am not sure how licenses time out works, but I would guess login from re-authentication from a session time out would take care of the license. Anyway, any service call to the server will trigger the re-authentication of a timed out session. A simple action is the refresh action of a page (not the browser refresh) such as the dashboard or an artifact table list view. Refresh the browser will trigger the re-authentication as well but you will lose the opened artifact pages. Note that the opened artifact pages are in the browser cache so navigating among them after the sesion timed out will not trigger the re-authentication.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.