Skip to main content

Cisco: Viptela v200 Py3 PowerPack Release Notification

  • March 20, 2025
  • 3 replies
  • 35 views

We are pleased to announce that the Cisco: Viptela v200 Py3 PowerPack has been released. The download for this release can be found on the Support Portal under the PowerPack filename:

https://support.sciencelogic.com/s/release-version/aBu0z000000XZMACA4/cisco-viptela

Enhancements and Issues Addressed

The following enhancements and addressed issues are included in this release:

  • Added the new "Cisco: Viptela Environment v200" Execution Environment to support conversion to the Snippet Framework.
  • Converted the PowerPack and all Dynamic Applications to support Python 3 using the Snippet Framework.
  • Added the new "Cisco SDWAN/Viptela" universal credential type and guided discovery workflow.
  • Made a number of updates to the "Cisco: Viptela Events" Dynamic Application: 
    • Consolidated functionality from the "Cisco: Viptela Events Caching" Dynamic Application into this Dynamic Application.
    • Added the new "API Alarms" collection object to trigger the API request.
    • Changed page size to 40 to reduce the number of requests made to the API.
    • Added a query parameter to reduce the number of alarms retrieved from the API to only those from the last hour. This can be customized in the snippet by adjusting the polling frequency.

NOTE: Upon upgrading from a version of this PowerPack using Python 2, duplicate alerts may be created due to incompatibility of the cached values from Python 2 to Python 3.

  • Deprecated the following Dynamic Applications:
    • Cisco: Viptela Token Configuration
    • Cisco: Viptela Events Caching
  • Added proxy support to the PowerPack.

NOTE: The HTTPS proxy scheme is only available using the new universal credential. Existing SOAP/XML credentials do not support switching the scheme.

Please refer to the Cisco: Viptela v200 Py3 PowerPack File Details in the PowerPacks section of the Support Portal for all information pertaining to the Cisco: Viptela v200 Py3 PowerPack Support Status, Minimum SL1 Version, Solution Information, and Pricing Information. The Cisco: Viptela v200 Py3 PowerPack Release File Details also contains links to the Release Notes, Manual, and PowerPack Info Report.

Issues Addressed in the Cisco: Viptela v200 Py3 PowerPack Release can be found in the Release Notes

3 replies

gbilwal
Forum|alt.badge.img
  • Contributor
  • September 28, 2026

Feature Request: Authentication Support Upgrade for Cisco Catalyst SD-WAN (Viptela v200) PowerPack

The Cisco Viptela PowerPack (v200) in Skylar One currently relies on basic username and password credentials, which no longer aligns with modern enterprise security standards or zero-trust architectures that require token-based access controls. As Cisco transitions toward cloud-managed Cisco SASE and SD-WAN solutions integrated with Duo MFA and Cisco ID SSO, adopting native API key and OAuth token-based authentication is essential to maintain seamless, high-assurance telemetry collection. We request the Skylar OEM product team treat this enhancement as a top priority, share the roadmap timeline for delivering API key support in the Catalyst SD-WAN PowerPack, and provide any recommended interim token-based credential configurations


Forum|alt.badge.img
  • Community Manager
  • September 28, 2026

As far as i know, Cisco's SD-WAN Manager (vManage) API does not currently expose a true API-key or OAuth client-credentials flow for machine-to-machine access. Username/password remains the root credential for every supported method, including the newer JWT bearer-token option introduced in 20.18.1. The OAuth endpoint Cisco does publish is for interactive SSO login (Cisco ID/Duo), not automated polling. So "native API key support" isn't something we can deliver ahead of Cisco offering it on their side.

What we're committing to instead, on the next Viptela PowerPack release (targeted for next month):
- Rework the PowerPack's credential handling to use short-lived JWT bearer tokens (30-minute default expiry, auto-refreshed) in place of persistent session cookies. The username/password remains the root secret, but it's sealed inside the credential object and re-minted automatically rather than kept alive as a long-running session.
 

If Cisco announces genuine client-credentials/API-key support on their side, we'll fold that in as a follow-on once available.  Let me know if i am missing something.

thanks

Leo


gbilwal
Forum|alt.badge.img
  • Contributor
  • September 28, 2026

I’m on 20.15 and able to download the API token with 10 years expiry from my profile. Will this be the right candidate to test? I’m still refering to Cisco SDWAN Cloud solution and not the on-prem.

 

This chapter describes how to acquire a Cisco API key and use Cisco APIs on a Cisco SD-WAN Cloud fabric in Cisco SD-WAN Cloud Release 20.15 and higher.

Please refer - https://www.cisco.com/c/en/us/td/docs/routers/sdwan/configuration/cloud-delivered-cisco-catalyst-sd-wan-getting-started-guide/api.html

Thanks