ExpertHi All,
Why in SL1 we have two credential type universal and native SOAP /XML where we discover via the respective SDN technology ?
What is recommended ones , when we create universal we can assign only to system ORG.
ModeratorHello Issac.
This is case specific. If you're referring to the Meraki PowerPack, the basic credential is the original one used, but as more features were added to the PowerPack, we needed to use a credential that had more fields for users to input values (such as tags) for discovery, so the Solutions group elected to use the SOAP/XML credential as there was not a a configurable credential type where new fields could be added.
Now the SL1 platform has the "universal credential" which allows a developer to add any number of arbitrary fields, so new PowerPack releases have the ability to use that. The latest version of the Meraki PowerPack released this year has the option for all three credentials, but we advise against using the basic credential since you will not be able to use all features in the PowerPack (like selective discovery), and we suggest users use the universal credential and guided discovery workflow if possible.
Similar cases exist across the PowerPack portfolio. The SOAP/XML credential was historically the most flexible one with the most fields. The universal credential now replaces that need.
Thanks,
Taylor
ExpertHi Taylor,
Thanks for the update , For guided discovery do we have rest api call to do it ,managing the complete workflow?
ModeratorHello Issac,
The guided discovery workflow is handled entirely in the UI. You select the Meraki icon and you are then prompted to fill in the required fields. SL1 will then create the root device and align the relevant DAs with the credential information you filled in.
That process is not relevant when changing a credential for an existing discovery.
Thanks,
Taylor
