The request failed with http status 401: unauthorized

[cdnadmin]

This document was generated from CDN thread

Created by: Syed Ahmed on 13-03-2010 12:34:11 AM
Hi,
I am using .Net AXLAPIService.cs  class to  query CUCM 6.x. I used the wsdl.exe to generate the .Net code and related stubs. I made all the changes to the generated code as per the instructions in the read me file. When I send a request 
ListPhoneByNameReq
<font size="2" color="#008080"><font size="2" color="#008080">
 
</font></font><font size="2" color="#008080">
 
</font>
I am getting authenticagtion failure.  Can one any help what I may be doing wrong
 
Thanks
 
 <font size="2" color="#0000ff"><font size="2" color="#0000ff">
private
</font></font><font size="2" color="#0000ff">
 
</font>
void getPhoneList()
{
<font size="2">
 
</font>
string ServerNameOrIPAddress = "xx.xx.xx.xx";<font size="2">
 
</font>
string UserName = "user";<font size="2">
 
</font>
string Password = "password";<font size="2">
 
</font>
AXLAPIService axlService = new AXLAPIService(ServerNameOrIPAddress, UserName, Password);<font size="2">
 
</font>
ListPhoneByNameReq listPhone = new ListPhoneByNameReq();<font size="2">
listPhone.searchString =
</font>
"%";<font size="2">
 
</font>
ListPhoneByNameRes result = axlService.listPhoneByName(listPhone);
 
<font size="2">
System.
</font>
Console.WriteLine(result.ToString());
}

Subject: RE: The request failed with http status 401: unauthorized
Replied by: Paul Wilkinson on 17-03-2010 12:46:39 AM
Hi,
 
Have you granted the AXL role to the end user or application user that you are using to authenticate?
 
Note, that by default this role is not associated with a group, so you will need to create a new group, add the AXL role to this group and then make your user a member of the group.
 
You can test your user's permission to run AXL by accessing https://yourserver:8443/axl/  from a browser.  You should get prompted for a username and password.  Once you enter this you should see a message stating the AXL is ready.
 
One other thing to check is that the AXL service has been started on your publisher server - by default this service is not active.  Check from the servicability page in CCMAdmin.
 
Paul