03.05.2015 Views

IBM WebSphere V5.0 Security - CGISecurity

IBM WebSphere V5.0 Security - CGISecurity

IBM WebSphere V5.0 Security - CGISecurity

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

4. Server ORB calls the request interceptor to allow security to send information<br />

back to the client along with the reply, send_reply().<br />

5. Client ORB calls the request interceptor to allow the client to cleanup and set<br />

the session status as validor invalid, receive_reply().<br />

The SAS protocol supports the establishment of both stateless and stateful<br />

security contexts. Stateless contexts exist only for the duration of the GIOP<br />

request that was used to establish the context. Stateful contexts endure until they<br />

are discarded and can be referenced for use with subsequent requests. The SAS<br />

protocol includes a simple negotiation protocol that defines a<br />

least-common-denominator form of interoperability between implementations<br />

that support only stateless contexts and those that support both stateless and<br />

stateful forms. While the J2EE Specification requires that only stateless mode is<br />

implemented, the Application Server implements both in order to improve the<br />

performance of a multiple message application. This is achieved by invoking the<br />

server request interceptor when the EJB method has completed and sending a<br />

new reply service context to client containing the outcome. This extra step is only<br />

necessary for the first request in the session.<br />

6.3 Configuring the Java client<br />

It is necessary to configure the Java client so that it can access secured<br />

applications. It must be made aware of certain properties, such as the security<br />

settings for the client ORB. The properties are provided in a file called<br />

sas.client.props. The JVM in which the application client will run should be set to<br />

use this property file by adding the directive:<br />

com.ibm.CORBA.ConfigURL=.<br />

So, to start the JVM, enter:<br />

java<br />

-Dcom.ibm.CORBA.ConfigURL=file://properties/sas.client.prop<br />

s com.abc.myJavaApp<br />

where should be replaced with the directory in which the<br />

Application Server, or the <strong>WebSphere</strong> Application Client, was installed, for<br />

example C:\<strong>WebSphere</strong>\AppServer on a Windows machine.<br />

Chapter 6. Securing Java clients 103

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!