Fix (APAR): WAS_Security_08-15-2003_4.0.6-4.0.5-4.0.4_AEs_cumulative_Fix Status: Fix Release: 4.0.6,4.0.5,4.0.4 Operating System: All Supersedes Fixes: WAS_Security_09-13-2002_4.0.4-4.0.3_AEs_cumulative_eFix, WAS_Security_10-07-2002_4.0.4-4.0.3_AEs_cumulative_eFix, WAS_Security_10-31-2002_4.0.4-4.0.3_AEs_cumulative_eFix, WAS_Security_11-19-2002_4.0.4-4.0.3-4.0.2_AEs_cumulative_eFix, WAS_Security_01-06-2003_4.0.5-4.0.4_AEs_cumulative_eFix, WAS_Security_03-17-2003_4.0.5-4.0.4-4.0.3_AEs_cumulative_Fix, WAS_Security_05-16-2003_4.0.5-4.0.4_AEs_cumulative_Fix.jar and WAS_Security_06-17-2003_4.0.6-4.0.5-4.0.4_AEs_cumulative_Fix as well as any fixes for APARs listed below. CMVC Defect: See APAR list below Byte size of APAR: 1325655 Date: 08/20/2003 Abstract: Security cumulative fix 08/15/2003. Description/symptom of problem: See APAR list below. Directions to apply fix: PQ70895 must be installed for this fix to properly function on 4.0.4. If PQ70895 is not installed, web applications will fail to function with security enabled. This fix can be obtained from: http://www-1.ibm.com/support/docview.wss?uid=swg24004451 1) Create temporary "efix" directory to store the jar file: AIX: /tmp/WebSphere/efix Solaris/Linux: /tmp/WebSphere/efix Windows: c:\temp\WebSphere\efix 2) Copy jar file to the directory 3) Shutdown WebSphere 4) Run the jar file with the following command answering questions/prompts as they appear: java -jar 5) Restart WebSphere 6) The temp directory may be removed but the jar file should be saved. Do not remove any files created and stored in the /WebSphere/AppServer/efix/ directories. These files are required if an efix is to be removed. Directions to remove fix: NOTE: EFIXES MUST BE REMOVED IN THE ORDER THEY WERE APPLIED. DO NOT REMOVE AN EFIX UNLESS ALL EFIXES APPLIED AFTER IT HAVE FIRST BEEN REMOVED. YOU MAY REAPPLY ANY REMOVED EFIX. Example: If your system has efix1, efix2, and efix3 applied in that order and efix2 is to be removed, efix3 must be removed first, efix2 removed, and efix3 re-applied. 1) Change directory to the efix location (/WebSphere/AppServer/efix/). 2) Shutdown WebSphere 3) Run the backup jar file with the following command: java -jar 4) Restart WebSphere Directions to re-apply fix: Follow the instructions for applying an efix. If the backup files still exist (from the previous efix application), you will be prompted to overwrite. Answer "yes" at the overwrite prompts. Additional Information: ------------------------------------------------------------------ If the following excption is encountered after applying the fixes, apply the latest JSSE fix. java.net.SocketException: Socket closed at java.net.PlainSocketImpl.socketSetOption(Native Method) at java.net.PlainSocketImpl.setOption(PlainSocketImpl.java:210) at java.net.Socket.setKeepAlive(Socket.java:619) at .... The following properties must be set for PQ56218 to be effective: In the admin.config file: com.ibm.CORBA.ListenerPort=2000 com.ibm.CORBA.SSLPort=2001 com.ibm.CORBA.LSDPort=9000 com.ibm.CORBA.LSDSSLPort=9001 In each of the Application servers system properties: com.ibm.CORBA.ListenerPort=3000 com.ibm.CORBA.SSLPort=3001 Note, each port number must be unique and must not be in use by any other service on the system. To enable PQ63020, set the following property in the admin.config. com.ibm.ejs.security.customregistry.useSecurityName=true Included APARS: APAR: PQ66162 Version: 400 Abstract: SERVERSIDEAUTHENTICATOR DOESN'T THROW EXCEPTION Error Description: SSOAuthenticator - When used 1. Authenticates userid and password. 2. Throws exception when authentication fails (works correctly) 3. Set HttpRequest and HttpResponse LPTA cookie so that they can be passed by servlet. 4. DOES NOT SET THE CONTEXT for SAS communication for ejb layer. So the ejb thinks the user is UNAUTHENTICATED and fails. ServerSideAuthenticator - When used 1. Authenticates userid and password. 2. DOES NOT Throws exception when authentication fails. 3. DOES NOT Set HttpRequest and HttpResponse LPTA cookie so that they can be passed by servlet. 4. Set context for for SAS communication for ejb layer. So, with this being the case, i have to use 2 separate API to authenticate correctly and set the desired information to enable J2EE security framework. Right now I call ServerSideAuthenticator first then SSOAuthenticator. Seems kind of expensive to me and confusing. Customer requests a fix for ServerSideAuthenticator for WebSphere Application Server 4.03 on AIX. When ServerSideAuthentication fails to authenticate, it returns a null credential. Not basic credentials. Second, a client may use ServerSideAuthenitcate for authentication purpose only. They may never go to a secure resource (like ejb) after that. Or my ejb may not be secure....I know that the ejb container will throw the error because the user is UNAUTHENTICATED. This is not new to developers, however, the Application Server is relying on the Ejb Server Container (security mechanism) to throw the error for simple WebSphere Application Server authentication...Not authorization...this is not correct. Local Fix: Logically Dependent Apars: Users Affected: WebSphere Application Server users who uses ServerSideAuthenticator to perform authentication. Problem Description: ServerSideAuthenticator should throw LoginFailed when login fails. Recommendation: Problem Summary: ServerSideAuthenticator should throw org.omg.SecurityLevel2.LoginFailed exception when the login fails and the force_authn flag is true instead of returing a null credential. Problem Conclusion: ServerSideAuthenticator will now throw org.omg.SecurityLevel2.LoginFailed exception when login fails. Test Comments: Circumvention: Temporary Fix: Available Comments: APAR: PQ69036 Version: 400 Abstract: APPLYING 11/19 CUMULATIVE SECURITY EFIX ON WAS 4.0.4 CAUSES SECJ0129A AUTHORIZATION FAILURE THAT DIDN'T OCCUR BEFORE EFIX Error Description: Environnment: WebSphere Application Server (WAS) 4.0.4 AE LDAP server . Description: After applying the 11/19/2002 cumulative security eFix, customer starts getting the following exception in the stdout file that didn't occur before the cumulative security efix was applied: . 12/5/02 10:29:02:301 CST 6e93ebd8 WebCollaborat A SECJ0129A: Authorization failed for while invoking POST on default_host:, Authorization failed, Not granted any of the required roles: Local Fix: Remove the cumulative security eFix Logically Dependent Apars: Users Affected: WebSphere Application Server users who have enabled security and use LDAP for the user registry. Problem Description: Authorization failure (403) received after security cache time out is exceeded. Recommendation: Problem Summary: After the cache timeout is exceeded, authorization failures (403) could occur. The reason is while creating new credentials, the group type was not properly appended to the group name which cuased the authorization code to fail in finding the proper group name in security roles. Problem Conclusion: The group type is now properly appended to the group name. A fix for this APAR will be contained in any security cumulative eFix dated after the closure date of this APAR. Test Comments: Circumvention: Temporary Fix: A test fix was provided. Comments: APAR: PQ69643 Version: 400 Abstract: AUTHORIZATION (403) FAILURES FORWARDING FROM AN UNPROTECTED SERVLET OR JSP TO A PROTECTED ONE. Error Description: Authorization (403) failures when forwarding from an unprotected servlet or JSP to a protected one. This issue can also be seen if the contect root is not protected but the default page is protected as a forward is implicit in this scenario. Local Fix: Protect the initially requested page. Logically Dependent Apars: Users Affected: All WebSphere Application Server users who have enabled sec urity and are using RequestDispatcher.forward() to forward from an unprotected servlet or JSP to a prot ected one. Problem Description: Authorization failure (403) is received. Recommendation: Problem Summary: An authorization failure is received when using RequestDispatcher.forward() to forward from an unprotected servlet or JSP to a protected one. Problem Conclusion: The servlet 2.3 specification, section 12.2, specifies that the security model does not apply when using a RequestDispatcher. Therefore, the recommended resolution to this issue is to protect the URI which is invoking RequestDispatcher.forward(). This prepares the application for migration to WebSphere 5.X. If this is not possible then setting the following property on each application server will yield a challenge when forwarding from an unprotected URI to a protected one. com.ibm.ws.security.RequestDispatcherChallenge=true Code implementing this property will be contained in any security cumulative eFix dated after the closure date of this APAR as well as the cumulative eFix dated 01-06-2003. Internal defect number 155475. Test Comments: Circumvention: Protect the URI which is invoking RequestDispatcher.forward(). Temporary Fix: Comments: APAR: PQ72357 Version: 400 Abstract: 403 FORBIDDEN ERRORS 20% OF THE TIME Error Description: . When accessing the /wps/portal page, 403 (forbidden) errors are sometimes returned. In a 62 hour test run, the 403 error occurred aproximately 20% of the time. Local Fix: None Logically Dependent Apars: Users Affected: WebSphere Application Server users who have enabled security and have secured at least one URI. Problem Description: Authorization fails without being challenged. Recommendation: Problem Summary: When multiple concurrent requests are received by the Web container for protected URIs, authorization failures may occur without any challenge. Problem Conclusion: A timing issue existed with the use of an instance variable. The variable was changed to a method variable which insures that two simultaneous threads do not update the variable concurrently. Test Comments: Circumvention: Temporary Fix: send testing fix. Comments: APAR: PQ68148 Version: 400 APAR: PQ65884 Version: 350 Abstract: REQUESTDISPATCH.FORWARD() TO A PROTECTED SERVLET FAILS Error Description: . Failing on security when doing requestdispatch.forward() to a protected servlet (and now failing) from the "baseLogon" servet that calls SSOAuthenticator. After calling SSOAuthenticator, the request thread should have a security context established and should not fail on the requestdispatch.forward() call. Local Fix: Test efix PMR81595-356-test-0829 fixed the customer's problem. Need official efix. Logically Dependent Apars: Users Affected: All WebSphere Application Server users who have enabled securit y. Problem Description: Users may not be properly challenged while accessing secured r esources. Recommendation: Problem Summary: Authenticated user may get challenged again, or unauthenticated user may not be challenged as authentication was not properly flaged. This scenario is only likely to occur if a servlet forwards or dispatches to another secured servlet. Problem Conclusion: The flag used to determine authentication was not used correctly. The flag has now been removed as it is redundant. Test Comments: Circumvention: Temporary Fix: test eFix has been send to customer Comments: APAR: PQ66190 Version: 400 Abstract: PROPFILEPASSWORDENCODER COMMAND CAUSES PROPERTY FILES' OWNERSHIP AND PERMISSIONS TO CHANGE TO THAT OF THE USER RUNNING THE SCRIPT Error Description: Environment: WebSphere Application Server 4.0.3 AE for Solaris . Description: Running the PropFilePasswordEncoder.sh command causes the user/group ownership and permissions to change to the default settings for the user running the script. Local Fix: Change ownership and permissions back after running the command. Logically Dependent Apars: Users Affected: All WebSphere Application Server users of PropFilePasswordEnco der script Problem Description: PropFilePasswordEncoder command causes property files' ownership to change Recommendation: Problem Summary: After running PropFilePasswordEncoder script, the user and group ownership and the file permissions of those files changed to the default settings for the user running the PropFilePasswordEncoder script. Problem Conclusion: The way of how backup files are generated is modified, so the original property files can keep their original file permissions. Test Comments: Circumvention: Temporary Fix: Available Comments: APAR: PQ66974 Version: 400 Abstract: GETCALLERPRINCIPAL() SHOULD JUST ALWAYS RETURN "UNAUTHENTICATED" Error Description: Customer sent the following: We have a distributed log viewer servlet architecture, which means each AppServer must have a Servlet to read log file and present it to the end user. . So we must know how to invoke this servlet before it is serviceable(choosable from a drop down list). In the servlet init() method, we probe WebSphere servlet engine configuration to obtain HTTP port number for the hosting AppServer. Then the user can pick a LogViewer and invoke it based on this information. . The available LogViewer Tracking EJB has to be invoked from the init() method in this sense, so in the serlvet init() we will perform following execution: . try { /** retrieve the collection of application server adapters, retrieve configuration information from servlet engin */ String adapterName = SystemProperties.get("LOGSERVER_ADAPTER"); LogServerAdapter adapter = . (LogServerAdapter)Class.forName(adapterName).newInstance(); . LogServer myLogServer = adapter.getLocalLogServer(); m_logServerManager = CoreManagerFactory.getLogServerManager(); /** first, see if the log server is already in the database */ Collection logServers = m_logServerManager.getLogServers(); for (Iterator it = logServers.iterator(); it.hasNext(); ) { LogServer logServer = (LogServer)it.next(); if (myLogServer.getHost().equalsIgnoreCase(logServer.getHost()) && myLogServer.getPort() == logServer.getPort()) { m_logServerID = logServer.getID(); break; } } if (m_logServerID == null) { /** did not find my log server in the database, create a new record */ m_logServerID = m_logServerManager.createLogServer(myLogServer); } } catch (Exception e) { m_cat.l7dError(CoreEjbBundleKey.DEFAULT, e); } . And in our LogServerManager EJB, it is plain DB persistence stateless session bean. createLogServer() is just an insert statement, while getLogServerManager() is simple select statement. As we have an abstract OR layer, I just provide the functionality of these methods here. . In our EJB, we have logging system, which will always capture user's caller information at the begining of the method and push it down to the underneath logging system. So whenever there is exception and it needs logging, the logging system can always write down the caller infomation transparently. Logging system is based on Log4j. . createLogServer(Object value) { // this method internally will keep track caller info, it is pushed down to the logging system, which is defined in a parent EJB class methodStart("createLogServer", value); try { // operations; } catch(Exception e) { // whenever we want to log the exception, we retrieve back the caller info directly from logging system // so the api is ignorant of it is inside EJB or Servlet logging(e); } finally { // we will pop up the caller info from the logging system methodFinish(); } } . This model is applied to every single EJB in our system, and it will fail in the methodStart() invokation for requests initiated from init() of a servlet. . private void methodStart(String methodName, Object params) { m_strCurrentMethod = methodName; m_params = params; . if (m_sessionContext != null) NDC.push(m_sessionContext); . Category cat = getCategory(); if (cat != null && cat.isDebugEnabled()) { StringBuffer buf = new StringBuffer(100); buf.append("ENTER: "); buf.append(getMethodNameWithParams()); cat.debug(new String(buf)); } } . In the NDC.push(): public static void push( javax.ejb.EJBContext theContext { push( theContext.getCallerPrincipal() ); } . NDC class is used for: The NDC class implements nested diagnostic contexts as defined by Neil Harrison in the article "Patterns for Loggin Diagnostic Messages" part of the book "Pattern Languages of Program Design 3" edited by Martin et al.

A Nested Diagnostic Context, or NDC in short, is an instrument to distinguish interleaved log output from different sources. . This problem applies to all EJBs that will track caller and being invoked from init() method of servlets. Local Fix: None Logically Dependent Apars: Users Affected: WebSphere Application Server 4.0 security users who use progra mmatic security. Problem Description: If the anonymous principal is propagated or the user id entity is missing, getCallerPrincipal() returns inconsistan t results. Recommendation: Problem Summary: getCallerPrincipal() returns different results in different timing if the anonymous principal is propagated or caller identity is missing. EJB 1.2 spec define that getCallerPrincipal() should always return container specific unauthenticated principal. Problem Conclusion: getCallerPrincipal() should return "UNAUTHENTICATED", the WebSphere specific unauthenticated principal, if caller identity is missing or the anonymous principal is propagated. Test Comments: Circumvention: Temporary Fix: send testing eFix to customer. Comments: APAR: PQ67473 Version: 400 Abstract: % SIGN IN THE USER CREDENTIALS IS CORRUPTED WHEN PASSED THROUGHTHE GETUSERPRINCIPAL CLASS Error Description: custom tion Description Form based security using er uses is a \242 (cent sign). When passed to getUserPrincipal, .ustomer programmatically checks security with user name goes in as usercompany, and comes back from the .etUserPrincipal API. For business reasons, customer uses a method as usercompany. This worked under .egistry to store usernames as weblogic :) and they want it to work the same under websphere. Problem Summary The security check passes OK, but the delim the Local Fix: None Logically Dependent Apars: Users Affected: WebSphere Application Server users with security enabled. Problem Description: Unicode character in the principal namegets changed after login with SSOAuthenticator. Recommendation: Problem Summary: When using unicode characters in the principal name, the principal name gets changed with an extra character in front of the unicode character when getUserPrincipal().getName() is called after login. Problem Conclusion: Inconsistent encoding was used when we convert bytecode to string and back. UTF8 should be used. Test Comments: Circumvention: Temporary Fix: available Comments: APAR: PQ67926 Version: 400 Abstract: CANNOT START THE ADMIN SERVER WITH A USER ASSIGNED TO ADMIN ROLE Error Description: Problem Reported: Cannot start the admin server with a user assigned to Admin Role: . performed the following steps: . 1.uninstalled WAS 2.dropped and recreated the admin database 3.deleted /usr/WebSphere/AppServer 4.installed WAS 4.0 5.installed PTF 2 6.started WAS 7.configured Security to use IBM bluepages as LDAP server . 8.stopped WAS 9.started WAS 10.Added user cdsharp@us.ibm.com to admin role 11.stopped WAS 12.installed PTF 4 13.started WAS 14.Admin. Server failed to start. Generated secuirty related errors in tracefile. 15.edited sas.server.props file. Set com.ibm.CORBA.securityEnabled=false 16.connected to the admin repository database and set securityenabled =0 17.(db2 "update ejsadmin.securitycfg_table set securityenabled =0") restarted WAS 18.Admin. Server started 19.connected to server with admin client and used the security center to remove the cdsharp entry from the admin role. 20.enabled security 21.stopped WAS 22.admin. server started with no errors connected to server with admin. client (received logon prompt) Local Fix: Workaround: . Disable security in DB2 Start adminserver and admin console Remove all users from admin role Re-enable security Shut down and restart WAS Adminserver should come up. Logically Dependent Apars: Users Affected: All WebSphere Application Server users who have enabled securit y and have invalid users listed in the Administrative Role. Problem Description: If an ID which is not valid in the user registry is referenc ed in the Administrative Role, the Administrat ion Server will not initialize. Recommendation: Problem Summary: If an ID which is not valid in the user registry is referenced in the Administrative Role, the Administration Server will not initialize. The problem stems from the user registry returning a null instead of returning a valid access ID. Errors similar to the following will be encountered. 11/18/02 15:12:24:621 CST 6097e07e Initializer X SECJ0007E: Error during security initialization. Exception null at location: java.lang.NullPointerException at com.ibm.ejs.models.base.bindings.applicationbnd. impl.SubjectImpl.equals(SubjectImpl.java:30) at com.ibm.etools.emf.ref.impl.OwnedListImpl. indexOf(OwnedListImpl.java(Compiled Code)) at com.ibm.etools.emf.ref.impl.OwnedListImpl. duplicate(OwnedListImpl.java(Compiled Code)) at com.ibm.etools.emf.ref.impl.OwnedListImpl. duplicate(OwnedListImpl.java(Compiled Code)) at com.ibm.etools.emf.ref.impl.OwnedListImpl. add(OwnedListImpl.java:48) at com.ibm.ejs.models.base.bindings.applicationbnd.gen. impl.UserGenImpl$User_List.add(UserGenImpl.java:31) at com.ibm.ejs.security.Initializer. bindServerIdToAdminApp(Initializer.java:503) at com.ibm.ejs.security.Initializer. initialize(Initializer.java:220) at com.ibm.ejs.security.Initializer. serverStarted(Initializer.java:136) at com.ibm.ws.runtime.Server. fireServerStarted(Server.java:2018) at com.ibm.ws.runtime.Server. fireServerStarted(Server.java:2011) at com.ibm.ejs.sm.server.AdminServer. initializeRuntime0(AdminServer.java:1144) at com.ibm.ws.runtime.Server. initializeRuntime(Server.java:884) at com.ibm.ejs.sm.server.AdminServer. main(AdminServer.java:392) at java.lang.reflect.Method.invoke(Native Method) at com.ibm.ws.bootstrap.WSLauncher. main(WSLauncher.java:158) . 11/18/02 15:12:24:711 CST 6097e07e Initializer X SECJ0007E: Error during security initialization. Exception null at location: java.lang.NullPointerException at com.ibm.ejs.models.base.bindings.applicationbnd. impl.SubjectImpl.equals(SubjectImpl.java:30) at com.ibm.etools.emf.ref.impl.OwnedListImpl. indexOf(OwnedListImpl.java(Compiled Code)) at com.ibm.etools.emf.ref.impl.OwnedListImpl. duplicate(OwnedListImpl.java(Compiled Code)) at com.ibm.etools.emf.ref.impl.OwnedListImpl. duplicate(OwnedListImpl.java(Compiled Code)) at com.ibm.etools.emf.ref.impl.OwnedListImpl. add(OwnedListImpl.java:48) at com.ibm.ejs.models.base.bindings.applicationbnd.gen. impl.UserGenImpl$User_List.add(UserGenImpl.java:31) at com.ibm.ejs.security.Initializer. bindServerIdToAdminApp(Initializer.java:503) at com.ibm.ejs.security.Initializer. initialize(Initializer.java:220) at com.ibm.ejs.security.Initializer. serverStarted(Initializer.java:136) at com.ibm.ws.runtime.Server. fireServerStarted(Server.java:2018) at com.ibm.ws.runtime.Server. fireServerStarted(Server.java:2011) at com.ibm.ejs.sm.server.AdminServer. initializeRuntime0(AdminServer.java:1144) at com.ibm.ws.runtime.Server. initializeRuntime(Server.java:884) at com.ibm.ejs.sm.server.AdminServer. main(AdminServer.java:392) at java.lang.reflect.Method.invoke(Native Method) at com.ibm.ws.bootstrap.WSLauncher. main(WSLauncher.java:158) . 11/18/02 15:12:24:751 CST 6097e07e AdminServer X WSVR0009E: Error occurred during startup java.lang.RuntimeException at com.ibm.ejs.security.Initializer. serverStarted(Initializer.java:142) at com.ibm.ws.runtime.Server. fireServerStarted(Server.java:2018) at com.ibm.ws.runtime.Server. fireServerStarted(Server.java:2011) at com.ibm.ejs.sm.server.AdminServer. initializeRuntime0(AdminServer.java:1144) at com.ibm.ws.runtime.Server. initializeRuntime(Server.java:884) at com.ibm.ejs.sm.server.AdminServer. main(AdminServer.java:392) at java.lang.reflect.Method.invoke(Native Method) at com.ibm.ws.bootstrap.WSLauncher. main(WSLauncher.java:158) Problem Conclusion: Null access IDs are now checked and ignored. Test Comments: Circumvention: Temporarily disable security, remove invalid IDs from the Administrative Role then restart then restart. Re-enable security then restart again. Temporary Fix: provided testing eFix to customer. Comments: APAR: PQ68882 Version: 400 Abstract: CANNOT HAVE , AND () IN ADMIN CONSOLE USER NAME Error Description: The customer cannot use user names that contain the comma character , and parentheses () in the DN as admin console users. The trace file contains the error message 'Invalid LDAP user'. Local Fix: There is no workaround for users whose DN contains a comma and parentheses characters. Logically Dependent Apars: Users Affected: WebSphere Application Server security users who has used a comma (, ASII 44) or open parenthese (ASII 40) or close parenthese (ASII 41) in a user's security name. Problem Description: If a user name or attributes in a DN (if LDAP is the user regi stry) contain comma or open parenthese or close parenthese, authorization for the DN may fail. Recommendation: Problem Summary: If user name or attribute in DN (if using LDAP registry) contain comma or open parenthese or close parenthese, user name was improperly truncated as security use those characters as delimiter, which results authorization error. If a Custom Registry is in use, this also applies to names returned by the following methods: List getUsers() List getUsers(String pattern) String getUserDisplayName(String userName) String getUniqueUserId(String userName) List getUniqueUserIds(String uniqueGroupId) String getUserSecurityName(String uniqueUserId) Problem Conclusion: Comma's and parenthesis were used internally as delimeters. The use of parenthesis as delimiters has been removed. Commas are now treated properly by escaping them. A fix for this APAR will be contained in any security cumulative eFix dated after the closure date of this APAR. Test Comments: Circumvention: Temporary Fix: A test fix was provided. Comments: APAR: PQ65687 Version: 400 Abstract: SECURITY EXCEPTIONS AFTER SERVER REBOOTS Error Description: We are currently having intermittent problems with the IBM WAS Admin service not starting, especially after server reboots. This generates the following entry in sas_server.log: . 1> 2002-07-24 14:23:16.772 , ServerID: 12221999 , SecurityTaggedComponentAssistorImpl.register , Thread Hash: 673378419 Thread P=596272:O=0:CT,5,main : . JSAS0026E: Exception connecting object to the ORB. Check the sas.server.props file to ensure that the SSL keyStore and trustStore properties are set properly. If the problem persists, contact support for assistance. . We did apply the following fix found from the IBM Websphere support site but the problem still recurs. Solution . Put the following parameters in separate lines in the /bin/admin.config and set them to unique unused ports on the machine and restart WAS: . com.ibm.CORBA.SSLPort= com.ibm.CORBA.LSDSSLPort= . Problem occurs on WAS AE 4.03 and 4.04. Local Fix: no workaround available Logically Dependent Apars: Users Affected: All WebSphere Users that have enabled security and restart their adminstration server while their application servers a re up and running. Problem Description: If application server is up and running while the adminst ration server is restarted, then application server continues t o uses a stale IOR without loading the newly created one. Recommendation: Problem Summary: If the WebSphere Application Servers are up and running while the Admin Server is rebooted; then the Application servers continue to use the stale IOR for the Adminstration Server instead of getting the new IOR for the Adminstration Server. With the stale IOR, the Application Servers get OBJECT_NOT_EXIST exceptions. Problem Conclusion: To resolve this problem, the bootstrap repository is read to load the new IORs for the server that was restarted. The logic is to read the bootstrap repository to get the IORs up to three times and ping the server with the new IOR. After three times, if the server does not respond to the new IOR, then OBJECT_NOT_EXIST exception is thrown. Test Comments: Circumvention: Temporary Fix: Comments: APAR: PQ66004 Version: 400 Abstract: MULTIPLE SECURITY LOG ENTRIES FOR ONE INVALID USERID/PASSWORD. Error Description: Upon entering a wrong password for a given userid, the following log statements are written to appserver-out.log. Apart from the fact, that times the same message seems unnecessary, it should the application's decision whether to write or not to write such message regarding invalid logins. Otherwise, a very simple denial of service attack could logins. Otherwise, a very simple denial of service attack could be convinced with bogus login attempts keeping the machine busy logging these messages. 8/26/02 13:17:39:080 CEST 37b2205d SystemOut U 5> 2002-08-26 13:17:39.08 , ServerID: 375334458 , LoginHelperImpl.request_login_controlled : 8/26/02 13:17:39:090 CEST 37b2205d SystemOut U JSAS0240E: Login failed. Verify the userid/password is correct. Check the properties file to ensure the login source is valid. If this error occurs on the server, check the server properties to ensure the principalName has a valid realm and userid. 8/26/02 13:17:39:110 CEST 37b2205d SystemOut U 6> 2002-08-26 13:17:39.11 , ServerID: 375334458 , CredentialsImpl.get_mapped_credentials : 8/26/02 13:17:39:120 CEST 37b2205d SystemOut U JSAS0240E: Login failed. Verify the userid/password is correct. Check the properties file to ensure the login source is valid. If this error occurs on the server, check the server properties to ensure the principalName has a valid realm and userid. 8/26/02 13:17:39:451 CEST 37b2205d SystemOut U 8> 2002-08-26 13:17:39.451 , ServerID: 375334458 , CredentialsImpl.get_mapped_credentials : 8/26/02 13:17:39:481 CEST 37b2205d SystemOut U JSAS0240E: Login failed. Verify the userid/password is correct. Check the properties file to ensure the login source is valid. If this error occurs on the server, check the server properties to ensure the principalName has a valid realm and userid. Action Planned: Sending to entitlement, then to WAS for customer Local Fix: none Logically Dependent Apars: Users Affected: WebSphere Application Server users who have security enabled. Problem Description: Multiple security log entries for one invalid login. Recommendation: Problem Summary: Upon entering a wrong password for a given userid, the following 3 log statements are written to appserver-out.log. It's unnecessary to have 3 login error messages. 8/26/02 13:17:39:080 CEST 37b2205d SystemOut U 5> 2002-08-26 13:17:39.08 , ServerID: 375334458 , LoginHelperImpl.request_login_controlled : 8/26/02 13:17:39:090 CEST 37b2205d SystemOut U JSAS0240E: Login failed. Verify the userid/password is correct. Check the properties file to ensure the login source is valid. If this error occurs on the server, check the server properties to ensure the principalName has a valid realm and userid. 8/26/02 13:17:39:110 CEST 37b2205d SystemOut U 6> 2002-08-26 13:17:39.11 , ServerID: 375334458 , CredentialsImpl.get_mapped_credentials : 8/26/02 13:17:39:120 CEST 37b2205d SystemOut U JSAS0240E: Login failed. Verify the userid/password is correct. Check the properties file to ensure the login source is valid. If this error occurs on the server, check the server properties to ensure the principalName has a valid realm and userid. 8/26/02 13:17:39:451 CEST 37b2205d SystemOut U 8> 2002-08-26 13:17:39.451 , ServerID: 375334458 , CredentialsImpl.get_mapped_credentials : 8/26/02 13:17:39:481 CEST 37b2205d SystemOut U JSAS0240E: Login failed. Verify the userid/password is correct. Check the properties file to ensure the login source is valid. If this error occurs on the server, check the server properties to ensure the principalName has a valid realm and userid. Problem Conclusion: 2 unnecessary messages are removed. Only one message will be logged. Test Comments: Circumvention: Temporary Fix: PQ66004_eFix_test.jar Comments: APAR: PQ66449 Version: 400 Abstract: AUTH PRINCIPAL NULLS OUT AND CAUSES AUTHORIZATION FAILURE. Error Description: Note from Tom D. at the WCC . Trace and this note on wasdoc0. . - error occurs on thread 5f8245 - prior authentication checks on this thread have succeeded - the failure occurs at 13:06:58 - sequence of events: - EJSSecurityCollaborator.preInvoke - received and invoke creds are both non-null - SetUnauthenticatedCredIfNeeded returns false, meaning that the creds are authorized - SecurityCollaborator.performAuthorization is called - since invokedCred is non-null, curReceived will be set to the value of invokedCred - ejbCheckAuthorization is called with curReceived - WSCheckAccessManager.checkAccess is called. One of the args is a new WSPrincipal, which is constructed with the receivedCred. - in checkAccess, creds is initialized to null. If the principal is non-null, then getCredentials will be called on the principal object. - isGrantedAnyRole is called with the creds object. If the creds object is null, or creds.isUnauthenticated is true, then the error occurs. Since there is one error message for two possible conditions, we do not know which one triggered the error. creds can be null if: 1) the principal passed to checkAccess is null. Then creds will not be set. 2) the call to getCredentials on the principal passed in returns null. - not sure where the code is for isUnauthenticated, so I do not know what conditions would cause this call to return true. * but, upon return to checkAccess from isGrantedAnyRole, a message is printed with the value of principal.toString(), which is UNATHENTICATED. So if the principal is UNAUTHENTICATED, then the call to getCredentials will probably produce null. . QUESTIONS: - why does the same thread seem to be able to create ejbs and have the authentication checks succeed, and then later fail on a subsequent create check? - from looking at two different traces, it does not appear as if the failure only occurs on one ejb. So that could rule out a config/deployment issue. - does an UNAUTHENTICATED invokeCreds object somehow get associated with the call? invokedCred is set by a call to current.get_credentials(). . At this point, I'm thinking that the call to current.get_credentials() in performAuthorization is perhaps not returning the proper credentials, and this leads to the client appearing as unauthenticated. But I still do not have enough evidence to back this up. Local Fix: No workaround available. Logically Dependent Apars: Users Affected: WebSphere Application Server users with security enabled and LocalOS as user registry. Problem Description: The authentication principal is lost which causes authorizatio n failure. Recommendation: Problem Summary: Authentication principal becomes unauthenticated when a valid uid/password is used. Actual Exception: ================= securityName: /UNAUTHENTICATED;accessID: UNAUTHENTICATED is not granted any of the required roles: XXXXX 9/24/02 9:23:37:698 EDT 261218 SecurityColla D Authorization failed accessing EJB com.ibm.ws.security.core.AccessException: securityName: /UNAUTHENTICATED;accessID: UNAUTHENTICATED is not granted any of the required roles: Problem Conclusion: LocalOS credentials were not mapped correctly to the OS user registry when a web request qas received. LocalOS credentials are now correctly mapped. Test Comments: Circumvention: Temporary Fix: available Comments: APAR: PQ69078 Version: 400 Abstract: PERFORMANCE DEGRADATION AFTER APPLYING SECURITY CUMULATIVE EFIX FROM 10-07 Error Description: Customer says that they experience degradation in performance after applying WAS Security cumulative efix dated 10-07-02. Local Fix: none Logically Dependent Apars: Users Affected: All WebSphere Application Server users who have enabled securit y and have deployed web applications with protected resource s. Problem Description: Performance degradation in web applications. Recommendation: Problem Summary: Performance degradation in web applications caused by the unnecessary creation of the special credential "UNAUTHENTICATED" with each web request to a protected resource. Problem Conclusion: The UNAUTHENTICATED credential is now cached after it is created the first time. Test Comments: Circumvention: Temporary Fix: Testfix submitted to Portal Server. Comments: APAR: PQ70121 Version: 400 Abstract: JAVA.LANG.NULLPOINTEREXCEPTION ERROR ON WAS 4.04 AFTER CUMULATIVE SECURITY EFIX INSTALLED. Error Description: Customer installed WAS 4.04 on AIX 4.3.3. Then installs cumulative security efix dated 01-06-2003. Database is ORacle. After starting admin server, sees in the tracefile: [1/21/03 9:18:20:458 CST] 1c37f64b EJBEngine I WSVR0037I: Starting EJB jar: Tasks java.lang.NullPointerException at com.ibm.ISecurityLocalObjectBaseL13Impl.VaultImpl.get_default_cr edentials(VaultImpl.java(Compiled Code)) at com.ibm.ISecurityLocalObjectBaseL13Impl.CurrentImpl.get_credenti als(CurrentImpl.java(Compiled Code)) at com.ibm.ISecurityLocalObjectBaseL13Impl.CurrentImpl.get_credenti als(CurrentImpl.java:313) at com.ibm.ISecurityLocalObjectBaseL13Impl.CurrentImpl.get_credenti als(CurrentImpl.java:299) at com.ibm.ejs.security.SecurityContext.enable(SecurityContext.java :151) at com.ibm.ws.wlm.admin.config.ServerGroupRefresh$RefreshThread.run (ServerGroupRefresh.java:330) [1/21/03 9:18:26:868 CST] 1c37f64b Server A WSVR0023I: Server __adminServer open for e-business . This error does not appear to affect function of the admin server security. Local Fix: none Logically Dependent Apars: Users Affected: All WebSphere Application Server users who have enabled security. Problem Description: java.lang.NullPointerException in tracefile during server startup after security cumulative fix installed. Recommendation: Problem Summary: java.lang.NullPointerException occured during the server startup. Exception as follows: java.lang.NullPointerException at com.ibm.ISecurityLocalObjectBaseL13Impl.VaultImpl. get_default_credentials(VaultImpl.java(Compiled Code)) at com.ibm.ISecurityLocalObjectBaseL13Impl.CurrentImpl. get_credentials(CurrentImpl.java(Compiled Code)) at com.ibm.ISecurityLocalObjectBaseL13Impl.CurrentImpl. get_credentials(CurrentImpl.java:313) at com.ibm.ISecurityLocalObjectBaseL13Impl.CurrentImpl. get_credentials(CurrentImpl.java:299) at com.ibm.ejs.security.SecurityContext. enable(SecurityContext.java:151) Problem Conclusion: java.lang.NullPointerException occured during the server startup. The null value caused the server credential cache to throw the java.lang.NullPointerException during the startup. However, this exception should not cause any functional loss. A fix for this APAR will be contained in any security cumulative eFix dated after the closure date of this APAR. Test Comments: Circumvention: Temporary Fix: available Comments: APAR: PQ71310 Version: 400 Abstract: getUserPrincipal() getname() returns wrong name rather than logg ed in username accessing from another domain Error Description: Customer logs in to the administration console using the administration username and password The Custom realm is called and accepts the administration username and password. Then logs to the Web Application using a web username and password (username and password are different from administration username and password): The Custom realm is called and accepts the authentication. The Web Application (a servlet) calls getUserPrincipal().getName() from the HttpServletRequest. The Web application receives the administration user identity. Later calls to getUserPrincipal().getName() from the HttpServletRequest return the correct logged user. Local Fix: none Logically Dependent Apars: Users Affected: WebSphere Application Server security users who have deployed servlets and EJBs in different realms. Problem Description: getName() in getUserPrincipal() may not return the right security name during an EJB call. Recommendation: Problem Summary: getName() in getUserPrincipal() may return wrong security name after servlet accesses an EJB in a different security domain. Problem Conclusion: When a servlet accesses EJB in a different realm, security will try to map the invocation credential to the target realm. If the credential mapping fails, the original credential is now returned rather than returning the default credential. Test Comments: Circumvention: Temporary Fix: provided test fix Comments: APAR: PQ71832 Version: 400 Abstract: NULL SESSION HANDLE ERRORS IN APPLICATION SERVER STDOUT FILE. Error Description: (PQ71832 is included in 5-16-2003 security cumulative fix.) 1.These errors occur repeatedly in the app servers stdout file. . [VaultImpl.get_security_context]: [12/13/02 9:11:12:905 EST] 1214b1 SystemOut U JSAS0170E: Null session handle in session table. Check to see if a server process has terminated just prior to receiving these errors. If a process has terminated, restart the process and retry the operation. Verify that the client userid/password is valid. If the login fails, the session will be deleted on the client side and the credentials will be marked invalid. If a retry occurs, you will likely see this error. Restart the client program after verifying the login info. If the errors persist, contact support for assistance. . 2.The errors happen on different application servers at different times. The customer has 52 application servers running on 2 nodes (36:1 ratio). The error also occurs in his production system which has 8 application servers to 1 node. . 3. When customer enables tracing, the errors do not occur. He is using seclogger40.jar for tracing. He began by filtering for these three classes: . com.ibm.CORBA.securityTraceFilter=SecureAssociationInterceptorI pl,VaultImpl,SecurityConnectionInterceptor . The problem did not occur during tracing. Once tracing was disabled, the problem came back. . He has also tried tracing while filtering for just one class at a time. The problem still does not occur even with tracing only one class. . 4. The customer has increased the value of maxopenconnections to 1000, and the errors still persists. The Sun environment has a limit of 1024 threads per process, so the most this value can be set to is 1024. . 5. The customer has tuned their system according to suggestions from the ORB team as follows. While this has improved other problems, it has not changed this problem. . 6. Two previous suggestions have NOT been tried: John suggested setting in sas.server.props file, the following property: com.ibm.CORBA.NotifyBrokenConnectionEnabled=false. This has not been tried due to concern over side effects (memory leaks). . The other suggestion was to just enable ORB tracing. The customer has concerns about the performance impact of doing this, and he is concerned that the ORB tracing will also mask the problem. . If level 3 thinks that it is essential to attempt these last two items, the customer is willing to attempt them - if their concerns are addressed. . This APAR is being created at the request of L3 security team: Because the null session handle error is a fully recoverable condition, the WebSphere administrator should not be informed of this condition. This APAR will address removing the message and making it a debug only message. Local Fix: Enabling security tracing on just one class causes the errors to disappear. Logically Dependent Apars: Users Affected: All WebSphere Application Server users who have enabled security. Problem Description: JSAS0170E: Null session handle in session table reported in the tracefile and Administration console. Recommendation: Problem Summary: These errors occur repeatedly in the application servers stdout file. [VaultImpl.get_security_context]: [12/13/02 9:11:12:905 EST] 1214b1 SystemOut U JSAS0170E: Null session handle in session table. Check to see if a server process has terminated just prior to receiving these errors. If a process has terminated, restart the process and retry the operation. Verify that the client userid/password is valid. If the login fails, the session will be deleted on the client side and the credentials will be marked invalid. If a retry occurs, you will likely see this error. Restart the client program after verifying the login info. If the errors persist, contact support for assistance. Problem Conclusion: The message currently represents a fully recoverable condition from respect of the code reporting it. The message has been converted into a message for debug tracing only. Test Comments: Circumvention: Temporary Fix: Comments: APAR: PQ75785 Version: 400 Abstract: 4.0.6 Admin Console re-prompting Customer for log-in Error Description: Customer is at 4.0.6 on Solaris. When they start the Admin Local Fix: During the 10 minutes after the pop-up disappears, anyone can Logically Dependent Apars: Users Affected: WebSphere Application Server users who have enabled security and are using the LTPA authentication mechanism. Problem Description: Java clients re-prompt for user ID and password after LTPAToken expired. Recommendation: Problem Summary: Java clients, including the Administration Console, may prompt for user ID and password information again after LTPA Token expired. This should not occur since Java clients use a basic authentication credential which does not expire. Problem Conclusion: The server now deletes the session on credential expiration. The client retries once using the existing basic authentication credential if the session was deleted for an expired credential. This prevents the client from re-prompting unless the user or password is no longer valid in the user registry. Test Comments: Circumvention: Temporary Fix: test fix provided. Comments: