|
|
 |
| e-docs > Tuxedo > Using Security in CORBA Applications > Automation Security Reference |
|
Using Security in CORBA Applications
|
DITobj_PrincipalAuthenticator.build_auth_data
Synopsis
Creates authentication data and attributes for use by DITobj_PrincipalAuthenticator.authenticate.
MIDL Mapping
HRESULT build_auth_data(
[in] BSTR user_name,
[in] BSTR client_name,
[in] BSTR system_password,
[in] BSTR user_password,
[in] VARIANT user_data,
[out] VARIANT* auth_data,
[out] VARIANT* privileges,
[in,out,optional] VARIANT* exceptionInfo);
Automation Mapping
Sub build_auth_data(user_name As String, client_name As String,
system_password As String, user_password As String, user_data,
auth_data, privileges, [exceptionInfo])
Arguments
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: The user_password and user_data parameters are mutually exclusive, depending on the requirements of the authentication service used in the configuration of the BEA Tuxedo domain. The default authentication service expects a user password. A customized authentication service may require user data. If both user_password and user_data are specified, the subsequent authentication call raises the CORBA::BAD_PARAM exception.
Description
This method is a helper function that creates authentication data and attributes to be used by DITobj_PrincipalAuthenticator.authenticate.
Note: This method raises CORBA::BAD_INV_ORDER if it is called with an invalid SecurityCurrent object.
Return Values
None.
|
|
|
|
||
 |
|
|
 |
 |
 |
|
||
