Using Security in CORBA Applications
DITobj_PrincipalAuthenticator.get_auth_type
Synopsis
Gets the type of authentication expected by the BEA Tuxedo domain.
MIDL Mapping
HRESULT get_auth_type(
[in, out, optional] VARIANT* exceptionInfo,
[out, retval] Tobj_AuthType* returnValue);
Automation Mapping
Function get_auth_type([exceptionInfo]) As Tobj_AuthType
Argument
exceptioninfo
An optional input argument that allows the client application to get additional exception data if an error occurs.
Description
This method returns the type of authentication expected by the BEA Tuxedo domain.
Note: This method raises CORBA::BAD_INV_ORDER
if it is called with an invalid SecurityCurrent object.
Returned Values
A reference to the Tobj_AuthType
enumeration. The following table describes the valid return values.
Return Value
|
Meaning
|
TOBJ_NOAUTH
|
No authentication is needed; however, the client application can still authenticate itself by specifying a username and a client application name. No password is required.
To specify this level of security, specify the NONE value for the SECURITY parameter in the RESOURCES section of the UBBCONFIG file.
|
TOBJ_SYSAUTH
|
The client application must authenticate itself to the BEA Tuxedo domain, and must specify a username, a name, and a password for the client application.
To specify this level of security, specify the APP_PW value for the SECURITY parameter in the RESOURCES section of the UBBCONFIG file.
|
TOBJ_APPAUTH
|
The client application must provide proof material that authenticates the client application to the BEA Tuxedo domain.The proof material may be a password or a digital certificate.
To specify this level of security, specify the USER_AUTH value for the SECURITY parameter in the RESOURCES section of the UBBCONFIG file.
|