tree 18ef3519b50a6f08ff88d0db6f47c6ecb6f026b2
parent 08bdcc71e5804db9b5c35361e8456e636d258b04
author Manojkiran Eda <manojkiran.eda@gmail.com> 1590131177 +0530
committer ManojKiran Eda <manojkiran.eda@gmail.com> 1592367795 +0000

Lock Management : Add Support for Mutltiple HMC's

- The Lock Structure already had the HMC-ID field which
  stores the corresponding unique Identifier that tells
  us which HMC has acquired the Lock.

- Now, that the Know you client functionality is up, we can
  leverage the clientId field in the bmcweb session store to
  fill the lock structure with the corresponding hmc identifier.

NOTE : Also note that a Single HMC can have mutliple session that
can acquire different locks, So when the ownership of any lock is
tied up to its cliendId as well as the SessionId.

- Release Lock call on any Transaction ID can only be successful if
  the transactionID of corresponding lock has the complete owner-ship
  as per the NOTE mentioned above.

Tested By:

1. CREATE Session with Client ID as mentioned below:

'{"UserName":"root", "Password":"0penBmc", "Oem":{"OpenBMC" : {"ClientID":<unique id>}}}'

2. Make sure the GetLockList of the above session populates the CliendID field
   as per data mentioned in the login Request.

3. Release Lock on transaction ID with same HMC-ID but with different
   sessionID's should be successful only when both the HMC-ID(mapped to
   X-Auth tokens in the session store) & Session ID(from the session store)
   of the ReleaseLock request matches with the ownwership of the lock pertaining
   to the transaction ID in the request.

Signed-off-by: Manojkiran Eda <manojkiran.eda@gmail.com>
Change-Id: I60161bea6007782a397fc60f19d44c2211d4cf7f