๐ŸŒ
Portal Docs
  • โœจOverview
  • ๐Ÿ“ŠDashboards
    • ๐Ÿ“ˆTraffic Overview
    • ๐Ÿ”Analysis
    • ๐Ÿ”ดPaths Attacked
    • ๐Ÿ‘๏ธโ€๐Ÿ—จ๏ธKnown Bots
    • โšกResponse Overview
    • โšกChallenge Performance
    • โšกTop Attack Sources
    • ๐Ÿ”ฌProfiling
    • ๐Ÿ”ฌDetails
    • ๐Ÿ”POV Report
  • โœ๏ธManagement
    • โ€ผ๏ธQuarantine
    • โ˜‘๏ธTrusted List Management
    • ๐Ÿ“ƒAudit Trail
  • ๐ŸงฎConfiguration
    • โš™๏ธDatastream Configurations
      • ๐Ÿ› ๏ธIntegration details
      • ๐Ÿ‘พChallenge configuration
      • ๐Ÿ”งThreat and Trust Lists
  • ๐Ÿ‘ฅUser Management
    • Single Sign On (SSO)
      • SAML SSO Setup
      • Okta SSO Setup
      • Entra ID SSO Setup
      • SSO FAQs
    • IP Restriction
  • โ”Glossary of Terms
  • ๐Ÿ“—User Guides & Videos
    • Portal Setup & Log Shipping Guide
  • ๐Ÿง™โ€โ™€๏ธCustomer Service Desk
  • ๐Ÿ“–Integrations Documentation
  • Release notes
    • Version 1.7
    • Version 1.6
    • Version 1.5
    • Version 1.4
    • Version 1.3
    • Version 1.2
    • Version 1.1
    • Version 1
Powered by GitBook
On this page
  • How SAML SSO works
  • What happens after enabling SSO?
  • Configuring SSO
  1. User Management

Single Sign On (SSO)

With SAML-based single sign-on (SSO), users can access the Netacea customer portal (Atlas) through an identity provider (IdP) of their choice

SSO is a standard feature of the Netacea Portal available to all customers

How SAML SSO works

  1. When an Atlas user tries to log in to Atlas using SSO, Netacea sends a SAML (Security Assertion Markup Language) request to the identity provider (IdP)

  2. The identity provider validates the userโ€™s credentials and sends a response back to Netacea to confirm the member's identity

  3. Netacea acknowledges the response and grants access, allowing the member to log into their Atlas account

What happens after enabling SSO?

Enabling SSO for the first time

The first time you set up SSO, existing users can keep working in Atlas without interruption. However, the next time they log out, their session expires, or they try to log in from a new device, they can sign in via SSO.

Username and Password log in will still be available for all existing users. However it is recommended that the Admin who sets up SSO disables the original user accounts.

For new users to Atlas and those that do not have an existing account with a username and password there is no work that's required, they can simply log on via SSO.

User creation for SSO

When users login via SSO for the first time, they will automatically have a new user record created for them, which is distinct from their Username and Password log in (if they had one previously). We recommend that the User Admin keeps both accounts so they can retain access if SSO is misconfigured.

New users are by default set to have Read Only permissions. Prior settings from the Username and Password login are not copied over to the new user record.

User records can be managed using the User Management section of the Atlas portal.

Configuring SSO

Netacea supports SAML 2.0 compliant SSO integrations. See the sections below to guide your setup.

If your IdP does not exist in the list below please contact our support team on support@netacea.com for more information.

PreviousUser ManagementNextSAML SSO Setup

Last updated 9 months ago

๐Ÿ‘ฅ
Cover

SAML Setup

Cover

Okta

Cover

Microsoft Entra ID