PM68303: Generate the outAsyncResponseBasicAuth element instead of the outRequestBasicAuth element when configuring a PolicySetBinding

Rational Application Developer for WebSphere Software 8.5.1
Rational Application Developer for WebSphere Software 8.0.4.2
Rational Application Developer Standard Edition, Version 8.0.4.2

APAR status

• Closed as program error.

Error description

• Abstract:
  
  When configuring a PolicySetBinding for a webservice provider
  using the 'Manage Policy Set Attachment...' wizard from the
  services context menu, a bindings.xml gets generated in [EAR
  Project]/META-INF/Binding1/PolicyTypes/JMSTransport.  This
  bindings.xml file contains an outRequestBasicAuth element to
  configure Basic Authentication. However, Asynchronous Basic
  Authentication is required for a provider, represented by the
  outAsyncResponseBasicAuth element.
  
  Problem:
  
  To reproduce, do the following:
  
  The initial setup is:
  http://www.ibm.com/developerworks/websphere/library/tutorials/09
  03_adams/index.html
  
  Then create a Policy Set named 'MyPolicy' for JMSTransport like
  described in step one:
  
  http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?
  topic=/com.ibm.websphere.base.iseries.doc/info/iseries/ae/twbs_w
  sspsptjms.html
  
  Note: do NOT do steps two and three.
  
  export it from WebSphere Application Server.
  
  In Rational Application Developer:
  1. Import the Policy Set created by the server.
  2. Right click on the web Service of project 'MyProject' and
  select 'Manage Policy Set Attachment...'
  3. Click Add...
  4. Select MyPolicy as the Policy Set, enter ''Binding1' in the
  binding field and click OK
  5. Click Finish
  
  The bindings.xml file found at [EAR
  Project]/META-INF/Binding1/PolicyTypes/JMSTransport contains:
  
  ??xml version='1.0' encoding='UTF-8' standalone='yes'??
  ?wsp:Policy
  
  xmlns:wsjms='http://www.ibm.com/xmlns/prod/websphere/200801/ws-j
  msTransport'
      xmlns:wsp='http://schemas.xmlsoap.org/ws/2004/09/policy'?
      ?wsp:ExactlyOne?
          ?wsp:All?
              ?wsjms:outRequestBasicAuth?
                  ?wsjms:basicAuth userid=''
  password=''??/wsjms:basicAuth?
              ?/wsjms:outRequestBasicAuth?
          ?/wsp:All?
      ?/wsp:ExactlyOne?
  ?/wsp:Policy?
  
  but should contain
  
   ...
              ?wsjms:outAsyncResponseBasicAuth?
                  ?wsjms:basicAuth userid=''
  password=''??/wsjms:basicAuth?
              ?/wsjms:outAsyncResponseBasicAuth?
   ...
  
  Local fix:
  
  The workaround is to manually add the above code snipped to
  bindings.xml
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The outRequestBasicAuth element is incorrectly generated in
  the JMS Transport Binding.
  

Problem conclusion

• Generate the outAsyncResponseBasicAuth element instead of
  the outRequestBasicAuth element when configuring a JMS
  Transport Binding for the web service provider.
  
  The fix for this APAR is included in Rational Application
  Developer v8.0.4.2.
  

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

  RATL APP DEV WI

• Fixed component ID

  5724J1901

Applicable component levels

• R750 PSN

     UP