Catalyst SDWAN / VIptela Logout API Method documentation does match

[Taylor Johnson]

Hello, 

We have found that the documentation for Catalyst SD WAN / Viptela claims the session log out call changed and requires a different HTTP method, however, in our testing, we have found this is not the case and "post" does not work in most cases. 

According to docs Between SD-WAN 20.11 and 20.12, the Authentication API used to logout was changed from GET to POST:

Authentication - SD-WAN API, Release 20.11 - Cisco DevNet

GET https://{vmanage-ip-address}/logout?nocache={random-number}`
HTTP Header: "Cookie: JESSIONID={session hash id}"

Authentication - SD-WAN API, Release 20.12 - Cisco DevNet

POST https://{vmanage-ip-address}/logout?nocache={random-number}`
HTTP Header: "Cookie: JESSIONID={session hash id}"

We re-tested and confirmed the “POST” logout option does not work against the devnet 20.10 Always On instance. Although it used to work back in November. We have also tested against a real 20.12 vManage where post doesn't work. 

The Cisco 20.12 documentation still indicates “POST” as the option for logout. And the Cisco bug tracker still indicates “get” was changed to “post” in 20.12.1:

https://bst.cisco.com/quickview/bug/CSCvv15134

Has anyone else encountered this? 

Thanks!

[bigevilbeard]

Not seen this one, in the past I was using GET did not know it was updated to POST. I had a sort of same issue with ping, in the end I had to use developer tools to capture what the API was doing under the hood of the UI, the doc weren’t even close even the docs in /apidocs on the device were incorrect. If I’m doubt the at was my default method to check.