Parameters in /utils/¶
In this section, we will describe all the parameters currently used by various utilities.
Parameters in /utils/tl-desktop-customizer/¶
In this section we will describe all the parameters currently used by
the ThinLinc desktop customizer. These configuration parameters reside
in /opt/thinlinc/etc/conf.d/tl-desktop-customizer.hconf.
- /utils/tl-desktop-customizer/xdg_data_dirs¶
A space separated list of directories that ThinLinc desktop customizer should look for applications in.
Parameters in /utils/tl-ldap-certalias/¶
In this section we will describe all the parameters currently used by
tl-ldap-certalias. These configuration parameters reside in
/opt/thinlinc/etc/conf.d/tl-ldap-certalias.hconf.
- /utils/tl-ldap-certalias/ldap_schema¶
Specify the schema type that is used on the target LDAP server. Valid options are
rfc2307andAD.rfc2307is default and should be used with standard LDAP servers that comply with RFC 2307.ADshould be used if the target LDAP server is an Active Directory.
- /utils/tl-ldap-certalias/allow_invalid_certificates¶
This parameter controls whether to perform validation on certificates found in the LDAP database. Possible values are
yesandno.Please note that by setting this to yes, you will allow users with expired, invalid, revoked or untrusted certificates to log in as if their certificates are valid.
Note
If you want tl-ldap-certalias to match the behavior of tl-ldap-certalias versions earlier than 3.2.0, set this to
yes.
- /utils/tl-ldap-certalias/certificate_user_match¶
The method to use for finding certificates assigned to the user. Valid options are
sameobjectandnovell_certificate_subjectname.sameobjectmakes tl-ldap-certalias search for certificates in theuserCertificateattribute on user objects it finds.novell_certificate_subjectnameallows for certificates to be stored in another LDAP tree. User objects are associated to certificates by storing subject names of certificates in a multivalued attribute calledsasAllowableSubjectName(OID 2.16.840.1.113719.1.39.42.1.0.69) on the user object. tl-ldap-certalias can handle both DN:s as written by Novell iManager (DC=com.DC=example.OU=test.CN=foo) and as returned bytl-certtool --subject(cn=foo,ou=test,dc=example,dc=com).
- /utils/tl-ldap-certalias/users/uri¶
An LDAP server URI for finding users on the form
ldap[s]://name[:port]
- /utils/tl-ldap-certalias/users/base¶
The LDAP search base for finding users.
- /utils/tl-ldap-certalias/users/binddn¶
The username to bind as for searching for users. If left blank, no bind is performed.
- /utils/tl-ldap-certalias/users/bindpw¶
The password to use in combination with
binddnfor bind operations Ifbinddnis left empty, this can also be left empty.
- /utils/tl-ldap-certalias/certs/uri¶
- /utils/tl-ldap-certalias/certs/base¶
- /utils/tl-ldap-certalias/certs/binddn¶
- /utils/tl-ldap-certalias/certs/bindpw¶
If
certificate_user_matchis notsameobject, these settings will be used to determine where to look for certificates. They follow the same rules as the settings for users.
Parameters in /utils/tl-mount-localdrives/¶
In this section we will describe all the parameters currently used by
tl-mount-localdrives. These configuration parameters reside
in /opt/thinlinc/etc/conf.d/tl-mount-localdrives.hconf.
- /utils/tl-mount-localdrives/mount_args¶
Specifies any extra mount parameters to be used when mounting local drives from a client.