Chapter 9. Authentication in ThinLinc
Agent−→Domain−→Advanced Domain Options . Windows Terminal Servers that are excluded in
this fashion should not have the RSA Ace Agent installed.
The configuration example below assumes that you are using LDAP and RADIUS, and the Steel-Belted
Radius (SBR) server. Step 8 through 11 should be repeated on all ThinLinc servers.
1. Install and configure RSA Authentication Manager (ACE server). For basic configuration tasks such
as creating users and assigning tokens, we refer to the RSA documentation.
2. Create a new Agent Host for the SBR server, with type "Net OS Agent". Select which users should
be able to login through ThinLinc. To allow all users, check the "Open to All Locally Known Users"
checkbox.
3. Generate a configuration file for the SBR server, by selecting Agent Host->Generate Configuration
File. Copy this file to c:\windows\system32 on the machine running SBR.
4. Open the SBR Administrator. Create clients for all ThinLinc servers, using default settings. Make
sure you enter a shared secret.
5. Use SBR Administrator to create a SecurID user. The user should typically be of type <ANY>.
6. Modify the SBR Authentication Policy, so that the only active method is "SecurID User". Exit SBR
Administrator.
7. Enable ACE authentication caching by editing the configuration file
c:\radius\service\radius.ini and set:
[SecurID]
CachePasscodes = yes
SecondsToCachePasscodes = 60
Restart SBR after changing the configuration file. For more information about ACE authentication
caching, refer to the Steel-Belted Radius Tech Note RD310.
8. Install pam_radius_auth. Some distributions, such as SUSE, includes this module.
9. Configure pam_radius_auth, by creating /etc/raddb/server . It should contain the SBR
server name, port, and a shared secret. Example:
myotpserver.example.com:1812 mysecret
10. Configure the ThinLinc servers 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/system-auth, by inserting the line
auth sufficient /lib/security/pam_radius_auth.so use_first_pass
after the line containing pam_unix.so.
11. Restart the VSM and SSH server.
12. Login to the system with a SSH client, and verify that an OTP is required and accepted.
13. Login to the system with a ThinLinc client, and verify that an OTP is required and accepted.
110
Comentarios a estos manuales