Local Group Configuration
In cases where it is not desired to create users on LDAP systems such as Active Directory etc. for externally supported individuals, multi-factor authentication can be provided by creating local groups and local users on Mirket. In many scenarios, such as enabling MFA on RDP connections of local users on the servers, secure access can be provided by creating a local user on Mirket.
In the Groups > Local Groups menu, a new group can be created, edited or deleted.
Group Name: The name to be given to the created group.
Description: The description to be given to the created group.
SAM: In Mirket, user identification is done using the SAM (Security Account Manager) name. This is preferred over the standard username. The formation of the SAM name is as follows:
If NPS is within a domain (for instance, if the domain name is 'mirket.local'), requests are sent in the format 'mirket\username'.
If NPS operates in a workgroup environment outside of a domain, requests use the NPS server's name as a basis, for example, 'mfaserver\username'. If Mirket does not find a user corresponding to the incoming SAM name, a 'user not found' log message will be recorded, and Mirket will deny the authentication request. This also applies to RDP and OWA connections. In these types of connections, requests are directly sent to the Mirket system in the 'sam\username' format. If there is no user with the same SAM name, Mirket will respond with a 'user not found' message and deny the request. In LDAP group definitions, the SAM values of users are specified. When Mirket imports users from LDAP, it adds the defined SAM value to the beginning of the usernames to create the SAM names. When local users are created, their SAM values are taken from the local groups they belong to. It is expected that SAM values are correctly entered in these local groups.
In the Groups > Local Groups menu, created local groups can be listed, searched, columns displayed, printed, filtered, or exported in CSV format.
Related Topics
Last updated