So it turns out I was handling authentication correctly. Instead, my problem is that it looks like AR System is attempting to send SOAP 1.1 rather than SOAP 1.2, even though the BMC documentation says that it should be able to consume 1.2. However, I am apparently able to authenticate correctly, so I will wait to hear back from BMC support on this issue.
Thanks, Shawn Pierson Remedy Developer | Energy Transfer From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Jason Miller Sent: Tuesday, September 22, 2015 3:47 PM To: [email protected] Subject: Re: How to Replicate Basic Authentication in Web Service Filter ** Just to double check... You specified the Username Token for the Authentication type and supplied the username/pass in the mapping under SOAPHeader? [9-22-2015 1-41-33 PM.jpg] The way I understand the Login button is it is only used to authenticate to get to the WSDL (if required). It is the credentials you put in the mapping that will actually be used in the WS call. Jason On Tue, Sep 22, 2015 at 12:48 PM Pierson, Shawn <[email protected]<mailto:[email protected]>> wrote: ** I'm running into an issue using a Filter to query a web service. However, I am able to connect to the web service in SoapUI. Basically, in SoapUI I go to the Authentication tab on the request and set it up to pass the Username and Password. However, I am unable to do something similar in the Filter. Following the advice that I found on https://communities.bmc.com/message/438480 I tried using the Login... button to add the Username and Password there. I also set up the mapping in the Set Fields to be passing the same data between SoapUI and the Set Fields on this Filter. However, when I execute the Filter I get a message stating: ARERR [9130] Error encountered while executing a Web Service : [ISS.0088.9117] One or more header entries were not understood by the SOAP processor Another thing I've done, which probably doesn't matter in this case, is downloaded a version of the certificate used by the server and added it to my Remedy server's Java Key Store file, but I don't think that's necessary with this even though it is using HTTPS. Does anyone have any other suggestions that I may be able to try to resolve this issue? I believe the problem is purely in the authentication within the header. I'm still waiting to hear back from the vendor but since they're not a Remedy shop they probably can't help me, especially since I am able to connect successfully from other tools. Thanks, Shawn Pierson Remedy Developer | Energy Transfer Private and confidential as detailed here<http://www.energytransfer.com/mail_disclaimer.aspx>. If you cannot access hyperlink, please e-mail sender. _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: "Where the Answers Are" and have been for 20 years_ Private and confidential as detailed here: http://www.energytransfer.com/mail_disclaimer.aspx . If you cannot access the link, please e-mail sender. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
