Hi vikas nayal
1815509 - New enhancement "License Abuse Prevention" in SAP Business One 9.0
Symptom
Currently, SAP Business One license could be abused in several ways:
1. Different persons login to the same company (taking advantage the dual login feature).
2. Different persons login to different companies using the same user code (but different password).
3. In hosted environment, several customers can connect remotely to different companies with the same Business One user and password. The abuse is done by the hosting provider, who maps windows user to SQL DB and give the same Business One user and password to all his Business One customers.
These scenarios impact significantly the Business One license structure. Therefore, since SAP Business One 9.0 PL01, a new enhancement is implemented with the name "License Abuse Prevention".
Please note this enhancement will replace both "dual login" feature in earlier versions and "logon limitation" in 8.82 version.
Solution
Now the license manager will verify the user name together with the 3 parameters: workstation IP, windows user and windows session ID.
The purpose of this solution is to ensure that one user can only connect to SAP Business One via one single session. Once the user logins via a second session, the first session will be locked. A session can be either a new windows login on the same machine (with the same windows user or a different windows user) or a login from a second station.
DETAIL:
For one Business One user, it can login successfully if all of 3 parameters are same. It means from one session, one user can login to unlimited number of companies and/or unlimited logins to the same company.
However, if any of these parameters are changed when the same user logins, the system will treat it as a second session, then the first session will be locked.
EXAMPLE:
SAP Business One user (let's call it UserA), when it logins to Business One alone for the first time, the system already records its parameters:
a. Workstation IP
b. Windows User
c. Windows session ID
Now for the following operations:
1. UserA opens a new Business One in the same workstation and logins to another company database: It is an existing Business One user name. All of 3 parameters are not changed. Login successful.
2. UserB login to Business One via the same workstation: It is a new Business One user name. Login successful.
3. UserA login to Business One via another workstation with the same Windows user account: It is an existing Business One user name, but parameter a and c are changed. Login successful but the previous session will be locked.
4. UserA login to Business One via the remote connection to the same workstation with the same Windows user account: It is an existing Business One user name, but parameter c is changed. Login successful but the previous session will be locked.
LOCKED:
As mentioned above, when another session of your logged user is connected, your current user session will be locked for all the companies, like when pressing File->Lock Screen menu in Business One.
System message will pop up:
Your session has been locked because another session was started using the same user ID. To continue, exit or lock the other session.
EXCEPTION:
User "manager" is exceptional and it can login via two sessions at the same time. This is for supporting implementation scenario, where usually SAP consultants use "manager" account without interrupting or taking other users' license.
Logon Limitations:
You can log on to SAP Business One client multiple times in a given MS Windows session using the same user ID.
If you try to log on to SAP Business One client in another MS Windows session using the same user ID at the same time, all SAP Business One clients running on the first MS windows session with that user ID will be locked, and it will be impossible to log on to SAP Business One client from any additional MS Windows session with the same user ID.
Regards
Kennedy