Fixes are available
8.5.0.2: WebSphere Application Server V8.5 Fix Pack 2
8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
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
APAR status
Closed as program error.
Error description
WebShpere Application Server V7.0 Network Deployment edition. Problem: authMechanismPreference change using console shows invalid jython code in 'view last action'. To reproduce: issue: 1) Add a resource adapter and create a J2C connection factory. 2) In the administrative console, go to Resource Adapters > J2C connection factories > "name_of_connection_factory". 3) Set Authentication preference to BASIC_PASSWORD. 4) Click Ok. 5) Save changes. 6) Go back to Resource Adapters > J2C connection factories > "name_of_connection_factory". 7) Set Authentication preference to None. 8) Click Ok. 9) Click "View administrative scripting command for last action" from the right side. The command assist output displayed is similar to the following: ====================================== AdminConfig.modify('(cells/aaaacell01/clusters/testCluster| resources .xml#J2CConnectionFactory_1350310753024)', '[[authMechanismPreference "BASIC_PASSWORD"] [name "testJ2Ccf"] [authDataAlias ""] [category ""] [description ""] [jndiName "eis/testJ2Ccf"]]') ====================================== 10) Click Save. Here, the following line in the resources.xml changed from: <factories xmi:type="resources.j2c:J2CConnectionFactory" xmi:id="J2CConnectionFactory_1350310753024" name="testJ2Ccf" jndiName="eis/testJ2Ccf" authMechanismPreference="BASIC_PASSWORD" connectionDefinition="ConnectionDefinition_1350310681263"> to: <factories xmi:type="resources.j2c:J2CConnectionFactory" xmi:id="J2CConnectionFactory_1350310753024" name="testJ2Ccf" jndiName="eis/testJ2Ccf" connectionDefinition="ConnectionDefinition_1350310681263"> 11) Open wsadmin, and use the command mentioned by command assist above, followed by "AdminConfig.save()". This turns BASIC_PASSWORD back on. Trying the command again does not change the settings. So it appears that the command provided by command assist is not correct for setting the Authentication preference to None.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server using the administrative console to * * manage J2C Connection Factories. * **************************************************************** * PROBLEM DESCRIPTION: You can not change the * * authMechanismPreference of a J2C * * Connection factory from * * BASIC_PASSWORD to none. * **************************************************************** * RECOMMENDATION: * **************************************************************** The Command Assistance for setting the authMechanismPreference to none still showed BASIC_PASSWORD. Although the user did select none, BASIC_PASSWORD is still being set. It is by design that if there is an authMechanismPreference value other than none, one of those values must be selected. Only if there are no options should the value be none.
Problem conclusion
The value of none is no longer presented as a selection if an actual authMechanismPreference is provided. The command assistance was actually correct, but confusing to the user. They were not setting the authMechanismPreference to none. The fix for this APAR is currently targeted for inclusion in fix packs 7.0.0.29, 8.0.0.6, 8.5.0.2. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Comments
APAR Information
APAR number
PM75082
Reported component name
WEBS APP SERV N
Reported component ID
5724H8800
Reported release
700
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2012-10-16
Closed date
2012-12-12
Last modified date
2012-12-12
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
WEBS APP SERV N
Fixed component ID
5724H8800
Applicable component levels
R700 PSY
UP
R800 PSY
UP
R850 PSY
UP
Document Information
Modified date:
29 October 2021