Feature to limit and control the use of the same user ID for multiple concurrent sessions in OSP/UA

Idea ID 2804802

Feature to limit and control the use of the same user ID for multiple concurrent sessions in OSP/UA

Hi,

If user logins into another session/browser, system invalidates the first session. 

Proposed high-level process, (excerpt from https://stackoverflow.com/questions/39881194/allow-one-concurrent-user-per-login-with-jwt

  1. A user logs in, you store the Refresh Token in a DB
  2. The Access Token expires. Before you issue a new Access Token from your Refresh Token, make the standard check that the account is still OK, but also compare the Refresh Token to the one in your DB. Make sure they match.
  3. A second user logs in with the same account. Store the issues Refresh Token in the DB and over write the old Refresh Token. (One stored Refresh Token per account.)
  4. First users Access Token expires again. This time there is another Refresh Token in the DB, and no new Access Token is issued for that user.

 

Lets discuss options. Thanks.

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.