Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
Software Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive
Help Center/ Cloud Bastion Host/ FAQs/ About CBH System Login/ Login Methods and Password Issues/ Which Login Authentication Methods Are Available in a CBH System?

Which Login Authentication Methods Are Available in a CBH System?

Updated on 2024-04-24 GMT+08:00

A CBH system supports local authentication, multi-factor authentication, and remote authentication. Multi-factor authentication includes mobile one-time password (OTP), mobile SMS, USB key, and OTP token methods. Remote authentication includes Active Directory (AD) domain, Remote Authentication Dial-In User Service (RADIUS), Lightweight Directory Access Protocol (LDAP), and Azure AD methods.

NOTE:
  • After a multi-factor authentication method is enabled, the local authentication becomes invalid. The CBH system can be logged in through the enabled multi-factor authentication method instead of usernames and passwords.
  • If more than one multi-factor authentication methods are enabled for a system user, they can log in to the CBH system using any of the methods.

Local Authentication

The local authentication method is the default verification method. In this method, the CBH system authenticates user's identity through username and password.

Mobile OTP Authentication

In mobile OTP authentication, the CBH system authenticates user's identity through username, password, and mobile OTP.

For mobile OTP authentication to take effect, users need to log in to the CBH system using the username and password and bind the mobile OTP application to their account. After that, the administrator of the CBH system can log in to the CBH system and configure Mobile OTP for the system users.

Mobile SMS Authentication

In mobile SMS authentication, the CBH system authenticates user's identity through username, password, and SMS message.

Users need to configure an active mobile number for their account first, following which the administrator can configure Mobile SMS for the users.

USB Key Authentication

In USB key authentication, a USB key and its personal identification number (PIN) code are used to authenticate user's identity.

For USB key authentication to take effect, a valid USB key needs to be bound to a user.

OTP Token Authentication

In OTP token authentication, the CBH system authenticates user's identity through username, password, and OTP token.

For OTP authentication to take effect, an OTP application must be bound to a user.

AD Domain Authentication

After an administrator configures the AD authentication, the administrator creates AD domain authentication users or synchronizes users from the AD domain server. The Windows AD domain server authenticates user's identity through the username and password.

Basic principles: The AD domain system terminal agent uses a third-party library to authenticate user identity.
  • IP: IP address of the AD domain server
  • Port: Set the port based on site requirements. The default value is 389.
  • Domain: Name of the AD domain

RADIUS Authentication

The administrator configures the RADIUS authentication mode and creates RADIUS authentication users. A third-party authentication server authenticates user identity through the username and password over the RADIUS protocol.

Basic principle: In RADIUS authentication, the client/server model is used to complete authentication by exchanging information between the user who accesses the device through a remote network and the server that contains user authentication and configuration information.
  • IP: IP address of the RADIUS server
  • Port: Set the port based on site requirements. The default value is 1812.
  • Password: authentication password of RADIUS
  • Test validity: Test using the RADIUS account and password

LDAP Authentication

The administrator configures the Lightweight Directory Access Protocol (LDAP) authentication and creates LDAP authentication users. A third-party authentication server authenticates user identity in password login mode through the username and password over the LDAP protocol.

Basic principle: LDAP is a directory access protocol based on the TCP/IP protocol suite. It is a common access protocol for directory services on the Internet. It is a tree-like directory database.
  • IP: IP address of the LDAP server
  • Port: Set the port based on site requirements. The default value is 389.
  • User OU: Organization unit information in the LDAP tree structure. A distinguished name (DN) resembles a path-like structure starting at the directory root. Base_DN indicates the DN where the LDAP server starts searching for the user organization unit data in the directory database. For example: If the organization unit of the DN to be searched for is ou1, the value of Base_DN is ou=ou1, o=O.

Azure AD Authentication

To enable Azure AD authentication, the administrator creates an enterprise application on the Azure platform and adds platform users to the enterprise application. The administrator then configures Azure AD authentication in the CBH system and adds those platform users to the CBH system. After Azure AD authentication is enabled, when you log in to the CBH system as a system user, the Azure login page is displayed. You need to enter the username and password on this page. Your login is then authenticated by the Azure AD platform.

Basic principles: Azure AD authentication uses the SAML protocol. You need to configure the CBH system as an application on the Azure AD platform for identity authentication.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback