App Connect

 View Only
Expand all | Collapse all

Ws-security not working with latest fix pack 11.0.0.6 but working with all previous fix packs

  • 1.  Ws-security not working with latest fix pack 11.0.0.6 but working with all previous fix packs

    Posted Tue October 22, 2019 01:34 AM
    ​I have recently installed newly released fix pack 11.0.0.6, and one of our integrations uses ws-security stops working, it was working with IIB and ACE previous fix packs.    The error I am getting is:
    org.apache.axis2.AxisFault: CWWSS6521E: The Login failed because of an exception: javax.security.auth.login.LoginException: javax.security.auth.login.LoginException: Broker security manager failed to provide a username.

    The soap message didn't even send out but failed in soapRequst node.  I wonder if anybody happens to know what might have been changed for the soapRequest node in FP6?

    Thanks,
    andy

    ------------------------------
    Andy Mao
    ------------------------------


  • 2.  RE: Ws-security not working with latest fix pack 11.0.0.6 but working with all previous fix packs

    Posted Tue October 22, 2019 02:57 AM

    Hi Andy

    Sorry to hear you are facing this issue. Your message flow must have been providing some "username and password" credentials to the SOAPRequest node, perhaps propagated from the flow input node, or using a configured static ID, however for some reason they are not being picked up correctly anymore. I think it would be best to open a case with IBM support to get this resolved, so that they can advise you of the diagnostics we'll need to gather etc to determine the root cause.

    Thanks



    ------------------------------
    Martn Boag
    Software Developer
    IBM
    ------------------------------



  • 3.  RE: Ws-security not working with latest fix pack 11.0.0.6 but working with all previous fix packs

    Posted Tue October 22, 2019 01:00 PM
    ​thanks, Martn.  I have opened a PMR.

    ------------------------------
    Andy Mao
    ------------------------------



  • 4.  RE: Ws-security not working with latest fix pack 11.0.0.6 but working with all previous fix packs

    Posted Tue November 12, 2019 10:59 AM
    Andy, did you resolve this? I have a soap request that will apply a ws-secuiry policy that adds a username/password and wondering if I'll need a fix. Thanks

    ------------------------------
    Duke Star
    ------------------------------



  • 5.  RE: Ws-security not working with latest fix pack 11.0.0.6 but working with all previous fix packs

    Posted Tue November 12, 2019 11:45 AM
    ​Hi Duke, if you use STATIC ID in the Security Profile attaching to the soap request node for the ws-security username and password, then you will need this hot fix.  I just got the hot fix yesterday, and trying to make it work in Linux now.  Verified in my local env in windows.

    ------------------------------
    Andy Mao
    ------------------------------



  • 6.  RE: Ws-security not working with latest fix pack 11.0.0.6 but working with all previous fix packs

    Posted Tue November 12, 2019 05:34 PM
    ​The hot fix works.

    ------------------------------
    Andy Mao
    ------------------------------



  • 7.  RE: Ws-security not working with latest fix pack 11.0.0.6 but working with all previous fix packs

    Posted Tue November 12, 2019 11:08 PM
    Thanks Andy that's exactly what we do...do you have an apar number for the fix so I can request it from IBM support? Thanks

    ------------------------------
    Duke Star
    ------------------------------



  • 8.  RE: Ws-security not working with latest fix pack 11.0.0.6 but working with all previous fix packs

    Posted Wed November 13, 2019 12:55 PM
    TFP54763.  ​

    ------------------------------
    Andy Mao
    ------------------------------



  • 9.  RE: Ws-security not working with latest fix pack 11.0.0.6 but working with all previous fix packs

    Posted Wed November 13, 2019 12:56 PM

    QuickFixes ...

    11.0.0.6-ACE-WinX64-TFP54763

    11.0.0.6-ACE-LinuxX64-TFIT30901

     

    . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
    Hirschel Wasserman

     


    This email and any attachments are intended only for the named recipient and may contain confidential and/or privileged material. Any unauthorized copying, dissemination or other use by a person other than the named recipient of this communication is prohibited. If you received this in error or are not named as a recipient, please notify the sender and destroy all copies of this email immediately.

    Insurance Corporation of British Columbia | 151 W. Esplanade | North Vancouver | V7M 3H9
    Contact Us






  • 10.  RE: Ws-security not working with latest fix pack 11.0.0.6 but working with all previous fix packs

    Posted Wed November 13, 2019 01:13 PM
    Is there an AIX fix or is the problem not happening with AIX?

    Thanks

    ------------------------------
    Duke Star
    ------------------------------



  • 11.  RE: Ws-security not working with latest fix pack 11.0.0.6 but working with all previous fix packs

    Posted Wed November 13, 2019 01:48 PM
    ​We only ask IBM to provider the fix for Window and Linux, you may reach out to IBM for the AIX fix.  thanks.

    ------------------------------
    Andy Mao
    ------------------------------



  • 12.  RE: Ws-security not working with latest fix pack 11.0.0.6 but working with all previous fix packs

    Posted Tue May 26, 2020 09:59 AM
    Hi Andy, How you are deploying the WS-Security policy, it seems there is a different way to do comparing to what we use to do in IIB 10, How we can add the policy to Integration node.

    ------------------------------
    Waleed Husni
    ------------------------------



  • 13.  RE: Ws-security not working with latest fix pack 11.0.0.6 but working with all previous fix packs

    Posted Tue May 26, 2020 12:21 PM
    ​Hi Waleed, just like you said, there are a number of ways setting up WSSecurity. In my case,  I created WS_PolicySet and WS_PolicySetBinding in the DefaultPolicies project, then created WSSecurity_SecurityProfile in the DefaultPolicies, where I specified value WSSecurityID for property Transport propagation configuration.    Then you run mqsisetdbparms {Node} -n WSSecurityID -u username-p password to register your credential.  
    After your application bar is created, you run mqsiapplybaroverride to assign WSSecurity_SecurityProfile, WS_PolicySet and WS_PolicySetBinding to SoapRequest node corresponding properties.  

    The last step, deploying DeafultPolicies, deploying application bar.  
    Hope it helps,

    andy


    ------------------------------
    Andy Mao
    ------------------------------



  • 14.  RE: Ws-security not working with latest fix pack 11.0.0.6 but working with all previous fix packs

    Posted Tue May 26, 2020 01:04 PM
    ​This is what I did, but I wonder if there is a way to do it outside of the default policy project, so you can assign the policy set and the binding in another policy project.

    Since I have faced similar limitation in the database inside the mapping node, the JDBC policy should be in the default policy project, but if you use Javacompute node you can specify the Policy Project. I hope there is a solution to reference different policy project for WS-Security policy.

    ------------------------------
    Waleed Abu Yahia
    ------------------------------



  • 15.  RE: Ws-security not working with latest fix pack 11.0.0.6 but working with all previous fix packs

    Posted Tue May 26, 2020 01:08 PM
    ​Yeah, I am totally with you.  Hopefully in the future fix pack, we can use policy defined in other policy projects anywhere in the ACE.

    ------------------------------
    Andy Mao
    ------------------------------



  • 16.  RE: Ws-security not working with latest fix pack 11.0.0.6 but working with all previous fix packs

    Posted Thu June 04, 2020 01:19 PM
    Hi All,

    in order to reference the ws-security policy set and policy set binding where they are not deployed as a part of the default policy project you have to do the followings:

    1- Create Policy Project and add your policy set
    2- Deploy the policy project as normal policy project not default policy project
    3- in the BAR file reference the policy set and policy set bindings  by prefix the policy name with project name it will be {PolicyProjectName}:PolicySetName same for policy set bindings. 


    ------------------------------
    Waleed Husni
    ------------------------------