During setup, you can define users who can bypass MFA (e.g., for emergency or monitoring accounts).
Example input:
π 6. Authentication Test
SSH Login
1 triggers a Mirket Push notificati
on to your mobile device.
You can also enter a passcode manually.
On Red Hat, authentication first checks MFA, and only then verifies the password.
Sudo/Privilege Elevation
On Red Hat privilege elevation, authentication first checks MFA, and only then verifies the password.
Supported Passcode Types:
Mirket token
TOTP (Time-based One-Time Password)
Offline code
Recovery code
π§Ή 7. Uninstalling the Agent
To remove the Mirket OS Agent completely:
This will:
Remove all related binaries
Clean PAM configurations
Restore SSH settings
π Enabling Passwordless MFA with Mirket PAM Module
This guide explains how to configure SSH login and privileged commands (sudo) to enforce passwordless Multi-Factor Authentication (MFA) using the pam_mirket_authenticator.so module. By adjusting the PAM configuration onlyβwithout modifying the sshd_config fileβyou achieve a secure and streamlined authentication flow.
π― Objective
To enforce Mirket MFA as the sole authentication method for:
SSH login
sudo and other PAM-based elevated actions
while fully disabling traditional password or public key authentication.
Configuring Passwordless SSH Authentication on Red Hat
To disable password-based authentication and enable passwordless SSH login:
Open the SSH PAM configuration file:
Locate the following line and disable it by commenting it out:
Restart the SSH service to apply the changes:
Re-enabling Password Authentication on SSH
To restore password-based authentication:
Open the same SSH PAM configuration file:
Enable the line by uncommenting it:
Restart the SSH service again:
Enabling Passwordless sudo on Red Hat
To enable passwordless sudo authentication on Red Hat systems:
Run the following command:
The script will:
Check for any existing custom authentication profiles.
Create a new custom profile named passwordless-mirket based on the sssd profile.
Activate the new profile automatically.
Example output:
β Note:
Ensure that the SSSD service is properly configured and enabled before applying this change.
Reverting to OTP + Password for sudo
If you want to revert and require both OTP and password for sudo authentication, run:
This will restore the configuration that enforces OTP + password for elevated access.
Reverting to Password-only sudo Authentication
If you prefer to use password-onlysudo authentication:
Please enter a username to add as a bypass user (type -1 to finish): mirket
Please enter a username to add as a bypass user (type -1 to finish): -1
login as: oliver
Keyboard-interactive authentication prompts from server:
| Enter Passcode Or 1 For Push: 1
| Password:
End of keyboard-interactive prompts from server
Activate the web console with: systemctl enable --now cockpit.socket
Last login: Tue Oct 7 08:20:09 2025 from 10.10.10.180
[oliver@localhost ~]$
[oliver@localhost ~]$ sudo su
Enter Passcode Or 1 For Push: 1
[sudo] password for oliver:
[root@localhost oliver]#
cd LinuxOSAgent/
sudo ./redhat_uninstall_mirket.sh
sudo nano /etc/pam.d/sshd
#auth substack password-auth
sudo systemctl restart sshd
sudo nano /etc/pam.d/sshd
auth substack password-auth
sudo systemctl restart sshd
sudo ./redhat_passwordless_mirket.sh
[*] Checking existing custom profile...
[*] Creating new custom profile based on 'sssd'
New profile was created at /etc/authselect/custom/passwordless-mirket
[*] Profile is activating
Backup stored at /var/lib/authselect/backups/2025-10-07-11-36-37.o9jXsI
Profile "custom/passwordless-mirket" was selected.
The following nsswitch maps are overwritten by the profile:
- passwd
- group
- netgroup
- automount
- services
Make sure that SSSD service is configured and enabled. See SSSD documentation for more information.
Changes were successfully applied.
[+] passwordless-mirket profile successfully activated