Hi,

I received the following requirements from my customer.

The solution must at least offer the possibility of disconnecting the user after a period of inactivity. 

The period of inactivity within a user session must be configurable.

The solution offers the possibility of warning the user that his session is about to expire.

Is there any way to have it done.

Thanks for your support.

------------------------------
Abed Hammami
------------------------------



#MaximoAnywhere
#AssetandFacilitiesManagement
#Maximo

I wanted to do this too. Unfortunately, I couldn't find a way, despite significant effort.

Here are some related posts:

1. How to make Anywhere automatically timeout?
2. Alternative timeout mechanism? (since Anywhere NEVER signs itself out)
3. Instead of timing out, we settled on giving the user a way to determine who is signed in:
  - Indicate what user is currently signed in to Anywhere?
  - Final solution in this post (combined with the solution for: How to determine what URL user is connected to?)
4. If you are using LDAP authentication:
  - Unfortunately, I don't think the LTPA token mechanism can be used to timeout Anywhere.

(Bear in mind that I'm NOT an expert. So I could be wrong about some of that stuff.)

I should mention:

At first, we thought we really did want a timeout mechanism -- since our tablets are shared between users.

However, ultimately, our users seem to like the fact that Anywhere never times out. If they have a record open that is only half-finished, they won't ever lose it, even if they leave it like that for a few hours (or even a few days).

It doesn't' change the fact that from a security and data integrity perspective, the lack of timeout isn't good. But from a user experience perspective, the "loose ship" is pretty handy.


#Maximo
#MaximoAnywhere
#AssetandFacilitiesManagement

If you are using an identity provider (Token based that does have a time out form the server side) the software can be customized to provide for a re-auth of the token.  I will have to check with Development to see if this was made part of the product when using SSO or other IDP authentication.  while this does not provide the spec idci use case you have talked about, I can imagine that when your token is facing a time-out that you can program Anywhere to throw a dialog box.

I would not recommend a separate mechanism to kick the user out of the application.  Forcing a user to log in when they are offline (for which the tool is designed to operate)  makes for a difficult user experience.  We designed it this way for a market-based reason.  However if you are using an IDP for authentication then the IDP takes care of the situation for you.  

Hope this helps.

------------------------------
Bradley K. Downing , MBA
IBM Certified Adv. Deployment Prof. Maximo v7.6.1
IBM
Bakersfield CA
------------------------------