Skip to main content
日本語 简体中文 繁體中文

[Access Control] Implementation Procedure Summary (Excluding Microsoft 365 and Google Workspace)

Overview

This article introduces the complete procedure for deploying Access Control without an SSO connection to Microsoft 365 / Google Workspace, from preliminary checks to connecting with cloud services via SSO and starting Access Control operations.

What You Need

  • An account with administrator privileges for the service to be integrated with single sign-on
  • An account with Global Admin privileges for Access Control
  • （Only when synchronizing with Active Directory）An account with administrator privileges for Active Directory

Notes

  1. Please check the required items according to the services and intended use.
  2. The content of this article is based on product information as of October 2026 and may be changed without notice.
  3. Before deployment, be sure to check HENNGE One System Requirements.
    Information on the limitations of each product and feature is provided.

Table of Contents

  1. Various Access Control Policy Settings

    1. Review Access Policies

    2. [Access Control] Define Access policy groups and Access policy templates

    3. Password-related settings (Modern View)

  2. User Registration and Synchronization

    • When creating accounts in Access Control

    • When synchronizing from Active Directory

  3. Administrator and End-user Tasks Based on Access Policies

    • Distribute Device Certificates

    • Secure Browser Configuration

    • OTP（One-Time Password）Configuration

  4. Assigning Access Policies and Operation Testing

    1. Assign Access Policy Group to Users (Modern View)

    2. Perform Access Policy Group Operation Test (Modern View)

  5. Single Sign-On Configuration

    1. Connection setup with the service to be used for single sign-on （SSO）

Procedure

1. Various Access Control Policy Settings

Starting in March 2026, Access Control has begun offering a new login screen.

If you subscribed to HENNGE One before the above date, complete the following procedure before starting the subsequent steps.
[Access Control] Migration Procedure to the New Login Screen

Configure access policies （access permission conditions） for logging in to single sign-on services from Access Control. Also configure the Password policy for the entire Tenant.
※Perform this procedure using an account with Access Control Global Admin privileges.

  1. Review Access Policies
    Determine the requirements you want to configure from the access control patterns in the table below.
    If you wish to implement an access control method other than the patterns below, search the Help Center for the relevant procedure or Contact Us your implementation representative.
  1. [Access Control] Define Access policy groups and Access policy templates 
    Configure the policies you have determined.
  2. Password-related settings (Modern View) 
    Configure the Password policy.

2. User Registration and Synchronization

The procedure differs depending on whether Users are synchronized from Active Directory or created in Access Control. Please review the applicable procedure before proceeding.

When creating an account in Access Control

Perform this Procedure using an account that has been granted Global Admin privileges for Access Control.

  1. Bulk User Registration/Update/Deletion (Modern View) 
    To use Access Control, create a User in Access Control that is linked on a one-to-one basis with a User in Microsoft 365.
When performing Synchronization from Active Directory

Perform this Procedure using an account that has been granted Global Admin privileges for Access Control and a Windows account that has been granted administrator privileges for Active Directory.

Synchronize User information from Active Directory to Access Control and create Users in Access Control.

  1. Define Synchronization Conditions and Receive the File 
    Define the Configuration Values for the HENNGE Directory Sync Tool synchronization configuration file used for Active Directory Synchronization, and receive the configuration file from HENNGE.
  2. Organize and prepare users on Active Directory 
    Organize Users in Active Directory, such as by storing the Users to be synchronized in the security groups or OUs specified in the synchronization configuration file.
  3. How to install HDEPasswordFilter.dll on Active Directory (WS 2016 or later) 
    This task installs the DLL file, which is one of the configuration files required to perform Active Directory Synchronization, on all Domain Controllers.
  4. Restart Domain Controllers
    Restart all Domain Controllers to apply the configuration file.
    ※ Please perform this task with attention to its impact on business operations, such as the time of execution.
  5. Change Passwords for Users to Be Synchronized in Active Directory
    Have the end users themselves or an Admin change the Passwords of all Users to be synchronized once.
    ※ Procedures 6 〜 9 can be performed without waiting for all Users to complete their Password changes.
  6. Installation of HENNGE Directory Sync Tool  
    Install the User synchronization tool on Active Directory.
  7. [Access Control] Procedure for Installing the Root Certificate Required for HENNGE Directory Sync Tool Operation 
    Install the Root Certificate required to operate the User synchronization tool.
  8. [Access Control] Creating an API Client for Executing the HENNGE Directory Sync Tool  
    Create the API Client secret required to run the User synchronization tool.
  9. [Access Control] Initial Setup of HENNGE Directory Sync Tool Configuration File config.ini 
    Place the synchronization configuration file in the specified folder in Active Directory.
  10. [Access Control] Checking the Password Settings for Synced Users 
    Confirm that the Passwords of Users to be synchronized have been set as synchronization information.
  11. [Access Control] Running the HENNGE One Directory Sync Tool 
    Run the synchronization tool to start User Synchronization from Active Directory to Access Control.

3. Administrator and End-user Tasks Based on Access Policies

Based on the access control requirements, please review the implementation procedures for the applicable features.

Perform the Procedures in this section only when configuring Access policies that use the respective features.
Click the feature to use and perform the Procedure.

Distribute the Device Certificates

Issue Device Certificates in the Access Control Administration. Once the issued Certificate is installed on the end user's device, preparation for using Device Certificates is complete.

  1. HENNGE Device Certificate Device Information Gathering 
    Collect the Device ID (a unique Value that differs for each device) of the Devices targeted for Device Certificate distribution.
  2. [Device Certificate] Issuing a Device Certificate 
    This task distributes Device Certificates to end-user devices.
    When an Admin issues a Device Certificate, an Email is sent to the end user with instructions to install the Certificate.
  3. How to Install HENNGE Device Certificate? 
    This task installs the Device Certificate on the end user's device.
    ※ This task must be performed on the end user's device.
OTP（One-Time Password） Configuration

Even when using OTP（One-Time Password）, you can skip this Procedure if any of the following apply.
※ The registration screen will be displayed upon your first Login.
・Accounts with Access Control Admin privileges
・Users assigned to an Access policy group that requires OTP

  1. [Access Control] Configuration for Receiving OTP (One-Time Password) via Connected Application 
    Install the dedicated Connected Application and configure OTP receipt settings.
    ※ This task must be performed on the end user's device.

OTP can only be received on one Device per User.

When issuing OTPs to Users who share an Access Control account, you can configure OTP receipt via Email Address instead of a Connected Application so that multiple people can receive OTPs.
[Access Control] Configuration for Receiving OTP (One-Time Password) via Email 
Secure Browser Configuration
  1. [Secure Browser] Installation and Device Authentication for Secure Browser 
    Install Secure Browser on the end user's device.
    ※ This task must be performed on the end user's device.
  2. Device Authentication for Secure Browser 
    This explains how the Admin performs Device Authentication so that Users can begin using Secure Browser.

All Configuration required before starting Access Control operations has now been completed. In the next Procedure, you will test the operation of the Access policy configured before beginning operations.

4. Assigning Access Policies and Testing Operation

  1. Assign Access Policy Group to Users (Modern View) 
    Assign Access policies to the Users created in Access Control.
  2. Perform Access Policy Group Operation Test (Modern View) 
    After assigning the Access policy, log in to the Access Control User screen as the Target User and test whether access control functions as expected.

After completing the operation test, configure single sign-on with the cloud service to be integrated in the next Procedure, and then begin operations.

5. Configuring Single Sign-On

When you perform this Procedure, authentication for end users logging in to the Target service will be switched to Access Control. Please carefully coordinate the timing of this change, such as by avoiding business hours.

  1. Connecting to Services for Single Sign-On (SSO) 
    The Procedure for configuring single sign-on varies by service.
    HENNGE provides manuals in the Help Center for services that have been verified by HENNGE. Please follow the relevant manual to complete the Configuration.

This completes all Access Control implementation tasks.

Translation Disclaimer

This article has been automatically translated from the original Japanese version for your convenience.
While we strive to ensure accuracy, we cannot guarantee its reliability or completeness.

In the event of any discrepancies or questions regarding the content, the official Japanese version shall prevail.