Dell Wyse Enhanced Ubuntu Linux T50 Manual de usuario Pagina 119

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 220
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 118
Chapter 9. Authentication in ThinLinc
5. Normally, when not using OTPs, the VSM and SSH Server PAM configuration is the same. This is
often accomplished by a symbolic link /etc/pam.d/thinlinc pointing to /etc/pam.d/sshd.
When using OTPs, this symbolic link should be replaced with a private copy:
# cp /etc/pam.d/thinlinc /etc/pam.d/thinlinc.new
# mv /etc/pam.d/thinlinc.new /etc/pam.d/thinlinc
6. Configure the SSH server for RADIUS authentication by modifying its PAM configuration. The
exact procedure depends on the system, but typically, this can be done by modifying
/etc/pam.d/sshd, by inserting the line
auth sufficient /lib/security/pam_radius_auth.so use_first_pass
after the line containing pam_unix.so. Lines with references to pam_ldap in the auth section
should be removed.
Note: If the system uses a "stackable" PAM configuration, then copy system-auth to
system-auth-radius, and modify this file instead of /etc/pam.d/sshd. Then, adapt this file to
use system-auth-radius instead of system-auth, in the "auth" section.
7. Restart the VSM and SSH server.
8. Login to the system with a SSH client, and verify that an OTP is required and accepted.
9. Login to the system with a ThinLinc client, and verify that an OTP is required and accepted.
9.6.4. Configuration for RSA SecurID
This section describes how to deploy a OTP solution based on RSA SecurID with ThinLinc. When using
this solution, the SecurID PASSCODEs are used instead of normal passwords. The PASSCODE should
be entered in the ThinLinc client password input field. Please observe the following limitations:
When SecurID requests additional information, in addition to the PASSCODE initially entered, a
popup dialog will be used. This happens, for example, in Next Token or New PIN mode. After
finishing the dialog, the ThinLinc client will display a "Login failed!" error message. This happens
since the SBR server clears the token cache when additional information is requested. When this
happens, wait until the token changes once more, and login again.
The ThinLinc Single Sign-On mechanism will store the string entered in the clients password input
field. When using SecurID, this is the PASSCODE, which cannot be used for further logins. To use the
Single Sign-On mechanism, the user must be prompted for their real password. This can be done with
the program tl-sso-update-password. To configure ThinLinc so that this program is executed during
login, execute this command:
# ln -s /opt/thinlinc/bin/tl-sso-update-password /opt/thinlinc/etc/xstartup.d/05-tl-sso-update-password
If an external application server is used, and you want to able to establish connections with the Single
Sign-On mechanism, this application server cannot be SecurID-protected. This includes Windows
Terminal Servers. When using SecurID-protected Windows domains, users and computers can be
excluded from SecurID protection at the domain controller, by selecting Control PanelRSA ACE
109
Vista de pagina 118
1 2 ... 114 115 116 117 118 119 120 121 122 123 124 ... 219 220

Comentarios a estos manuales

Sin comentarios