Your own ID-Server
On premise installations of SecSign ID offer the flexibility to connect with your preferred servers, services, and devices. And you can customize the SecSign ID with your own organization’s branding.Learn More
The Pluggable Authentication Modules (PAM) is a software library which offers a general programming interface for authentication services. By using the PAM-API one does no longer need to define the settings for every single authentication application. Instead, individual standarized modules can be used. The modules can be assigned to individual services in the configuration file. There is no need to change the compilation of the corresponding software. PAM is available for AIX, HP-UX, Solaris, Linux, FreeBSD, NetBSD, Mac OS X and DragonFly BSD.
Please read the SecSign ID PAM Tutorial before using the SecSign ID PAM for SSH Authentication. Follow steps 3 to 5 to configure and install PAM correctly.
Overview on the configuration and installation:
pam_secsignid.soin the PAM library (usually
Depending on your system, settings, login preferences and OpenSSH version, these steps might differ:
Public Key with Keyboard interactive 2FA (example in RHEL):
After OpenSSH version 6.2, the AuthenticationMethods configuration parameter can be used. Open the configuration file/etc/ssh/sshd_config and change the following parameters:
PubkeyAuthentication yes PasswordAuthentication no PermitEmptyPasswords no AuthenticationMethods publickey,keyboard-interactive ChallengeResponseAuthentication yes UsePAM yes
Then open the configuration file for the SSHd PAM settings/etc/pam.d/sshd and change it to the following:
auth required pam_sepermit.so #auth substack password-auth auth required pam_env.so auth required pam_secsignid.so auth include postlogin
Restart the sshd service
service sshd restart
Establish a connection to the SSH server and try the SecSign ID Two-Factor Authentication.
Password with 2FA (example in Ubuntu):
Open the configuration file/etc/ssh/sshd_config and activate the utilization of PAM:
Then open the configuration file for the SSHd PAM settings/etc/pam.d/sshd, uncomment the entry at “Standard Un*x authentication” and add the following:
# PAM configuration for the Secure Shell service # Standard Un*x authentication. auth [success=1 default=ignore] pam_secsignid.so auth requisite pam_deny.so auth required pam_permit.so #@include common-auth
Save the file and reboot the SSH server. Establish a connection to the SSH server, enter your password and try the SecSign ID Two-Factor Authentication.
The library libcurl needs to be installed in the standard path, otherwise make fails. If libcurl is not on the standard path the compilation needs to be executed manually.
If the authentication fails the debug- and logmodus should be activated (see PAM debug- and logmodus) and the output should be written in a file. This is necessary since PAM normally needs to be silent and does not allow for output for security reasons. If no log- or debug-files are generated the paths provided in secsignid.c are incorrect or no read-and-write authorizations are available.
A log-file is produced stating all errors. It is determined if libcurl works accurate, if the SecSign ID server is available, if port 443 is available to communicate with the server, if the configuration file is available and if PAM has reading authorization.
A debug file is created which records the interface communication. It is determined wether errors in the communication persists because no SecSign ID for the specific user was found or if there are errors in a different parameter, for example the service name.
To do so, check your system log file and find the lines that are “denied”
sudo grep denied /var/log/audit/audit.log
Copy it and run the following command:
sudo audit2allow -M local << _EOF_ (paste the content) _EOF_
semodule -i local.pp
That will create a permanent rule for it so you shouldn't need to disable SELinux.
The FIDO2 Project is a set of standards developed by the FIDO Alliance and the World Wide Web Consortium (W3C) to create a strong authentication protocol for the web. It consist mainly of the WebAuth standard for the browser part ...Mehr Lesen
The FIDO2 Project is a set of standards developed by the FIDO Alliance and the World Wide Web Consortium (W3C) to create a strong authentication protocol for the web. It consist mainly of the WebAuthn standard for the browser part ...Mehr Lesen
In the recent weeks, home office work has increased potentially. And while employees are practicing social distancing from their home computer, attackers are working hard to exploit security issues in this situation that is unfami ...Mehr Lesen
Want to learn more about SecSign’s innovative and highly secure
solutions for protecting your user accounts and sensitive data?
Use our contact form to submit your information, and a SecSign sales representative will contact you within one business day.
If you need assistance with an existing SecSign account or product
installation, please see the FAQs for more information on the most common questions. You don’t find the solution to your problem? Don’t hesitate to contact the
I am Interested in