IBM Support

IT27195: SECURITY PROFILES POLICY LOOKUP FAILS IN MULTIPLE SCENARIO

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

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

Temporary fix

Comments

APAR Information

  • APAR number

    IT27195

  • Reported component name

    APP CONNECT ENT

  • Reported component ID

    5724J0550

  • Reported release

    B00

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-12-05

  • Closed date

    2019-05-14

  • Last modified date

    2019-05-14

  • 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

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSDR5J","label":"IBM App Connect Enterprise"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"B00","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
14 May 2019