Thanks for the information David.I had a concern as in the documentation for AXL services it was mentioned that :
"CautionThe AXL API allows you to modify the Cisco Unified Communications Manager system database. Use caution when using AXL because each API call affects the system. Misuse of the API can lead to dropped calls and slower performance. AXL should act as a provisioning and configuration API, not as a real-time API."
(1)I am not sure as to how big of an impact is an authentication request on the system.Do you have any views on this?
(2)The HTTP basic authentication response itself is an indicator of authentication. Is there any specific reason for this webservice call or does it do the same thing conveniently wrapped as a WS call?
Thanks.
The AXL SOAP API has <doAuthenticateUser>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns="http://www.cisco.com/AXL/API/7.0">
<soapenv:Header/>
<soapenv:Body>
<ns:doAuthenticateUser sequence="1">
<userid>testUser</userid>
<password>password</password>
</ns:doAuthenticateUser>
</soapenv:Body>
</soapenv:Envelope>
----------------------
<SOAP-ENV:Envelope SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header/>
<SOAP-ENV:Body>
<axl:doAuthenticateUserResponse sequence="1" xmlns:axl="http://www.cisco.com/AXL/API/7.0" xmlns:xsi="http://www.cisco.com/AXL/API/7.0">
<return>
<userAuthenticated>true</userAuthenticated>
<code>0</code>
</return>
</axl:doAuthenticateUserResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
