Micetro by Men&Mice
Latest versions
Search all documentation
This section discusses the available user authentication methods available with the Men & Mice Suite.
In addition to Local User Authentication, the Men & Mice Suite currently supports two methods of AD user authentication using the Windows Active Directory user database and authentication through a RADIUS server.
The Active Directory (AD) User Authentication mechanism allows you to have users authenticate themselves in the AD login system before allowing them to login to the Men & Mice Suite. In large installations, this system has obvious benefits as the users do not have to maintain their passwords in multiple locations. The password rules (password expiry, minimum password length, etc.) that have been applied within the organization automatically apply to the Men & Mice Suite.
Even when you are using AD User Authentication, you must create users in the Management Console and assign privileges to them using the Men & Mice access system. The only difference between AD vs. local user authentication is that when AD user authentication is used, users are authenticated using the AD User Authentication system before they can access the Management Console. When AD User Authentication is used, the user password is not stored in the Men & Mice software.
Only one authentication method can be used per user, but different users can have different authentication methods. That means you can have some users log in using AD user authentication, while other users log in using local user authentication.
AD user authentication using Active Directory is only possible when you run Men & Mice Central on a Windows machine. The machine running Men & Mice Central must be a member in an Active Directory domain or forest.
No specific configuration is needed for Men & Mice Central for AD user authentication using Active Directory.
To configure a user to use AD user authentication, do the following:
You can enable the Single Sign-on so that Active Directory users do not have to authenticate when logging in through the Management Console or the Command Line Interface.
To enable Active Directory Single Sign-on, do the following:
When single sign-on is enabled, it is possible to enable sign-on in the web interface if the web application is running on an IIS Server.
To enable single sign-on in the web interface, do the following:
Logging into the Men & Mice Suite will not change when AD user authentication is used and Single Sign-on is disabled. The only thing to keep in mind is that the user name that is entered must match the user name stored in the Men & Mice Suite. If a distinguished user name is used, it must be entered in the same way when logging in.
The Group Level Active Directory (AD) User Authentication mechanism allows you to set user access privileges by group membership in the AD. In large installations, this system has obvious benefits as the users do not have to maintain their passwords in multiple locations. The password rules (i.e., password expiry, minimum password length, etc.) that have been applied within the organization automatically apply to the Men & Mice Suite.
The login sequence is as follows for users with Group Level AD authentication:
To allow a user to log in to the Men & Mice Suite, you must create a group in the AD that has the same name as a group in the Men & Mice Suite and place the AD user in that group. You may create multiple groups in the AD that match group names in the Men & Mice Suite.
When using AD Group level authentication, you must specify which groups in the Men & Mice Suite should be used to verify group membership.
Group Level Active Directory user authentication is only possible when you run Men & Mice Central on a Windows machine. The machine running Men & Mice Central must be a member in an Active Directory domain or forest.
You do not have to create users in the Men & Mice Suite when the Group Level AD authentication is used. Instead, user access is controlled by the group membership of the user in the AD.
The Men & Mice Suite can authenticate using an external RADIUS server. In large installations, this system has obvious benefits as the users do not have to maintain their passwords in multiple locations. The password rules (i.e., password expiry, minimum password length, etc.) that have been applied within the organization automatically apply to the Men & Mice Suite.
Even when you are using RADIUS User Authentication, you must create users in the Management Console and assign privileges to them using the Men & Mice access system. The only difference between RADIUS vs. local user authentication is that when RADIUS user authentication is used, users are authenticated using the RADIUS User Authentication system before they can access the Management Console. When RADIUS User Authentication is used, the user password is not stored in the Men & Mice software.
NOTE: Only one authentication method can be used per user, but different users can have different authentication methods. That means you can have some users log in using RADIUS user authentication, while other users log in using local user authentication.
To enable RADIUS authentication, you must add several properties to the Men & Mice Central configuration file preferences.cfg. This file is located in the data folder inside the Men & Mice Central data directory:
Windows: C:\ProgramData\Men & Mice\Central\
All others:
Set during installation. Usually /var/mmsuite/mmcentral or /chroot/var/mmsuite/mmcentral, where /chroot is the location used as a chroot jail for named.
The properties to be added are:
RADIUSServer | Defines the address of the RADIUS server that will do RADIUS authentication. |
RADIUSPort | Defines the port that the RADIUS server is listening on. The default value is 1812, which is the port normally used by RADIUS. |
RADIUSSharedSecret | The shared secret between the RADIUS server and the Men & Mice Suite. |
RADIUSAuthentication | The type of authentication used. 0 = PAP, 1 = CHAP. |
Example:
<RADIUSServer value="192.168.1.3"/>
<RADIUSPort value="1515"/>
<RADIUSSharedSecret value="MyBigSecret"/>
<RADIUSAuthentication value="1"/>
After editing the file, restart Men & Mice Central.
Windows: Use Administration Tools > Services to restart Men & Mice Central.
All others: Execute the mmcentral init script with the 'restart' argument.
To allow a user to log in to the Men & Mice system, the user must exist in the Men & Mice user database. If the user does not exist in the Men & Mice user database, they are not allowed to log in, even if they provide a valid user name and password in the RADIUS login system.
To configure a user to use AD user authentication, do the following:
When the RADIUS authentication method is selected, the Password field is disabled, since the password is not stored in the Men & Mice Suite.
Logging in to the Men & Mice Suite will not change when RADIUS user authentication is used. The only thing to keep in mind is that the user name that is entered must match the user name stored in the Men & Mice Suite.