Tutorials · Security

How to Add Single Sign-On (SAML or OpenID Connect) to Network Management

Let engineers sign in to firewalls, controllers and cloud dashboards with company accounts and MFA: choose SAML or OpenID Connect, map groups to roles and keep an emergency login.

Intermediate15 min7 steps

Quick answer

Single sign-on (SSO) moves admin logins from many local password databases to one identity provider (IdP), such as Microsoft Entra ID, Okta or Google Workspace. People sign in once with MFA, and disabling a leaver's company account removes their network access everywhere.

SAML 2.0 and OpenID Connect (OIDC) are the two standard protocols. Use whichever your management platform supports. Many support both.

Key terms

Identity provider (IdP)
The system that holds user accounts and performs authentication and MFA.
Service provider (SP) / relying party
The application the admin signs in to, such as a firewall GUI or cloud dashboard.
SAML assertion
A signed XML statement from the IdP saying who the user is and which groups they belong to.
OIDC ID token
A signed JSON Web Token (JWT) with the same purpose, built on OAuth 2.0.
Federation
Trust between organisations or systems so one login works across them.

Before you start

  • An identity provider with MFA enabled
  • A management platform that supports SAML or OIDC
  • Groups in the IdP for each admin role

Step by step

  1. Create the application in the IdP

    Add a SAML or OIDC app. Enter the SP's entity ID and assertion consumer service (ACS) URL, or its redirect URI for OIDC.

  2. Exchange metadata

    Import the IdP metadata (or issuer URL and client ID) into the management platform, and the SP metadata into the IdP.

  3. Send group claims

    Configure the IdP to include group membership in the assertion or token.

  4. Map groups to admin roles

    In the platform, map 'net-viewers' to read-only, 'net-engineers' to engineer, and so on. Unmapped users get no access.

  5. Enforce MFA and conditional access

    Require phishing-resistant MFA and allow admin access only from managed devices or trusted locations.

  6. Keep an emergency login

    Keep one local admin per platform for IdP outages, stored in a vault and alerted on use.

  7. Test joiner, mover and leaver

    Add a test user to a group, change the group, then disable the account. Confirm access changes each time.

Pro tips

  • SSO is only as strong as the IdP. Protect IdP admin accounts with hardware security keys.
  • Prefer SP-initiated login, and set a short session lifetime for admin portals, such as 8 hours.

SAML vs OpenID Connect

SAML 2.0OpenID Connect
FormatSigned XML assertionsSigned JSON Web Tokens
Built onIts own XML frameworkOAuth 2.0
Best forEnterprise web apps, older admin portalsModern web and mobile apps, APIs
Typical IdPsEntra ID, Okta, ADFS, GoogleEntra ID, Okta, Google, Keycloak

Last reviewed:

FAQ

Frequently asked questions

What is the difference between SAML and OAuth?

SAML is for authentication (signing users in). OAuth 2.0 is for authorization (granting an app access to an API). OpenID Connect adds an authentication layer on top of OAuth 2.0.

Does SSO replace TACACS+ for switches?

Not usually. Web dashboards and cloud platforms use SAML or OIDC. Device CLIs still use TACACS+ or RADIUS, which can themselves check passwords against the same directory.

Stuck on a step?

Ask Navijin technical support or an authorised partner for help with your configuration.