Guest

Preview Tool

Cisco Bug: CSCvu93393 - Multitenant vManage may send CSR to wrong VA

Last Modified

Aug 29, 2020

Products (1)

  • Cisco SD-WAN

Known Affected Releases

20.1 20.1.0

Description (partial)

Symptom:
vManage may send CSR to wrong VA(Virtual Account).

example)
vManage has the following tenants.
- tenant1
- tenant2
- tenant3

Customer has the following VA.
VA-provider : VA for provider
VA-tenant1 : VA for tenant1
VA-tenant2 : VA for tenant2
VA-tenant3 : VA for tenant3

vManage should send CSR for tenant1's vsmart to VA-tenant1, but vManage may send CSR to VA-provider or VA-tenant2 or VA-tenant3.
Similary, vManage should send CSR for tenant2's vsmart to VA-tenant2, but vManage may send CSR to VA-provider or VA-tenant1 or VA-tenant3.
Similary, vManage should send CSR for tenant3's vsmart to VA-tenant3, but vManage may send CSR to VA-provider or VA-tenant1 or VA-tenant2.
Similary, vManage should send CSR for vmanage and vbond to VA-provider but vManage may send CSR to VA-tenant1 or VA-tenant2 or VA-tenant3.

Conditions:
This issue happens only while using Multitenant vManage.
Use Cisco PKI.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.