Would be great to allow the option to setup authentication for Hyperglass before allowing the user to run commands on devices. This will put one additional security layer on the application for more sensitive data that will be displayed by the commands run on the devices.
Feature Type
New Functionality
Use Case
I'm currently building an Hyperglass and have setup a directive that allows users to send any "show commands" to a network device. Since this is no longer using the default Looking Glass commands (Ping, Trace, BGP Route and As-Path) it would be great if we can enable an application authentication using LDAP and LDAPS so only users allowed run commands on these devices.
This will enhance security policies in most companies and will be allowed to get approved faster. Also will allow to have an audit logs of authentication to the server and who is using it.
Version
v2.0.4
Feature Details
Would be great to allow the option to setup authentication for Hyperglass before allowing the user to run commands on devices. This will put one additional security layer on the application for more sensitive data that will be displayed by the commands run on the devices.
Feature Type
New Functionality
Use Case
I'm currently building an Hyperglass and have setup a directive that allows users to send any "show commands" to a network device. Since this is no longer using the default Looking Glass commands (Ping, Trace, BGP Route and As-Path) it would be great if we can enable an application authentication using LDAP and LDAPS so only users allowed run commands on these devices.
This will enhance security policies in most companies and will be allowed to get approved faster. Also will allow to have an audit logs of authentication to the server and who is using it.