These are the variables described below:
|
*USER
*USER represents the User ID with which the Visual LANSA application (x_run) was started. If running a function through LANSA SuperServer, *USER represents the User ID used to connect to the server. If running in a Web Environment, *USER stores the LANSA User ID. Mappings between the User ID used to logon to the web session and LANSA User ID's are created through the Web Administrator.
*USER_AUDIT
*USER_AUDIT represents the user that has been set by an executing application using the Built-In Function SET_SESSION_VALUE. It may be used where the current user does not give sufficient differentiations, such as in web jobs where all user jobs run under the default web user profiles.
*USER_AUTHENTICATED
*USER_AUTHENTICATED represents the User ID which has been used to log on to the operating system and which has been authenticated by the selected authentication protocol (such as Kerberos). If running a function through LANSA SuperServer, *USER_AUTHENTICATED represents the User ID used to connect to the server. The authenticated name is the fully qualified name which includes the User ID and the domain/workgroup/machine name. For example, JohnCitizen@mydomain.com.au, JohnCitizen@Johnspc.
In LANSA SuperServer mode, if the User ID is defined both as a local user and a domain user, the local user will be used for authentication.
In the web runtime environment, *USER_AUTHENTICATED represents the User ID used to log on to the web session.
Please refer to *WEBUSER for more details.
Examples:
|
|
|
|
*WEBUSER represents the User ID used to log on to the web session. If Integrated Windows Authentication is specified, the User ID used to log on to the operating system is used for the web session. Otherwise the User ID specified when the session is started is used. The User ID will be truncated to the length of *WEBUSER.
*WEBUSER is the first ten bytes of the *USER_AUTHENTICATED value.
Examples:
With the following User Registration settings:
|
|
|
|
|
