You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
End point URL : "/dna/intent/api/v1/business/sda/authentication-profile"
Schema : siteNameHierarchy(string, required): Path of sda Fabric Site
authenticateTemplateName(string, required, enum: No Authentication , Open Authentication, Closed Authentication, Low Impact)
For authenticateTemplateName parameter , input string "No Authentication" [without white space at end] is failing at parameter validation.
Actual API call would still take both strings with and without white spaces.
Expected behavior
Api call should still happen as API accepts both strings with and without white.
Screenshots
Environment (please complete the following information):
Cisco DNA Center Version and patch: 2.3.6.0
Python version:3.6
SDK version:2.3.3
OS Version:
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
### Changed
- SDK implementation for API Add Edge Device to Sda fabric on DNAC Version 2.3.3.0 inconsistent with previous DNAC versions implementation #90
- Actual error message was not being used in case of exceptions #98
- SDA :: add_default_authentication_profile #97
- DNA_CENTER_VERIFY not being imported correctly from the environment #92, now you can export this as:
```zsh
export DNA_CENTER_VERIFY=false
export DNA_CENTER_VERIFY=true
```
Prerequisites
Describe the bug
End point URL : "/dna/intent/api/v1/business/sda/authentication-profile"
Schema : siteNameHierarchy(string, required): Path of sda Fabric Site
authenticateTemplateName(string, required, enum: No Authentication , Open Authentication, Closed Authentication, Low Impact)
For authenticateTemplateName parameter , input string "No Authentication" [without white space at end] is failing at parameter validation.
Actual API call would still take both strings with and without white spaces.
Expected behavior
Api call should still happen as API accepts both strings with and without white.
Screenshots
Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: