Using Security in CORBA Applications
|
|
Logs in to the BEA Tuxedo domain. The correct input parameters depend on the authentication level.
HRESULT logon(
[in] BSTR user_name,
[in] BSTR client_name,
[in] BSTR system_password,
[in] BSTR user_password,
[in] VARIANT user_data,
[in,out,optional] VARIANT* exceptionInfo,
[out,retval] Security_AuthenticationStatus*
returnValue);
Function logon(user_name As String, client_name As String,
system_password As String, user_password As String,
user_data, [exceptionInfo]) As Security_AuthenticationStatus
For remote CORBA client applications, this method authenticates the client application via the IIOP Listener/Handler so that the remote client application can access a BEA Tuxedo domain. This method is functionally equivalent to DITobj_PrincipalAuthenticator.authenticate, but the parameters are oriented to security.
The BEA Tuxedo username. This parameter is required for TOBJ_NOAUTH, TOBJ_SYSAUTH, and TOBJ_APPAUTH authentication levels.
Application-specific data (custom authentication service). This parameter is required for the TOBJ_APPAUTH authentication level.
Note: If user_name, client_name, or system_password is NULL or empty, or exceeds 30 characters, the subsequent authenticate method invocation raises the CORBA::BAD_PARAM exception.
Note: If the authorization level is TOBJ_APPAUTH, only one of user_password or user_data may be supplied.
The following table describes the valid return values.
|
The authentication failed, or the client application was already authenticated and did not call one of the following methods: |
|
|
|