IBM WebSphere V5.0 Security - CGISecurity

►►►sas.jarecutils.jardirectory where the implfactory.properties file residesAs an additional library do not forget to add the EJB client code, home andremote classes of the EJB to your classpath.In your thin Java application, you can leave the authentication challenge to theWebSphere code; or you can program your own login module with your owncallback implementation.The libraries included in the classpath contain the necessary code for the clientto perform the authentication for WebSphere. The default source for login is theGUI login panel; you can change it to something else in the SAS clientconfiguration file.For more information about the programmatic login for thin Java clients, refer to8.7.2, “Client-side login with JAAS” on page 209.Unzip the itsobankThinClient.zip file to a directory of your choice. You will find thesource and compiled classes in the directory. There are also supportingproperties files and key files for the secure connection.In order to run the client, use the following syntax:runclient server_name server_port [login]The server_name and the server_port define the remote application serverlocation for the remote EJB connection. The optional login parameter tells theapplication to use programmatic login instead of the built in login mechanism.The following example runs the application using WebSphere’s login challenge:runclient appsrv01 28096.7 Where to find more informationFor more information on the security aspects of J2EE, see the followingdocuments:► The Java 2 Platform Specification v1.3 at►http://java.sun.com/j2ee/docs.htmlThe Object Management Group (OMG) specification about CSIv2 athttp://www.omg.org/technology/documents/formal/omg_security.htm#CSIv2124 IBM WebSphere V5.0 Security Handbook