napalm-ros
napalm-ros copied to clipboard
Support additional SSL context parameters for Netbox
New optional_args for Netbox
- When netbox_default_ssl_params is set to True:
-
- verify_certificate - if specified and set to False (default is True), the MikroTik certificate will not be checked for trust, meaning the common name doesn't need to match the device being connected to, and the issuing CA doesn't need to be trusted (use this if the certificate is set to none in the api-ssl service on the MikroTik)
-
- check_hostname - if specified and set to False (default is True unless the device being connected to is via IP Address not Hostname), the certificate common name doesn't need to match the device being connected to
-
-
ca_certificate - if specified (as a Base64 string e.g.
Mw9THGWGW........saW6Ttg==
), the MikroTik certificate will be checked it has been issued by this CA
-
ca_certificate - if specified (as a Base64 string e.g.
- username and password - allows overriding the otherwise global NAPALM credentials with device specific credentials (Netbox limitation)
So netbox passes params in optional_args per device group or for single one ?
So netbox passes params in optional_args per device group or for single one ?
Per device "platform", you can use that to group devices, or use per device if you wish.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
Do you want me to do anything further with this?
Sorry for not responding.
After revisiting and rereading all netbox specific features, I have some thoughts. napalm-ros
allows for passing ssl contexts as well as username and password. There is no need to add custom logic if netbox
things. It is just a matter of time when some one comes and asks to change e.g. ssl context because they don't use host cert verification while someone wants to use it.
I'd prefer for netbox (and others) to use already existing functionality. Please contact netbox developers and override any required params there.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.