Session Management
The formerly used headers
x-login.userx-login.externaluserx-login.externaluser.fullnamex-credential-login.runonbehalfof
are obsolete, but are still supported for compatibility reasons.
With content web service (CWS) calls, exactly one EBIS client license is occupied for the calling technical user on the server side which, unless a query parameter named logout=true is transmitted, will be reused for other calls by the same technical user.
x-login-user
Example:
|
In this way, a separate server session opens for S.Sample and is reused for all future calls (transmitting the same header) until an explicit logout is performed via the query parameter, or until Server Session Timeout takes effect.
If a value is used here that has already been used in a previous request, the session of the previous request is reused. If this parameter is not specified or a new value is specified, a new session is created on the server.
x-login-externaluser
Example:
|
A non-system user can be logged in via the CWS using a technical user.
When logging in via the CWS, the additional data of the "real" user account can be transferred with this parameter.
Prerequisite: The external system account property must be active in the technical user account.
x-login-externaluser-fullname
Example:
|
Here it is possible to specify a first and last name for the non-system user.
The prerequisite is that the corresponding system field exists in the document schema. This parameter only applies to schema-based documents.
x-credential-login-runonbehalfof
CWS supports the "trusted user" concept of EBIS.
This parameter can be used to specify the archive user on whose behalf the called archive operation is to be performed.
The prerequisite is that the technical user specified for authentication has been assigned the trusted_server role.