IBM WebSphere V5.0 Security - CGISecurity

Once the client has been authenticated, the appropriate remote method will beinvoked.The client runtime determines which method to use to collect the user details bychecking the com.ibm.CORBA.loginSource property in the sas.client.props file.The default value is prompt which causes the window to appear. However,changing this to stdin will cause the client runtime to request the details on thecommand line.If the wrong user details are entered four times, the Application Server will throwa javax.naming.NoPermissionException exception with acom.ibm.websphere.security.auth.AuthenticationFailedException as thereason.6.6 Java thin application clientThe thin application client phrase refers to the Java client that is not runningwithin the J2EE client container. It is a stand-alone Java application, thatimplements EJB clients connecting to an EJB container of WebSphereApplication Server.The clients usually run on a client machine separated from the application server.In order to connect to the server you have to provide the connection informationfor the EJB client, including the server name and the port number (the defaultport number for WebSphere Application Server V5 is 2809).There are certain configurations you have to set for the JVM in order to operatein a secure environment. These settings are the following:►►Djava.security.auth.login.config - tells the JVM where to find the JAAS loginconfiguration file. For example:Djava.security.auth.login.config=file:properties/wsjaas_client.confDcom.ibm.CORBA.ConfigURL - points to the file containing the client SASsettings for IBM SAS and CSIv2. For example:Dcom.ibm.CORBA.ConfigURL=file:properties/sas.client.propsThere are also libraries which you have to include in your classpath whenrunning a Java thin client in a secure environment. You will need the following .jarfiles from the WebSphere library at /libs:► wssec.jar► namingclient.jar► lmproxy.jarChapter 6. Securing Java clients 123