Login Syntax, Identity Source & Password Recovery on MTN Cloud

Overview

This guide explains how users log in to an MTN Cloud tenancy with the SubDomain\Username syntax. It covers how a Customer Admin User configures the account subdomain under Identity Sources, and how a user recovers a forgotten password.

Why it matters:

  1. Consistent Login: Every user of the tenancy logs in with the same subdomain prefix, which identifies the tenant.
  2. Your Own Login URL: Setting the account subdomain gives your tenancy its own account login URL.
  3. Self-Service Recovery: Users with locally managed accounts can reset a forgotten password without contacting support.

Prerequisites

Before you begin, ensure you have:

  1. An MTN Cloud Console login with the appropriate role (full permissions) to Administration (Users and Roles). This means having the Customer Admin User role, or a role with equivalent privileges, assigned. This applies to Phase 1. Phase 2 can be completed by any user.

Tip: If you cannot see the Users and Roles features despite having the correct role, try refreshing the portal. If the issue persists, contact MTN Cloud Support.

Key Terms

TermMeaning
Identity SourcesExternal authentication integrations that enable centralised user identity management by using enterprise providers. They authenticate users against services such as Active Directory, which gives consistent access control and simpler management.
SubDomainA unique identifier assigned to each customer tenant within MTN Cloud. It is used mainly for user authentication and identification.

Login Syntax

Once the account subdomain is set, tenant users log in with the subdomain as a prefix to their username, in the following format:

SubDomain\Username

The Right Sequence

To manage how users log in, follow this sequence:

  • Configure the Account Subdomain: Go to Administration → Users → Identity Sources, edit the SubDomain, and save the change to update your Account Login URL.
  • Recover a Forgotten Password: Request a reset link from the login page using the SubDomain\Username format, then set a new password from the link in the email.

Phase 1: Configure the Account Subdomain

Purpose: Set the account subdomain, which updates your Account Login URL and the prefix that users enter when they log in.

  1. As a Customer Admin User, or any user with equivalent administrative privileges, navigate to Administration → Users.
Administration menu expanded with Users highlighted on the MTN Cloud dashboard
  1. On the Users page, click the Identity Sources tab.
Users page with the Identity Sources tab highlighted in the MTN Cloud console
  1. Click Edit beside your SubDomain, under Account Login URL.
Identity Sources page showing the Account Login URL with the Edit button beside the SubDomain
  1. In the Edit Subdomain window, enter the desired value in the Subdomain field. The Login URL shown above the field includes the subdomain.
Edit Subdomain window showing the Login URL and the editable Subdomain field with the current value
  1. Click Save Changes to apply the update.
Edit Subdomain window with the new subdomain entered and the Save Changes button
  1. To verify the change, open the login page and log in using the new SubDomain\Username format. The Log In screen accepts the username in this format.
MTN Cloud login screen with the username entered in the SubDomain backslash Username format
  1. After a successful login, the MTN Cloud dashboard is displayed.
MTN Cloud dashboard shown after a successful login with the configured subdomain

Result: Your account subdomain and login URL are now configured, and your MTN Cloud tenancy can be accessed with the configured subdomain. Make sure that identity sources and users are set up to use the correct login URL.

Phase 2: Recover a Forgotten Password

Purpose: Reset the password of a locally managed user account from the login page. The process has four steps: find the Forgot password? link, submit the request, receive the email, and set a new password.

Important Note: Where an external identity provider is in use, user data, including passwords, is synced from the external identity source (such as Active Directory or Azure AD). The password of such a user cannot be edited in MTN Cloud, and must be updated in the external source.

Step 2: Set a New Password

  1. A message confirms that an email has been sent if the username is valid. If a matching locally managed user account is found, MTN Cloud sends an automated email with a password reset link to the registered email address.
Confirmation message that a reset email has been sent if the username is valid
  1. Open the email and click Click here to reset. The link is valid for 30 minutes.
Password reset email from donotreply@mtn.com with a Click here to reset button
  1. On the reset page, enter the new password and confirm it by entering it again. The two entries must match. The password must be at least 8 characters long and include an uppercase letter, a lowercase letter, a number and a special character.
  2. Click Reset Password.
Secure password reset page with the Password and Confirm Password fields and Reset Password button
  1. Log in using the SubDomain\Username format and your new password.
MTN Cloud login screen with the SubDomain Username and the new password entered

Final Notes

  1. Login Requirement: Once the account subdomain has been updated, all tenant users must log in with the new subdomain prefix, in the format SubDomain\Username. This ensures proper authentication within the MTN Cloud tenancy.
  2. Unique Identifier: The account subdomain is the unique identifier of your tenant. An incorrect subdomain causes authentication attempts to fail.
  3. External Identity Provider: When an external identity provider (for example, Active Directory) is in use, the subdomain is aligned to that of the external identity source. Use this subdomain when you log in to the MTN Cloud Console.
  4. Password Recovery: The Forgot password process applies to locally managed users only. Users managed through an external identity source must change their password in that source.