Registration Server Settings¶
Registration Server Settings can be changed in the Administration Console, via the Server Management -> Registration Server Settings page.
These settings are split up into several categories, which are listed below (in alphabetical order).
You can define a minimum password length to be used by a user. The default value is 8 characters. This parameter will only be checked by the API, since the Clients only send an MD5 hash of the password, which can not be checked on server side. A password complexity check is not implemented at the moment.
You can define a minimum username length to be used by a user. The default value is 5 characters.
These settings define how the Registration Server delivers outgoing email messages to an SMTP server (MTA).
The sender header can be defined to avoid spam classification (see sender field description in: http://en.wikipedia.org/wiki/Email#Header_fields). This is necessary in case that the invitations between the users don’t match to the domain which will be used by the registration server. If this value is empty, only the from header will be used.
This setting can be overridden by the provider setting
EMAIL/EMAIL_SENDER_EMAIL, to define a custom sender address on a
per-provider basis. See chapter EMAIL_SENDER_EMAIL for details.
As described in the SMTP protocol
there will be communication between the SMTP client on the registration server
and the SMTP server which will accept the email for delivery. To avoid spam
HELO command must match the servers
FQDN. If this
value is empty, the default hostname / IP address detection will be used which
127.0.0.1 instead of the hostname.
This is a security setting, since invitation mails can, potentially, also be used for spam mails from an user sent by your mail server. You can define how many mails the user can send per day. (-1 = unlimited, 0 = no mail)
The IP or DNS name of the SMTP server. It must be a SMTP server which can
sendmail requests without requiring any form of encryption
Timeout parameter in seconds for
A Provider will be identified by the IP address where an API request
originates from. If different Providers send requests coming from the same IP
address, this value must be changed to
True so that the Provider can be
set within the requests.
If you are using the Administration Console and have multiple providers using the Registration Server, this value must be set to True.
To detect “man in the middle” attacks when sending API requests to the Registration Server, a random “salt value” is generated during the initial installation. The sender must add this salt value to his request before calculating the MD5 hash value of the API request content which will be sent to the Registration Server.
The checksum will be included in the URL, so that the Registration Server can check if the content was modified during the transport.
This setting is read-only and can not be changed via the Administration Console.
See chapter API Basics for details.
A log file that tracks API requests issued by the Administration Console. This
file needs to be owned and writeable by the apache user. (default:
On startup and later on in intervals between 4 and 12 hours, the client will
ask for new
RegServerURLs using the balance call (if the value is empty,
RegServerURL is used instead).
If more than one URL is returned, the client uses a round robin algorithm to send the request to all different servers. The first URL in the list is the URL which must be always available. This will be used as a fallback URL, if the others in the list fail.
The time in seconds that Registration Server configuration options are cached.
Changes to the Registration Server or Provider setting will be reloaded after
The default poll interval for clients (in seconds) to look for new invitations on the Registration Server.
These settings are sent to all Clients after login. Settings specified for a Provider can override the values defined here.
This setting can be overridden by the provider setting
CLIENT/CLIENT_SETTINGS on a per-provider basis. See chapter
CLIENT_SETTINGS for details.
Select the existing Provider account that acts as the default Provider (this is usually the first provider created on the Registration Server).
For more information about the Provider concept, please refer to Provider Concept.
IP address or host name of the HTTP proxy server to be used for the Registration Server to Host Server communication.
TCP port of the HTTP proxy server to be used for Host Server requests.
Set to True if outgoing Host Server requests must be sent via a HTTP
proxy server. This requires setting
Invitations will be stored on the server for a specified period of time. The default is 30 days (2592000 seconds). After that duration the server will automatically delete older invitations. If the value is to 0, invitations will never be deleted. Deletions are carried out by the background task described here: “Delete Old Messages”-Task.
Within 14 days after the first registration, the client will send an invitation for each created Space to the registration server for devices the user may install in future. See Invitation for future devices for a detailed description.
Each new Client installation by a user will create a new device in the database. If the user were to get a new PC, it would be installed as a new device, but the first device will remain in the Registration Server database, even if the user no longer uses it. Invitations will only be sent to devices which were active within the defined period. Please notice, that the device active timestamp will only be updated once a day. So, the value should not be less than one day (86400 seconds). The default value is 96 days (8294400 seconds).
Optional load balancer URL. If empty
RegServerURL will be used.
In case of errors on the Client side, the user can submit a support request by
uploading its log files to the Registration Server. The archive of log files
and additional debug information will be sent to a PHP script
recommend keeping the existing URL since in general it will only be possible for
TeamDrive Systems GmbH to understand the log output.
If you want to set up your own log upload service, you could direct the URL to
your server. The
upload.php will insert the log reports into the database
which could be viewed in
Manage Clients / Download Client Log Files.
The name of the Master Registration Server in your TeamDrive Network.
Default URL of the Master Registration Server.
For TeamDrive 3 clients using the free version, the media URL is used to download new banners from the server, which are to be displayed.
With TeamDrive 4 banners are not longer supported.
It’s possible to send notifications to other Space members with the client.
The notification URL will be used to send these notifications.
Please use the same domain as in
For an inital connection or later on the online test, the client will ping the
PingURL. This will return a defined answer:
<?xml version='1.0' encoding='UTF-8' ?> <teamdrive> <intresult>0</intresult> </teamdrive>
back to the client, so that the client can check if he can reach the server,
or if there is a proxy or an other gateway which require additional steps
to get internet access. The
PingURL can be located on another server
and just requires a file
ping.xml with the above content.
Default should be the same domain as in
IP address or host name of the HTTP proxy to be used for outgoing HTTP requests.
TCP Port of the HTTP proxy server to be used for outgoing HTTP requests.
This URL will be used by the client to open web pages in response to clicks within the client.
The client will add different parameters to the URL, so that the same URL can
be used to call different pages. The
RedirectorURL will not open the
expected target page directly, it will redirect the call to the right target
Therefore it’s possible to change the URLs later in the admin console without changing the client. There are different target pages defined:
ProviderInfoURL: Info page about available provider codes
ForumURL: A link to a forum
TutorialURL: Link to tutorials
HelpURL: Link to a general help page
FAQURL: Link to FAQs
TDPSOrderURL: Link to buy a license for a TDPS
LicensePurchaseURL: Buy client licenses
DownloadURL: A link to your client download page
ReferralURL: User invite user referral URL
These links could be changed using the admin console in the global settings for all provider or for each provider individual in the Provider settings (see Provider Settings).
Optional Reg Server API URL, used by the Administration Console (e.g.
http://regserver.yourdomain.com/pbas/td2as/api/api.htm). Must be set, if HTTPS
should be used for API communication or if a dedicated API server is used. If
empty, it will be derived from
The name of your Registration Server which should be defined together with TeamDrive Systems GmbH. The name must be unique within the TDNS network, and it can not be changed later on without reinstalling all clients.
This is the main URL which will be used by the Clients to register and interact with the Registration Server. This URL must always be reachable by the Clients to offer the services. If the URL is no longer valid the Clients have no possibility to reach the server again.
Location of various server log files that can be viewed from within the Administration Console via Server Management -> View Server Logs. For security reason this setting can only be changed directly in the database to avoid unauthorized access to other than the allowed log files.
Timezone used for date functions in the Adminstration Console. Please ensure
that the timezone is valid (see
/usr/share/zoneinfo/ for available time
zone information)! (default:
Enables backward compatibility with TeamDrive 2 clients.
Each client registration will store the IP address which was used to register the client. In case of a hacked account, it may be possible to identify the source of the request. The default is 2592000 seconds (30 days) after which the IP will be removed. Other possible values are -1 (never store the value) or 0 (never delete it). All values greater than zero will be taken as seconds. The Delete Client IPs auto task as described in “Delete Client IPs”-Task must be enabled.
Each new Registration Server in the TDNS network will be added to the
TD2RegServerList” table and must be white listed manually. You can define
an automatic whitelisting of new servers using this field.
This value will be used to activate the TDNS integration of the RegServer, so
that the users of your Registration Server can invite users of other
Registration Servers which are registered in the TDNS network. Each
Provider on a Registration Server needs an own
TDNS-ServerID and a
TDNS-Checksum value which will be defined by TeamDrive Systems. Without
these values your server can not communicate with the TDNS. The two values
must be set when for adding a new Provider on the Registration Server
(see TDNS Settings).
URL used to access the TeamDrive Name Server (TDNS).
This is the location of the default email and HTML templates.
The Clients will call this URL to retrieve update notifications about newer versions. For TeamDrive 3 clients the server will return a HTML file with update information which is then displayed in the client. For TeamDrive 4 clients only the new version number will be transferred. Upon clicking update in both client versions, the client will open a browser and direct the user to your download page. The update notification can be configured using the admin console (see Administrative Guide).
Set to True if outgoing requests must be sent via a HTTP proxy server.
This requires setting
ProxyPort as well. Note that Host
Server access uses different proxy settings (see
Whether the user email must be unique so that not two different accounts could use the same email.
This value is only valid per Registration Server. Duplicate emails within the TDNS network on a second Registration Server are allowed.
$false if usernames should be case sensitive. By default usernames
are case insensitive. Since case-sensitive usernames can be a security risk,
this is the recommended setting.
These settings allow to enforce some security related restrictions on the Administration Console.
The number of failed login attempts to a particular account within
LoginMaxInterval before further login attempts are subjected to a delay.
Time interval used by
LoginMaxAttempts, in minutes. (default:
Period of idle time before you need to log in to the Administration Console
again, in minutes. (default:
Log security events to a local syslog, rather than
The maximum number of search results that will be shown for any given request (0 == unlimited)
If set to a non-zero value, this is the maximum number of user records that
can be viewed within the interval defined by
The time interval that
UserRecordLimit applies to.