✨ New: Try our AI‑powered Search (Ctrl + K) — Read more

Configure User Authentication on Docker

Prev Next

The Sensor Management web user interface only supports ZITADEL-based user authentication.

This section explains how to log in to Sensor Management Docker using a ZITADEL account.

Configure ZITADEL Before Logging In

ZITADEL is the Identity Infrastructure for Developers.

Refer to ZITADEL's documentation for details.

Reference version: 4.15.1

Creating the Organization on the ZITADEL server

Refer to Organizations for details.

Prerequisites

  • User can access ZITADEL Console.
  • User has permission to create/manage organizations, for example INSTANCE_OWNER.
  • ZITADEL URL is available, for example:

https://<zitadel-domain>/ui/console

Steps

  1. Open supported browser and access ZITADEL Console:

https://<zitadel-domain>/ui/console

  1. Log in to ZITADEL Console.
    Log in with an administrator account.

  2. Open Organization Menu.

    a. In the top header, click the Organization dropdown.
    b. Select + New Organization.

  3. Input Organization Information.

    a. Enter the organization name.

Example: Orchestrator

b. Select the initial administrator option:

Current User: Use the currently logged-in user as the organization manager.

New Account: Create a new user account to manage this organization.

Recommended option: Current User

  1. Create Organization.

    a. Click Create.
    b. Wait until the organization is created successfully.
    c. The new organization should appear in the organization list/dropdown.

Creating the ZITADEL Project: Manage Apps, Services & Roles

Refer to ZITADEL Projects: Manage Apps, Services & Roles for details.

The idea of projects is to have a vessel for all components who are closely related to each other. Multiple projects can exist within an organization.

Image

All applications within a project share the same roles, grants, and role assignments:

  • Applications initiate the authorization flow. They could be a web application and a mobile application that share the same roles.
  • Roles define the access rights of a project and can be assigned to users.
  • Role Assignments define the association between users and their roles within a project.

A Project is the vessel that holds your Applications and Roles. It defines the security context for a specific software solution.

Create a Project

  1. Navigate to your Organization in the Console.
  2. Go to Projects.
  3. Click the Create New Project button.
    Image
  4. Input your Project name.
  5. Click the Continue button.
  6. Check on Return user roles during authentication option.
  7. Click Save button.

Creating the ZITADEL Applications

Refer to Applications for details.

Applications are the entry point to your Project Overview. Users either log in to one of your applications (Frontend) and interact with them directly or use one of your APIs (Backend).

All applications within a project share the same Roles and Role Assignments. This means you define a role once (e.g., admin) on the Project level, and it applies across all your web, mobile, and API applications.

Create an Application

  1. Navigate to your Project in the Management Console and select your application.
    Image

  2. Click the New button and select your Application Type: WEB.
    Image

  3. Click Continue button.

  4. Select the Authentication Method: PKCE.
    Image

  5. Input the redirect URI is where the ZITADEL authorization server redirects the user after they have been authenticated.

    • Redirect URIs: https://<server_IP>/businessweb/login/oauth2/code/zitadel
    • Post Logout URLs: https://<server_IP>/businessweb
  6. Click Continue button.

  7. Click Create button.

Application Settings

After creating an application, you can modify its settings.

  1. OIDC Compliance: The Management Console checks if your settings are OIDC compliant and shows tasks for completion if anything is missing.

    • Response Types: Code
    • Authentication Method: None
    • Grant Types: Authorization Code and Refresh Token
    • Check on Refresh Token

Image

  1. Token Settings
  • Using the Token with

    • Auth Token Type: JWT

    • All three following settings must be checked

      • Add user roles to the access token
      • User roles inside ID Token
      • User Info inside ID Token

Creating the Roles in the Project

After the ZITADEL server authenticates a user, it sends Cisco Crosswork Assurance Sensor Management a list of roles for the user. The user roles must be among the roles recognized by Cisco Crosswork Assurance Sensor Management. See "Managing User Accounts".

Your ZITADEL server must be configured to send the list of roles to Cisco Crosswork Assurance Sensor Management after authentication.

To add roles, navigate to the section Roles and create those new roles with the following values:

  1. Click New button.
    Image
  2. Input all information below to create 6 supported Roles.
Key Display Name Group
ROLE_USER ROLE_USER USER_GROUP
ROLE_ADMIN ROLE_ADMIN ADMIN_GROUP
ROLE_OPERATOR ROLE_OPERATOR OPERATOR_GROUP
ROLE_FW_MGMT ROLE_FW_MGMT FW_MGMT_GROUP
ROLE_VIEWER ROLE_VIEWER VIEWER_GROUP
ROLE_WS ROLE_WS WS_GROUP
  1. Click Save.

All 6 supported roles will be displayed.
Image

Configuring ZITADEL to Add Authorizations for the Project

If ZITADEL sends any roles that Cisco Crosswork Assurance Sensor Management does not recognize, the login to the Cisco Crosswork Assurance Sensor Management will fail. If the resulting list of roles is empty or if ZITADEL sends an empty list, Sensor Management will deny access to the user.

At authentication time, the ZITADEL user must be assigned one of the following roles below for the Roles Assignments configuration in the ZITADEL:

  • ROLE_USER, ROLE_ADMIN
  • ROLE_USER, ROLE_OPERATOR
  • ROLE_USER, ROLE_FW_MGMT
  • ROLE_USER, ROLE_VIEWER
  • ROLE_USER, ROLE_WS

Obtaining OAuth/OIDC Endpoints from ZITADEL

All standard OAuth/OIDC endpoints can be automatically discovered from the OpenID Connect Discovery document.

Image

Before enabling ZITADEL authentication using the Cisco Crosswork Assurance Sensor Management CLI, ensure that the required OAuth/OIDC configuration values have been obtained from the ZITADEL server.

These values are used to configure the connection between Cisco Crosswork Assurance Sensor Management and ZITADEL, allowing users to authenticate through the OpenID Connect (OIDC) protocol.

The following parameters must be collected from the ZITADEL deployment before executing the authentication configuration commands.

Configuration Property Description How to Obtain Discovery Endpoint Field
client-id The Client ID of the application registered in ZITADEL. This identifier is used by the application when communicating with the ZITADEL authorization server Navigate to ZITADEL Console → Projects → Applications → Select Application → Client ID.
project-id This value is required so that the system can reference the correct ZITADEL project during authentication setup and related management operations Navigate to ZITADEL Console → Projects → Select the target project → Project ID
issuer-location The issuer URL of the ZITADEL OIDC provider. This value is used to validate tokens and verify the identity provider Open OIDC discovery and copy the value of the issuer field. issuer
authorization-uri The authorization endpoint where users are redirected to authenticate Open the OIDC discovery document and copy the value of authorization_endpoint authorization_endpoint
token-uri The token endpoint used to exchange an authorization code for access tokens, ID tokens, and refresh tokens Open the OIDC discovery document and copy the value of token_endpoint token_endpoint
user-info-uri The UserInfo endpoint used to retrieve authenticated user information such as username, email address, and profile attributes Open the OIDC discovery document and copy the value of userinfo_endpoint userinfo_endpoint
jwk-set-uri The JSON Web Key Set (JWKS) endpoint containing the public keys used to validate JWT signatures issued by ZITADEL Open the OIDC discovery document and copy the value of jwks_uri jwks_uri

Enable ZITADEL Authentication

The OAuth CLI enables configuration of OAuth 2.0 / OpenID Connect (OIDC) authentication for end users, including setting up the identity provider connection, authorization and token endpoints, role mapping, and remote authentication management.

Note

Sensor Management Docker only supports connecting to ZITADEL servers using HTTPS. HTTP connections are not supported.

  1. Open an SSH terminal session to the Cisco Crosswork Assurance Sensor Management CLI on port 2200.
  2. Log in as the skylight user.
  3. Enter the command below to show current OAuth configuration:
oauth show
  1. (Optional) If the ZITADEL server uses a self-signed certificate, import and trust the certificate:
certificate import trusted-cert-file <certificate_file> alias <alias_name>
  1. Enter the commands below:
oauth edit enabled true
oauth edit client-id <client_id>
oauth edit project-id <project_id>
oauth edit issuer-location https://<zitadel_domain>
oauth edit authorization-uri https://<zitadel_domain>/oauth/v2/authorize
oauth edit token-uri https://<zitadel_domain>/oauth/v2/token
oauth edit user-info-uri https://<zitadel_domain>/oidc/v1/userinfo
oauth edit jwk-set-uri https://<zitadel_domain>/oauth/v2/keys
  1. Enter the command below to show OAuth configuration again:
oauth show
  1. Stop the Cisco Crosswork Assurance Sensor Management services by entering:
services stop
  1. Start the Cisco Crosswork Assurance Sensor Management services by entering:
services start

Note: Wait about 10 minutes to ensure all services are healthy.

Log In Using a ZITADEL Account

Administrators define user accounts in the ZITADEL server. When you have your account, you can log in as explained below.

This section explains how to configure and log in to the Cisco Crosswork Assurance Sensor Management.

To log in to Sensor Management

  1. Open a supported browser. See the list of "Supported Web Browsers".

  2. Enter the following URL in the browser's address bar: https://<serverIPaddress>/businessweb
    The login dialog is displayed.
    Image

  3. Click Remote Log in button.
    The login dialog is displayed.
    Image

  4. Enter your ZITADEL Username and Password.

  5. Click Next.

Automatic Creation of ZITADEL Users in Sensor Management

When a user logs in to Sensor Management using a ZITADEL account, a corresponding Sensor Management user account (with User Type set to OAUTH_JWT) is automatically created in the Sensor Management data store.

These OAUTH_JWT user accounts cannot be converted to LOCAL or RADIUS users in Sensor Management.

The Admin ▶ Users page displays operational data on ZITADEL authentication.

© 2026 Cisco and/or its affiliates. All rights reserved.

For more information about trademarks, please visit:
Cisco trademarks 
For more information about legal terms, please visit:
Cisco legal terms