17.1 The LoginInfoManager class
- Description
-
Provides security authentication by using the user name and password specified for a J2EE server.
The following describes the J2EE servers responsible for security authentication.
-
When the ejbserver.security.service.url property is specified:
J2EE servers connect to the CORBA naming service specified by the ejbserver.security.service.url property. If one of the servers has the same name as that specified by the ejbserver.serverName property, the J2EE server with that name is responsible for security authentication.
Specify the ejbserver.security.service.url property when security authentication involves using a J2EE server that is not connected to the CORBA naming service specified by the java.naming.provider.url property.
-
When the ejbserver.security.service.url property is not specified:
J2EE servers connect to the CORBA naming service specified by the java.naming.provider.url property. If one of the servers has the same name as that specified by the ejbserver.serverName property, the J2EE server with that name is responsible for security authentication.
In a load balancing configuration that uses JNDI round-robin search or CTM linkage functionality, there will be two or more J2EE servers that can provide security authentication. When using this configuration, you need to configure the same user name and the same role for all of the J2EE servers and then select one J2EE server for security authentication.
For details about the properties, see 12. Files Used in Java Applications in the uCosminexus Application Server Definition Reference Guide. For details about how to implement security in an EJB client application, see 3.6 Implementing security in an EJB client application, in the uCosminexus Application Server EJB Container Functionality Guide.
The package name of the LoginInfoManager class is com.hitachi.software.ejb.security.base.authentication.
-
- Methods
-
Method name
Functionality
Obtains the LoginInfoManager object.
Logs into a J2EE server.
Logs out of a J2EE server.
- Remarks
-
When using the methods of the LoginInfoManager class, observe the following precautions:
-
We recommend issuing the methods of the LoginInfoManager class from an EJB client application. If you issue them from within a JSP, servlet, or EJB, information configured with the RunAs functionality is deleted for each request.
-
Make sure that you issue the logout method after calling a J2EE server by issuing the login method.
-
Do not issue the login and logout methods as nested methods. If you repeatedly issue the login method without issuing the logout method, information specified with the first login method is overwritten by the following login method.
-
- Organization of this section