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
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

Built-in Authentication Providers

Updated on 2024-12-30 GMT+08:00

Introduction

This section describes how to use the FIDO2 authentication providers (such as facial or fingerprint authentication) to log in to the applications integrated into OneAccess. You can configure the FIDO2 authentication providers on OneAccess and enable the FIDO2 login mode for each application. In this way, SSO is implemented, providing users with more convenient, secure, and reliable login.

Configuration Process

NOTE:

The procedure for accessing the user portal on a PC is used for illustration. Select and configure an application that meets your service requirements.

Prerequisites

  • You have permissions to access the administrator portal.
  • The user PC uses security keys (USB or Bluetooth) or biometric authenticators (such as Windows Hello and Touch ID).

Enabling FIDO2 Authentication on the PC

Enable the options of security keys (USB or Bluetooth) or biometric authenticators (such as Windows Hello and Touch ID) on the user PC. The following uses Windows Hello as an example.

Configuring a FIDO2 Authentication Provider in OneAccess

Add a FIDO2 authentication provider and configure the application information in OneAccess.

  1. Log in to the administrator portal.
  2. On the top navigation bar, choose Authentication > Authentication Providers. On the displayed page, choose Built-in Authentication Providers > FIDO2.
  3. Configure authentication provider parameters.

    Figure 1 Configuring the FIDO2 Authentication provider
    Table 1 Configuring parameters

    Parameter

    Description

    Icon

    Upload a custom icon.

    Display Name

    Enter a display name of the authentication provider.

    Open no username process

    If this function is enabled, users do not need to enter the username or email address for login. Instead, they can select a relying party ID or bound authenticator to find the authenticator private key.

    Require Resident Key

    Whether to allow the authenticator to produce Public Key Credential as Client-side-resident Public Key Credential Source. Default option: No. If you enable login without username, this option will be changed to Yes.

    User Verification Requirement

    Whether to allow the authenticator to confirm the actual authentication user for registration and authentication. Default option: PREFERRED. If you enable login without username, this option will be changed to REQUIRED.

    Attestation Conveyance Preference

    Select the preference of the WebAuthn API for generating an attestation. This parameter is used for registration. Default option: DIRECT.

    Authenticator Attachment

    Select an authenticator attachment mode that can be accepted by the WebAuthn client. This parameter is used for registration. Default option: NONE.

    Avoid Same Authenticator Registration

    Whether to allow re-registration of authenticators of the same type. Default option: Yes.

    Timeout

    Timeout interval for connecting to the identity authenticator during binding and authentication. Default value: 180, in seconds.

    Acceptable AAGUIDs

    (Optional) Add the Authenticator Attestation GUID (AAGUID) of the trusted authenticator. This parameter is used for binding authenticators. If this parameter is left blank, any authenticator can be registered.

Enabling FIDO2 Authentication

  1. Log in to the administrator portal.
  2. On the top navigation bar, choose Resources > Applications.
  3. Click User Portal on the page.
  4. On the application information page, click the application icon.
  5. Choose Login Settings > Web Applications. In the Operation column of the row of FIDO2(WebAuthn), click to enable FIDO2 authentication.

    Figure 2 Enabling FIDO2 authentication

Activating the Binding on the OneAccess User Portal

  1. Log in to the OneAccess user portal, hover the cursor on the username in the upper right corner, and click Account Settings.
  2. Choose Account Security and click the bind button next to the added security key or biometric authenticator.

    NOTE:
    • If no security key or biometric authenticator is added, the bind button is grayed out
    • You can bind multiple authenticators, or remove the added validator and add one again.

Logging In to the User Portal Through FIDO2 Authentication

Go to the user portal page, and select the FIDO2 authentication mode for login. The security key or biometric authenticator is displayed. Complete the authentication.

Figure 3 Selecting the FIDO2 authentication mode
NOTE:

In the traceless browser mode, biometric authenticators cannot be bound, which means FIDO2 authentication cannot be used in this mode.

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