Tag :: Authentication

EOS 4.22.1F adds support for disabling the IS IS authentication check for received IS IS PDUs. By enabling this

LDP per-neighbor authentication provides greater flexibility in the authentication of LDP routers in a network. Individual routers or groups of routers may be configured with different passwords to enhance security and to ensure certain routers do not exchange MPLS

This feature provides support for SPIFFE-ID in OpenConfig. The SPIFFE-ID will take precedence over any metadata usernames or common name username found. This username will be used for all AAA operations. 

The OSPFv2 Secure Hash Algorithms (SHA) Authentication support as defined in RFC 5709 supports the configuration of

This document describes the support for authenticating users using SSH certificates and the authorized principals command in EOS. SSH certificate authentication was previously restricted to just using the authorized principals file. This file is populated by configuring authorized principals for each user. In order to login with a SSH certificate a user must present a certificate that includes at least one of their configured principals. The authorized principals command allows this list of configured principals to be generated by an executable dynamically at runtime. This provides a more flexible and scalable way to perform SSH certificate authentication.

This document describes the support for performing SSH authentication with X.509 certificates. Authentication to SSH can be completed using a number of different methods. Public key, password and keyboard interactive are supported in EOS. Certificate login is a type of public key authentication in which the public key does not have to be stored on the server. Instead trusted certificate authorities are installed. A presented certificate must be signed either directly or indirectly by one of these trusted certificate authorities to allow authentication to the device. Support for OpenSSH certificates (also known as SSH Certificates) was added in 4.22.1F.

This feature adds support for configuring multiple authentication keys each with a specified lifetime using a shared secret profile. With a shared secret profile, a current key (key having the most recent start time) is automatically picked as per the lifetime specified. Authentication types supported are MD5 and SHA. The feature can be configured at both global and interface level. SHA algorithms supported are SHA-1, SHA-224, SHA-256, SHA-384 and SHA-512.