tree 52e48fbdd2a77c2c6ba583a2d41750e265336a77
parent 40e4f380d645c6bbe6bd8050e501203798a0c488
author Ed Tanous <edtanous@google.com> 1659485274 -0700
committer Ed Tanous <ed@tanous.net> 1665165968 +0000

Move ClientID parameter out of OEM

In 2022.2, Redfish added support for the Context parameter on the
Session Resource.  This parameter has the same function that the
OemSession.ClientId field served.  This commit moves all the existing
ClientId code to produce Context as well.

Functionally, this has one important difference, in that Context in
Redfish is optionally provided by the user, which means we need to omit
it if not given by the user.  The old implementation left it set to
empty string ("").

Because of this, a few minor interfaces need to change to use
std::optional.  Existing uses of clientId are moved to using
value_or("") to keep the same behavior as before.

Tested:
curl --insecure -X POST -d "{\"UserName\": \"root\", \"Password\":
\"0penBmc\"}" https://192.168.7.2/redfish/v1/SessionService/Sessions

Returns a Session object with no Context key present

curl --insecure -X POST -d "{\"UserName\": \"root\", \"Password\":
\"0penBmc\", \"Context\": \"Foobar\"}"
https://192.168.7.2/redfish/v1/SessionService/Sessions

Returns a Session object with:
"Context": "Foobar"

Subsequent Gets of /redfish/v1/SessionService/Sessions/<sid>
return the same session objects, both with and without Context.

Signed-off-by: Ed Tanous <edtanous@google.com>
Change-Id: I4df358623f93f3e6cb659e99970ad909cefebc62