"Log out" user option for MAS system administrators

Mark - could you email me directly with more details about the problems you are seeing where users are unable to login because old sessions are preventing login

We have not address this requirement directly, but I wanted to highlight that the new active/inactive user state feature delivered in MAS v8.11 can be utilized to achieve something close/equivalent.When you deactivate a user, this has multiple effects / implications:

• A User cannot login if they are inactive

• If already logged in, then when their token next refreshes it will fail and they will be logged out. (By default, the token is refreshed every 30mins.)

• Any action in the UI that requires the authentication token (the JWT that is stored in the cookies when a user logs in) will fail with an unauthorised error because part of the token validation code in the backend now validates that the User the token is associated with is active. With some very specific exceptions, every action in the UI requires a valid token associated with an active user.

The most important point here is that although the user isn’t technically logged out (i.e forced back to the login screen), they are effectively made inert… all API calls issued by the UI to create, retrieve, update, or delete any resource would fail with an unauthorised error because the backend checks that the User is active.

Hello, when was this delivered? We have Maximo Application Suite on Cloud and I can't find this function.

Best regards,

I'd also like to know when and where this option will be available, now that it's "Delivered".

This just changed to "Delivered". Can someone point us to documentation on how it has been implemented?

Hello, in which version this will be included?

Best regards,

Hello, this is a critical feature to manage AppPoints consumption. We understand there is a licensing model change and we like it but IBM needs to enable the tools for customers to properly manage the resources.

We can't rely that users will properly clean browsing cache or log-out every time they use the system. For instance we are in the testing phase and noticed that we have 1 month old active sessions and we know the user have not been using the system in a full-time basics.

Best regards,

Thanks for this good idea.

Being a customer of the MAS Manage (CI), I kindly ask you to consider as well to have the Admin to be able do a logout of one or more end users and block for further login (for a while). Being the Maximo Admin, sometimes I need to be sure specific users can’t login to the application. E.g. when deploying changes to the system and I need to verify before re-opening for end user access.

/Michael, Sund & Bælt

Thanks for your feedback and Ideas. We have a number of user management enhancements we are looking to address in upcoming releases and we expect to cover this requirement also.