Specifying Credentials in EJB Clients

Depending on the type of client, you may need to specify security credentials before your client can access an EJB or other JNDI-accessible resource.

Table 22-1 classifies EJB clients by where they are deployed relative to the target enterprise JavaBeans they invoke. Where you deploy the client relative to its target enterprise JavaBeans determines whether or not you must specify security credentials.

Table 22-1 Client Security Credential Requirements

Client Type	Relationship to Target EJB	Set Credentials?
Any client	Client and target EJB are collocated	No
Any client	Client and target EJB are deployed in the same application	No
Any client	Target EJB deployed in an application that is designated as the client's parent^Foot 1	No
Any client	Client and target EJB are not collocated, not deployed in the same application, and target EJB application is not client's parent^Footref 1.	Yes

^Footnote 1See the Oracle Containers for J2EE Developer's Guide for more information on how to set the parent of an application.

When you access EJBs in a remote container (that is, if the client and target EJB are not collocated, not deployed in the same application, and the target EJB application is not the client's parent), you must pass valid credentials to the remote container. How your client passes its credentials depends on the type of client:

EJB Client: pass credentials within the InitialContext, which is created to look up the remote EJBs (see "Specifying Credentials in the Initial Context").
Stand-alone Java Client: define credentials in the jndi.properties file deployed with the EAR file (see "Specifying Credentials in JNDI Properties").
Servlet or JSP Client: pass credentials within the InitialContext, which is created to look up the remote EJBs (see "Specifying Credentials in the Initial Context").

For more information, see:

Specifying Credentials in JNDI Properties

To specify credentials in a jndi.properties file:

Create or modify an existing jndi.properties file.

Configure the appropriate credentials in the jndi.properties file as Example 22-6 shows.

For property names, see the field definitions in javax.naming.Context.

Example 22-5 Specifying Credentials in JNDI Properties

java.naming.security.principal=POMGR
java.naming.security.credentials=welcome
java.naming.factory.initial=
    oracle.j2ee.server.ApplicationClientInitialContextFactory
java.naming.provider.url=opmn:ormi://opmnhost:6004:oc4j_inst1/ejbsamples

Ensure that the jndi.properties file is on the client's classpath.
Use the JNDI API in your client to look up the JNDI-accessible resource as Example 22-6 shows.
Example 22-6 Looking Up a JNDI-Accessible Resource
```
Context ic = new InitialContext();
CustomerHome = (CustomerHome)ic.lookup("java:comp/env/purchaseOrderBean"); 
```

At runtime, JNDI uses ClassLoader method getResources to locate all application resource files named jndi.properties in the classpath. In doing so, it will use the JNDI properties you set in Example 22-6 to access the purchaseOrderBean.

For more information, see "Setting JNDI Properties with the JNDI Properties File".

Specifying Credentials in the Initial Context

To specify credentials in the initial context you use to look up JNDI-accessible resources:

Create a HashTable and populate it with the required properties using javax.naming.Context fields as keys and String objects as values as Example 22-7 shows.

Example 22-7 Specifying Credentials in the Initial Context

Hashtable env = new Hashtable(); 
env.put(Context.SECURITY_PRINCIPAL, "POMGR"); 
env.put(Context.SECURITY_CREDENTIALS, "welcome"); 
env.put("java.naming.factory.initial",
        "oracle.j2ee.server.ApplicationClientInitialContextFactory"); 
env.put("java.naming.provider.url",
        "opmn:ormi://opmnhost:6004:oc4j_inst1/ejbsamples");

When you instantiate the initial context, pass the HashTable into the initial context constructor as Example 22-8 shows.
Example 22-8 Looking Up a JNDI-Accessible Resource
```
Context ic = new InitialContext (env); 
CustomerHome = (CustomerHome) ic.lookup ("java:comp/env/purchaseOrderBean");
```

For more information, see: