Reputation: 1095
This question is, hopefully, fairly simple.
I have a Web service that I'm querying, https://myip:8443/AXL
, in this case the application in question is a CUCM server. I know it provides a SOAP API for querying and I'm trying to use new-webserviceproxy
to connect to it.
Unfortunately WSDL and SOAP are a little opaque to me. I'm relatively confident that the problem is that I'm trying to connect to the wrong uri but at this point I don't know enough to understand what I'm doing wrong.
Here's my command:
New-WebServiceProxy -Uri https://myip:8443/axl?WSDL -Credential ($AXLCred)
it returns the following error:
New-WebServiceProxy : The request failed with HTTP status 401: Unauthorized.
just in case you're concerned my credentials are the problem the following command works fine:
Invoke-WebRequest -Uri https://myip:8443/axl/ -Credential ($AXLCred)
Upvotes: 2
Views: 2205
Reputation: 1
$AXL = New-WebServiceProxy -Uri ($scriptPath + "\AXLAPI.wsdl") -Credential $MyCreds
the WSDL file is not available via http you need to catch if from the downloaded AXL toolkit
Upvotes: 0
Reputation: 1114
Here is a list of WSDL locations.
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/devguide/5_0_4/ccmdev/ccmdvCh2.html#wp96739
Upvotes: 2
Reputation: 3341
I'm assuming this is Cisco UC stuff, which is documented here: http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/devguide/6_0_1/cucm_devguide/ccmdvCh1.html#wp37665
From the doc, it should be basic auth all the way, which PowerShell should handle without problems. My first stop would be to perform a fiddler or wireshark trace of the two requests and check if authentication headers differ.
Upvotes: 2