EXOS v21 - SOAP/XML API

[Bryn_Sadler]

Hi, we've long been users of the XOS SOAP/XML API for provisioning tasks, but it seems to have changed in v21, since the CherryPy update of the web framework. The API endpoint used to be http(s):///xmlService, but this now just gives a 404. The WSDL and XSD files all seem to still be there. Can't find anything in the documentation, apart from the release notes acknowledge that the SOAP/XML functionality should still be there. Anyone know what the API endpoint is now?

[OscarK]

Is the user you tried an admin user ?

[Bryn_Sadler]

Hi Oscar, thanks for the response. We did get some feedback from TAC that there were errors with the version we were running, and xmlService was actually xmlservice with a lower S. I've booted a lab switch into the same version as you, and I'm able to use the Object-based APIs to pull port info etc, but the XOS APIs such as the execCLi you use above are failing with "Not a valid user". I've tested the same code against an older version (15.3), and it works fine. Using same creds for Object-based and XOS APIs. Do you know if the auth mechanism has been changed?

[OscarK]

Using a switch with v22.2 on it it seems to work without problems.
someone@host:~/work/EXOS-XML$ perl execCli.pl 10.116.3.22 admin "" "show ver"
Slot-1 : 800550-00-08 1626N-41812 Rev 8.0 BootROM: 1.0.2.1 IMG: 22.2.1.5
Slot-2 : 800554-00-07 1636N-41581 Rev 7.0 BootROM: 1.0.2.1 IMG: 22.2.1.5
Slot-3 :
X460-G2-VIM-2Q-B-1: 800555-00-03 1dddN-40658 Rev 3.0

Image : ExtremeXOS version 22.2.1.5 by release-manager
on Mon Feb 27 11:03:54 EST 2017

there are some bugs in 21.1 where login does not work and such, can you try wih 22.2 ?