Domain Controller Integration Guide on MTN Cloud
Overview
The MTN Cloud Domain Controller Integration is a centralised identity management capability that links external directory infrastructure seamlessly to your cloud tenancy. This configuration allows for unified authentication, cross-subdomain access control, and programmatic role mapping across your active environments.
Why it matters:
- Centralised Management: Walks administrative teams through integrating an external domain controller with MTN Cloud to maintain a single identity source of truth.
- Access Synchronization: Provides the architecture required for Active Directory user authentication and structural directory queries across tenant workloads.
- Granular Security Policies: Restricts integration traffic to validated network zones through port allocations and dedicated security group restrictions.
Prerequisites & Port Requirements
Before initializing the integration, ensure your cloud security boundaries permit communication over required protocols. Port parameters must align with the following specifications:
- Core Ports: Ports 53, 88, and 389 are mandatory for Active Directory authentication and directory services.
- Supporting Ports: Ports 135 and 464 are recommended for full system functionality.
- NetBIOS Ports: Ports 137 to 139 are only required if operating legacy or NetBIOS-based infrastructure environments.
| PORTS | PROTOCOL | SERVICE | PURPOSE |
|---|---|---|---|
| 53 | TCP/UDP | DNS | Name Resolution |
| 88 | TCP/UDP | Kerberos | Authentication |
| 135 | TCP | RPC Endpoint Mapper | Remote procedure calls |
| 137-138 | UDP | NetBIOS | Name service |
| 139 | TCP | NetBIOS | Session service |
| 389 | TCP/UDP | LDAP | Directory Queries |
| 464 | TCP/UDP | Kerberos Password | Password Changes |
Tip: If you cannot see the Administration settings, Users panel, or Identity Source catalog components, try refreshing the portal. If features remain missing, contact your Customer Admin User or system support team.
Phase 1: Domain Controller Integration
Step 1: Security Group Configuration
Before proceeding with the physical integration of the Domain Controller Server to MTN Cloud, you must update the relevant network security groups to allow specialized ingress traffic.
- Open your tenancy firewall panel and add rules to allow TCP traffic on port 389 from the following explicit public networks:102.88.18.238/32102.88.18.72/32
- Add rules to allow UDP traffic on port 389 from the identical source paths:102.88.18.238/32102.88.18.72/32

Step 2: Readiness Confirmation
- Audit the rules list to ensure all four modifications appear explicitly within the active firewall set.
- Validate that the rules are fully active and correctly applied to your instances before moving into Phase 2.
Phase 2: Identity Source Configuration
Step 1: Navigate to Identity Sources
- Log in to the portal as the designated Customer Admin User of your active tenancy.
- From the primary horizontal command deck, select and open the Administration menu dropdown.
- Click on the Users option.

- Inside the main Users view, look for the action block buttons and click on Identity Sources.

- Once the directory management screen initializes, click on the + Add Identity Source button.

Step 2: Add and Configure Identity Source
When the configuration card loads, systematically apply the required system details across the designated input groups.
Identity Source Identification:
- TYPE: Click the dropdown menu and select Active Directory.
- NAME: Enter a unique identifier string for the source directory.
- DESCRIPTION: Provide a brief operational description summarizing the scope of the link.
Active Directory Connection Parameters:
- AD SERVER: Input the path using the format IP-Address:389 (e.g., 102.80.29.3:389).
- DOMAIN: Provide your official directory domain name.
- USE SSL: Leave this set to the default option (No).
- BINDING USERNAME: Input your administrative service account credentials (e.g., Administrator or SuperUser).
- BINDING PASSWORD: Input the corresponding password for the specified binding account.
Role Options & System Mappings:
Ensure you manually check the following boxes to establish integration features:
- Support User Principal: Enables UPN log-in workflows for end users attempting access across all configured system subdomains (Requires specifying the Global Catalog port in the AD Server field if utilized).
- Include Member Groups: Dynamically imports organizational groups linked to user objects.
- Enable Role Mapping Permission: Activates permission evaluation options for automated group assignment.
- Manual Role Assignment: Retains permissions configuration choices directly within the management console.

- Review all parameters for connection accuracy and click on the Save Changes button to deploy the identity integration.