Remedy - Consuming external Web Service authentication failed

Version 1
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    Remedy AR System Server


    APPLIES TO:

    9.x and above



    PROBLEM:

    Failed to consume an external web service that requires authentication from Remedy filter action.  
    User name and Password mapped accordingly in the filter set action, however the authentication info is missing in the soapheader  when request is sent to external WS and error returned is  "authentication failed". 

    Webservice log
    Thu Jun 27 00:14:04.801 2019 [pool-Fast-thread-2] DEBUG org.apache.http.wire  << "<s:Envelope xmlns:s="http://www.w3.org/2003/05/soap-envelope"><s:Body><s:SaveOutboundSMSResponse><s:SaveOutboundSMSResult>Authentication failed</s:SaveOutboundSMSResult></s:SaveOutboundSMSResponse></s:Body></s:Envelope>"

    Filter log

    inputDoc: 
    <?xml version="1.0" encoding="UTF-8"?><ns0:ROOT xmlns:ns0="http://www.w3.org/2003/05/soap-envelope" xmlns:ns1="urn" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
        <ns0:SOAPHeader>
            <ns1:AuthenticationInfo>
                <ns1:password>RFfi7u1oqxVYcqsgnB2BpRoUyr5R1WnoADhRZ2j3MwqihTtBGnxhNoOLRRX9RbgWtLQwggZMBaLgEAtIUndgXoqCpbo2qzFzvjg8YV/DejPCbJUC1hr2SQ==</ns1:password>
                <ns1:username>smsUser</ns1:username>
            </ns1:AuthenticationInfo>
        </ns0:SOAPHeader>
        <ns0:message>TESTING ONLY. PLEase ignore.aaa</ns0:message>
        <ns0:telephone>96638970</ns0:telephone>
    </ns0:ROOT>



     


    CAUSE:

    The third party that receives the web service required the authentication to be sent outside the header


    SOLUTION:

    When an authentication is used over the filter in Developer Studio, this will be sent over the SOAPHeader, as most of the standard web servers will read it from there.

    In this case there are two options

       
    • The provider of the external Web Service should read the authentication from the header as standard
    •  
    • If the authentication is required in the body you can map it statically over the filter with the matching xml element of username and password like the screenshot below
       User-added image

     


    Article Number:

    000170312


    Article Type:

    Solutions to a Product Problem



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles