Maybe you could do something with the MQTT Web client component; with this component you can communicate between multiple browser clients.

Kind regards,

Matthias

Hi Mihaela,

You can use this - retrict user login on second browser 

  Maintain a flag in database; upon every login/out update the flag. For instance, upon every authentication request  you can reject the login request if the flag is already true.

Thanks

Rahul Sahu

Hi Mihaela,

You'll have to manage the User sessions yourself since I don't think Outsystems exposes them: you'd need an Entity with something like:

 - a UserId, to identify who owns that session;

 - a LastDateOfInteraction, to know when was the last time the session was used;

 - something to identify the origin of the session: an IP address, possibly;

And with those three things, you'd be able to identify if a user starts any "concurrent" sessions. The part of your implementation that will vary is going to depend on how quickly you need to react to that second login: if you want the user to be immediately logged out, you'd need to implement something with a server push (like Matthias' suggestion). If it's okay to only log out the user when he goes back and attempts to interact with the application on his first session, then you could have an action that checks for concurrent sessions and logout the user there.

You could register the user login and broadcast a message by MQTT to logout other sessions. In every screen there is a MQTT listener that response on this message by logging out.

Hope this helps,

Matthias

Why would you try to make something like this?

If 2 people are working with the same account perhaps?
But wouldn't that infuriate the users when they get kicked out of the application? 

In order to achieve this you would have to invalidate the session if you receive a new login and as stated before, you can't really do this in Outsystems, if you had more control over your server you could probably narrow down what session to destroy so that the other "browser" gets a forced log-out.

Within Outsystems you will have to create an extension of the user entity, where you hold a certain value to check against (this could be a random hash which you compare with some user-session value). But it will require a few extra checks since Outsystems considers this user as logged in.

Again asking why would you want this? Isn't there another way to reach your objective?

Hi Mihaela,

There is solution in Outsystems to invalidate user session. 

1) Create an extension entity containing following attributes,
- UserId (as identifier)
- SessionGUID

2) Add Session variable, SessionGUID

3) In OnSessionStart action, update SessionGUID session variable and also update the SessionGUID in an entity against UserId.

4) In OnBeginWebRequest action, check if SessionGUID of the session and from entity is different then call logout action.

Hope this helps.

Regards,
Sagar