PI07570: IBM CONNECTIONS POLICY FAILS TO PASS CONNECTIONS ERROR STATUS CODES TO THE CALLER

APAR status

• Closed as program error.

Error description

• When calling a request against connections which results in a
  status code 403 for example, this will always result in a 404
  being reported by the ajax data sources.
  
  This does make sense for general use of the ajax proxy, however,
  for the connections integration use case it would be reasonable
  to be able to react accordingly to the connections response.
  

Local fix

• Adding the metadata
  
  <meta-data>
  <name>forward-http-errors</name>
  <value>true</value>
  </meta-data>
  
  to the respective proxy-config.xml would relieve this issue.
  

Problem summary

• When calling a request against connections which results in a
  status code 403 for example, this will always result in a 404
  being reported by the ajax data sources.
  
  This does make sense for general use of the ajax proxy, however,
  for the connections integration use case it would be reasonable
  to be able to react accordingly to the connections response.
  .
  

Problem conclusion

• A code fix for this issue is integrated into the WebSphere
  Portal & WCM Combined Cumulative Fix 10 (PI08371) for Portal
  8.0.0.1 available from Fix Central:
  
  http://www-933.ibm.com/support/fixcentral/swg/selectFixes?parent
  =ibm/WebSphere&product=ibm/WebSphere/WebSphere+Portal&release=Al
  l&platform=All&function=aparId&apars=PI08371
  
  You might need to type or paste the complete address into your
  Web browser.
  

Temporary fix

Comments

APAR Information

• 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 PORTA

• Fixed component ID

  5724E7600

Applicable component levels

• R800 PSY

     UP