Your organization may want to have users authenticate to Lumeta Enterprise Edition using Active Directory (AD). This arrangement––with an assist from you––maps AD user-rights to the Lumeta system and controls what individual users can see and control when logged in to a Lumeta Command Center. Your contribution is to tell the Lumeta system how to apply rules to map groups, organizations, and roles by creating a csv group mapping file. The group mapping file you create specifies the mapping.
For more on organizations, roles, and permissions, see the About Organizations, Zones & Users page.
In the groupmapping mechanism, a list of AD groups separated by the pipe symbol (|) can now be set as 'superuser' (or the column can be left blank).
When an AD (new) user logins into Lumeta, a user account is created along with roles mapped to the user's AD groups. If these AD groups are defined as 'superuser', all the users in AD group will be designated at Lumeta superusers. Changes to groupmapping data take effect when the users associated with those records login to the Lumeta system.
Let's assume, for example, that Active Directory contains (or has defined) these groups and we want to assign users to particular roles in Lumeta, remembering that each Lumeta role is always paired with an organization defined in Lumeta.
And you want these rules to apply to your Lumeta users:
That portion of the group mapping CSV file would look like this:
Notice that the CSV example contains only two columns––the first for AD group name and the next the Lumeta role + organization. The two columns are separated by a comma (,). Any row containing more than two columns is considered an invalid row.
Admins should get SysAdmin roles in their own regions
The AD users in row #1 are members of both the admin and na groups. The Lumeta users in row #1 are SysAdmins for the NA organization.
That portion of the group mapping file would look like this:
The contents of the assembled CSV file would look like this:
The rules we've introduced are as follows:
The admin and manager users and see these roles by default.
To map Active Directory (AD) groups and roles to Lumeta organizations, here's the process.
To configure Active Directory on Lumeta Enterprise Edition:
|CLI Command||Description & Example||Likely Order of Operations|
Maps an Active Directory group to an Organization in Lumeta Enterprise Edition
If your Active Directory mapping introduces new Organizations, you will need to create those organizations in the Command Center as follows:
Configures an Active Directory authentication server
The netbios is an alias for the hostname used in Active Directory authentication. It's only required if your hostname is more than 15 characters long.
In this example, the hostname of the Command Center is longer than the maximum number of characters allowed, so AD could not be enabled. In cases like these, use the netbios to serve as an alias for a too-long hostname.
This command would create a hostname on the AD server with the name "TestAD."
Enables and disables an AD authentication
Displays the current AD configuration. The two examples below show a not joined/disabled AD server and a joined/enabled AD server.
Clears the current AD configuration
When an AD user logs in to Lumeta, and browses to Settings > Users, users, groups, and organizations to which he has been given rights in the AD server groupings––and only those––are visible.