Fixes are available
8.0.0.3: WebSphere Application Server V8.0 Fix Pack 3
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
8.0.0.4: WebSphere Application Server V8.0 Fix Pack 4
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
8.0.0.5: WebSphere Application Server V8.0 Fix Pack 5
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
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.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
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.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
APAR status
Closed as program error.
Error description
While creating a foreign bus using the foreign bus creation wizard, if you leave the "Inbound User ID" field blank the wizard will insert an empty string value for the inboundUserid into the sub-bus.xml. This empty userid value overrides the any user ids configured in messages and leads the the errors in the log as shown in the following example: [10/28/11 9:21:03:390 IST] 0000002a SibMessage W [:] CWSII0227W: The bus securebus2 denied an anonymous user access to send messages to the destination _SYSTEM.Exception.Destination. [10/28/11 9:21:03:390 IST] 0000002a SibMessage W [:] CWSIP0313E: A user is not authorized to access exception destination _SYSTEM.Exception.Destination.Node01.Server1-Bus1. In the sib-bus.xml, the inboundUserid attribute is added even though it was left blank during the foreign bus creation wizzard as seen below: <virtualLink xmi:type="sibresources:SIBVirtualGatewayLink" xmi:id="SIBVirtualGatewayLink_12345" name="Bus1:Bus2" uuid="67890" inboundUserid=""> This attribute value is overriding any userids sent in messages or over the secure bus link. When a user attempts to put a message onto the foreign destination, the empty userid value is used and assumed to be anonymous, therefore permission is denied.
Local fix
You can correct the configuration in the following way: 1. Navigate to the properties of the foreign bus and set a userid in the Inbound User ID field. 2. Save the changes. 3. Navigate back to the forign bus properties and remove the value in the Inbound User ID field. 4. Save the changes. The inboundUserid attribute is removed from the sib-bus.xml as in the following example and the connection works as expected: <virtualLink xmi:type="sibresources:SIBVirtualGatewayLink" xmi:id="SIBVirtualGatewayLink_1319772922647" name="securebus1:securebus2" uuid="021401B7FA2C9BA7FFC711D7">
Problem summary
**************************************************************** * USERS AFFECTED: Users of the default messaging provider * * for IBM WebSphere Application Server 7.0 * * and 8.0. * **************************************************************** * PROBLEM DESCRIPTION: When a user attempts to put a message * * onto the foreign destination over the * * secure bus link, there is permission * * denied error. * **************************************************************** * RECOMMENDATION: * **************************************************************** In the sib-bus.xml, the inboundUserid attribute was added even though inboundUserid textbox was left blank during the foreign bus creation wizard as seen below: <virtualLink xmi:type="sibresources:SIBVirtualGatewayLink" xmi:id="SIBVirtualGatewayLink_12345" name="Bus1:Bus2" uuid="67890" inboundUserid=""> This attribute value was overriding any userids configured in messages or over the secure bus link. When a user attempted to put a message onto the foreign destination, the empty userid value esd used and assumed to be anonymous, therefore permission esd denied. sib-bus.xml is not expected to have "inboundUserid" attribute when it has empty value.
Problem conclusion
Source code has been modified not to add "inboundUserid" attribute into sib-bus.xml if the attribute has no value. The fix for this APAR is currently targeted for inclusion in fix pack 7.0.0.23 and 8.0.0.3. Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
In the admin console, go to the edit properies of the foreign bus. Then click save button (leave the "inboundUserid" as it wss). Edit doesn't add "inboundUserid" attribute into the sib-bus.xml if "inboundUserid" is empty.
Comments
APAR Information
APAR number
PM52295
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
2011-11-15
Closed date
2011-12-30
Last modified date
2012-03-09
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
Document Information
Modified date:
28 October 2021