IT27195: SECURITY PROFILES POLICY LOOKUP FAILS IN MULTIPLE SCENARIO

APAR status

• Closed as program error.

Error description

• The lookup for a Security Profile policy fails when specified at
  the message flow level and silently fails to find the
  Default_Propagation policy when specified at the message flow
  or message flow node level.
  
  A user will see either:
  An exception being thrown on message flow load and being unable
  to start about the policy not being found:
  
  BIP9320E: Message Flow 'myFLow', 'myFlow' encountered a failure
  and could not start.
  
  BIP4761E: The message flow attempted to use 'SecurityProfiles'
  policy '{PolicyProj}:myLDAPProfile', which has not been defined
  in the integration server.
  
  or if Default_Propagation is specified as the policy then an
  error will not be seen but the user will see a node fail to
  propagate a userid/password as expected.
  
  For instance if a SOAPRequest node is expected to propagate a
  userid/password from the properties folder as BasicAuth then
  they would not see this happen.
  
  
  Additional Symptom(s) Search Keyword(s):
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of App Connect Enterprise version 11 using security
  profile policies.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  The lookup for a Security Profile policy fails when specified at
  the message flow level and silently fails to find the
  Default_Propagation policy when specified at the message flow
  or message flow node level.
  
  A user will see either:
  An exception being thrown on message flow load and being unable
  to start about the policy not being found:
  
  BIP9320E: Message Flow 'myFLow', 'myFlow' encountered a failure
  and could not start.
  
  BIP4761E: The message flow attempted to use 'SecurityProfiles'
  policy '{PolicyProj}:myLDAPProfile', which has not been defined
  in the integration server.
  
  or if Default_Propagation is specified as the policy then an
  error will not be seen but the user will see a node fail to
  propagate a userid/password as expected.
  
  For instance if a SOAPRequest node is expected to propagate a
  userid/password from the properties folder as BasicAuth then
  they would not see this happen.
  

Problem conclusion

• The product has changed to successfully resolve security profile
  policy references.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v11.0      11.0.0.3
  
  The latest available maintenance can be obtained from:
  http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
  
  If the maintenance level is not yet available,information on
  its planned availability can be found on:
  http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
  ---------------------------------------------------------------
  

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

  APP CONNECT ENT

• Fixed component ID

  5724J0550

Applicable component levels