Fixes are available
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server
Obtain the fix for this APAR.
APAR status
Closed as program error.
Error description
If a user creates a keyring in RACF for the servant region userid only, not the control region userid, and then creates a keystore or truststore that points to that keyring, then the certificates can't be viewed by the admin console. With SSL=all trace enabled: The following error surfaces in the control region indicating that the keyring does not exist for the control region userid which it doesn't. --------- Trace: 2010/07/23 19:56:19.588 01 t=8C2608 c=UNK key=S2 (13007002) ThreadId: 00000016 FunctionName: com.ibm.ws.ssl.config.WSKeyStore SourceId: com.ibm.ws.ssl.config.WSKeyStore Category: FINEST ExtendedMessage: Cannot open keystore URL and since this is a RACFKS, we will return null: ; java.io.IOException: R_datalib (IRRSD L00) error: profile for ring not found (8, 8, 84) at com.ibm.crypto.provider.RACFInputStream.a(Unknown Source) at com.ibm.crypto.provider.RACFInputStream.<init>(Unknown at com.ibm.crypto.provider.safkeyring.a.getInputStream(Unknown at java.net.URL.openStream(URL.java:1011) com.ibm.ws.ssl.config.WSKeyStore.openKeyStore(WSKeyStore.java:11 at com.ibm.ws.ssl.config.WSKeyStore$1.run(WSKeyStore.java:807) com.ibm.ws.security.util.AccessController.doPrivileged(AccessCon com.ibm.ws.ssl.config.WSKeyStore.do_getKeyStore(WSKeyStore.java: com.ibm.ws.ssl.config.WSKeyStore.getKeyStore(WSKeyStore.java:874 com.ibm.ws.ssl.config.WSKeyStore.invokeKeyStoreCommand(WSKeyStor com.ibm.ws.ssl.config.WSKeyStore.invokeKeyStoreCommand(WSKeyStor com.ibm.ws.ssl.core.SSLAdmin.invokeRemoteKeyStoreCommand(SSLAdmi com.ibm.ws.ssl.core.SSLAdminProxy.invokeRemoteKeyStoreCommand(SS oxy.java:281) .... --------- You will also find an FFDC log owned by the control region useid with the above stacktrace as well. The RACF adminstrator can confirm that the keyring exists for the servant region userid, but not for the control region userid by issuing the sample RACF command RACDCERT LISTRING(KEYRING) ID(CNTL_USERID) RACDCERT LISTRING(KEYRING) ID(SRVNT_USERID) Where CNTL_USERID is the control region userid, SRVNT_USERID is the servant region userid, and KEYRING is the KEYRING that is defined for the servant region userid.
Local fix
Define a keyring for the control region userid with the same name as the servant region keyring name. The keyring does not have to have any certificates on it. RACDCERT ADDRING(KEYRING) ID(CNTL_USERID)
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V7.0 * **************************************************************** * PROBLEM DESCRIPTION: If a user creates a keyring in RACF * * for the servant region * * userid only, not the control region * * userid, and then creates a * * keystore or truststore that points to * * that keyring, then the * * certificates can't be viewed by the * * admin console. * **************************************************************** * RECOMMENDATION: * **************************************************************** WebSphere Application Server was incorrectly marking the keystore as Read/Write internally. Exception handling was driven due to a failed attempt to create a writable keystore.
Problem conclusion
WebSphere Application Server was modified to correctly mark the keystore as ReadOnly. APAR PM20000 is currently targeted for inclusion in Service Level 7.0.0.15 of WebSphere Application Server. Please refer to URL: //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970 for Fix Pack availability.
Temporary fix
Comments
APAR Information
APAR number
PM20000
Reported component name
WEBSPHERE FOR Z
Reported component ID
5655I3500
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2010-08-06
Closed date
2010-10-11
Last modified date
2011-04-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Fixed component name
WEBSPHERE FOR Z
Fixed component ID
5655I3500
Applicable component levels
R700 PSY UK65060
UP11/03/04 P F103
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
Document Information
Modified date:
24 October 2021