Release Notes - Version 4.5¶
The most significant additions to the Registration Server in this version are the “Super PIN” functionality, and support for a new “on-boarding” process.
The Super PIN functionality is required to support client-side “local encryption”. The Super PIN is activated for a user account when client-side local encryption is enabled by the TeamDrive client.
Local encryption adds an addition layer of security by protecting important data stored on then client. When using a Web Portal, local encryption is automatically enabled.
When the Super PIN is activated, the user may no longer set their password using a temporary password. If the user forgets their password they must either enter their Super PIN, or a Recovery Code, which is obtained using a “Recovery URL” (stored as a QR Code).
The user will be promoted by the TeamDrive client to export and store this information when the Super PIN functionality is activated.
It is now possible for a provider to reserve domains and register external authentication services. Reserved domains must be activated by TeamDrive before they are used. When activated, domain reservation, prevents users of other providers from using email addresses with the reserved domains. In addition, external authentication services can be registered and then associated a reserved domain.
This information used by the TeamDrive client to locate the correction Registration Server during login and registration (required client 4.6.9), and the domain-based external authentication selection service.
Domain and service information is stored on TDNS (the TeamDrive Name Service), and can be managed using the Registration Admin Console.
The new on-boarding process involves the automatic creation of user accounts when
a user is invited to a space (see the new
INVITATION_CREATES_USER provider setting).
The user is registered using the email specified in the
invitation, and does not have a username (which means that
must be set to
default, see USER_IDENTIFICATION_METHOD).
An email (the reg-activationsetpassword email template) is sent to the user with a
link which allows the user to set a password for their user account.
Activation is optional (see
Note: if the user is not activated within a certain number of days, specified by
AUTO_CREATED_USER_TIMEOUT, then the user will be automatically deleted. By default
this is 60 days (see AUTO_CREATED_USER_TIMEOUT for details).
Users added by invitation, are listed as “guests” members of an account, if they are invited by a member of an account (REGSERVER-1504). Guest users can then be easily added to the account as member or manager.
After setting a password, the user may be provided with links to a Web Portal, or with a link to download the TeamDrive client. This can be done by configuring the relavent HTML templates, in particular set-password-ok. After login, using email and password the user will have access to the space to which they were invited.
On-boarding in this manner is the default when a user is created in the Admin Console. In other words, after creating a user in the Admin Console the user is sent an email with a link that allows the user to set their password, and after doing this proceed to a Web Portal or to download the TeamDrive client.
Users that are on-boarded automatically using this functionality can be granted a
special license as specified by the
NEW_USER_LICENSE_FEATURES provider setting.
In addition to these changes, it is now possible for a manager to invite an existing users to an account. Support is provided for this in the Registration Server API and the Admin Console. Invited users can be assigned a license which will be applied when the user accepts the invitation. Licenses assigned during invitation are counted to the usage of those license.
Registration Server Functionality¶
Added support for registration of users without a username in the TeamDrice client.
[[SUPERPIN]]conditional template variable is now used in the new-passwd and web-newpassword templates to return an appropriate message to users that attempt to change their password using an old TeamDrive client, after the Super PIN has been activated (REGSERVER-1447).
Conditional blocks in templates may now have the form
ELSEmarkup tag is optional).
SUPERPIN_LOGIN_WITHOUT_ACTIVATIONsetting which determines whether an activation email is sent the user when using a Super PIN to login to a new installation (REGSERVER-1451).
TEMP_PASSWORD_TIMEOUTprovider setting which determines the amount of time a temporary password valid (REGSERVER-1438). Default is 10 minutes.
MAXIMUM_DEVICES_PER_USERprovider setting. The default value is zero, which means no limit. If set to another value the new “Deactivate/Activate Devices” auto task will enabled and disable devices as required to ensure that only the specified number of devices are active. The disabled devices are set to the “too many devices” status (REGSERVER-1399).
The server always disables the least recently used devices. As a result, a device can be reenabled by simply running the TeamDrive client. However, it takes an average of 3 hours before a device is reenabled by the server.
The device status is now sent to the TeamDrive client which should disable the GUI and stop synchronisation when the status of the devide is disabled.
In this state the device will receive invitations, but will not send them to the client. This ensures that if the device is enabled, then the invitations will be sent to the client.
Added new provider settings:
ACTIVATE_ON_INVITATION(see INVITATION Settings).
These new settings belong to the
INVITATIONsettings group, which was previously called the
A new email template, inv-newuser-invited, has been added (see Templates for Client Actions). This template is used when a user is automatically registered by the new
INVITATION_CREATES_USERfeature (see above).
[[DISCLAIMER]]email template field has been added to all email templates to which it may apply (REGSERVER-1290). The disclaimer text can be set in the Admin Console under the account of the user. If no disclaimer text is available, then the
[[DISCLAIMER]]field is removed, including the extra empty line that results from this.
When the TeamDrive client requests the “default” depot, the Registration Server will now return any depot that the user has in use, if the user’s “cloud depot” and default depot’s do not exist.
Added the NoDepot license feature which disables the creation of a default depot for new users (see DEFAULT_FREE_FEATURE).
The server now retains the “default” depot status, when the default depot is removed from usage. As long as the user’s default depot is either in-use or is owned by the user, it retains the “default depot” status for the user.
In addition, the default depot status will be restored to a depot, if it is removed from the user (both in-use and ownership), and then added again, as long as the user is not given a different default depot.
As long as the user has a default depot, no new default depot will be created.
In previous version of the server, removing the usage of a the default depot from a user would cause a new default depot to be created (assuming
HAS_DEFAULT_DEPOTis set to
True), as soon as a TeamDrive client calls the Registration Server.
ALLOWED_DIST_CODESis now also applied on user registration. However, this is only done when the client sends the distributor code from the DISTRIBUTOR file (REGSERVER-1402). This required client version 4.6.8 or later.
For login, clients before this version were not sending the distributor code from the DISTRIBUTOR file if users entered a different code in the Provider panel. In this case the server was checking the entered distributor code.
In the case of external authentication all client version send the correct distributor code (the distributor code from the DISTRIBUTOR file).
Added a checkbox to accept the “Terms of Service” on the portal registration page (template: portal-register), and the set password activation page (template: set-password) (REGSERVER-1450).
REDIRECT_TERMSprovider setting which specifies the “Terms of Service” page. A reference to this page is used in the portal-register and set-password HTML templates.
Added depot template: depot-warning, depot-cancelled, depot-reduction and depot-reduced which are used by the Host Server to inform the managers and owners when depots usage has exceeded the required limit (see :ref:mail_templates_for_depots).
USE_SENDER_EMAILsetting has been deprecated, and replaced by
FROM_EMAIL_OPTIONS(see FROM_EMAIL_OPTIONS). The
FROM_EMAIL_OPTIONSvalue is set by default so that the behaviour of the Registration Server in this regard will not change (REGSERVER-1452).
EnableDomainSupport(TDNS) setting. When set to
Truethis setting enables the support for the reservation of domains and registration of service by a provider.
PREVIOUSLY_UNNAMED_SERVICES(AUTHSERVICE) provider setting. This setting must be used when upgrading an existing external authentication service to a “named” service. “Named” services are services registered globally on TDNS (This is done using the Admin Console).
Changes to provider settings:
- Renamed settings group:
- Renamed settings group:
- Rename setting
- The following setting have been moved from
- Renamed settings group:
Documentation: updated screenshots in section Using the Administration Console
The email template: reg-registrationnotify, which was previously unused, is now sent after a user sets a password using the link sent in the activationsetpassword email. The
[[PASSWORD-SET]]template variable is also set to
truein this case.
Added global setting:
EmailSendRate, which determines the maximum rate at which emails will be sent. The default is “0”, which means unlimited. Any other value is the number of emails that may be sent per minute.
SPACE_SIZE_LIMITprovider setting which restricts the size of spaces for users with a restricted or non-professional license (REGSERVER-1502).
Fixed TD2OwnerMetaHistory does not exist error when updating from Registration Server 4.0.1 (REGSERVER-1520).
Registration Server API¶
The “registeruser” API call now supports the option
<nodepot>which, when set to
true, prevents the assignment, or creation of a default depot for the user. In addition, a depot may be assigned to a user on registration using the appropriate tags (REGSERVER-1326).
The new “inviteusertoaccount” API call can be used to invite a user to an account via email. The call will send the “account-manager-invitation” or “account-member-invitation” email template depending on the type of invitation. The user is provided with links in the email to either accept or reject the invitation (REGSERVER-1289).
The function to invite users to an account is also available in the Admin Console.
The “tdnslookup” API call will now work, even when the Registration Server is not connected to TDNS. In this case the call will return information from the local database (REGSERVER-1410).
<messagetext>tag to the “registeruser” API call. This tag specifies a message that can be placed in the email sent by the call use the
Also added a
<sendcc>tag (default is
false). When set to
truethe Registration Server will “CC” the email sent to the user, to the caller (set by the
All email addresses must now have the form: firstname.lastname@example.org, where x is one or more characters. White space, ‘,’ and ‘;’ are not allowed (REGSERVER-1471).
Added “getsettings” API call. A list of Registration Server and provider settings can be specified, using the
<settings>tag. This tag is also supported by the “getuserdata” and “getaccountdata” API calls (REGSERVER-1511).
The Admin Console will indicate if the Super PIN functionality has been activated, and also allows managers to disable the Super PIN functionality, which will delete the user’s Super PIN.
Only delete the user’s Super PIN if the user has lost both their Super PIN and their password. After removal, the user may then set their password using the temporary password functionality, however previously local encrypted client installations will not be accessable, including Web Portal containers.
In addition, the user will loose access to space keys stored in the Registration Server’s key repository.
It is now possible to specify a banner and a footer for the Web Portal user interface, for all users of an account, see Customize Web Portal under Extended Settings (REGSERVER-1433).
Host Servers can now be assigned to accounts (REGSERVER-1299). In this case, the account Host Server overrides the Host Server specified by the
HOST_SERVER_NAMEprovider setting. In addition,account managers are able to set the following parameters at the account level:
Default depot: Determine whether members of the account have a default depot. This setting, can override the provider level settings
Storage size: This is the storage size of default depots created. This setting override the
Traffic limit: This sets the traffic limit of default depots created. This setting override the
See HOSTSERVER Settings for more details on these settings.
When creating a user, a checkbox has been added which allows you to prevent the creation or assignment of a default depot.
Note that a default depot will nevertheless be created with the user’s first client registration, unless:
- the user belongs to an account with a default account depot,
- the user’s account has a host server and the Default depot account level setting to prevents the creation of a depot,
- the user’s license has the NoDepot feature.
The “Purchase License/Depot” buttons now open a new browser page or tab (REGSERVER-1281).
UI improvement: the background of the paging control is now transparent.
The user’s account depot is now included in the user’s list of depots (REGSERVER-1419).
Added domain and external authentication service management. This is only enabled when the setting
False). This functionality requires TDNS 1.9.11.
Depot lists now have separate columns for Storage/Traffic limit/used and can be individually sorted (REGSERVER-1472).
Added a new
InboxUploadFormaccount-level setting, which can be used to configure a form that users must fill out before uploading files to an inbox
The domain-based selection of the external authentication service (
domaindirectory) now uses the reserved domain information, and the associated authentication services to direct user’s to the correct external authentication service.
The other external authentication services have been updated to check the configuration using the information stored centrally (TDNS 1.9.11).
Check the example configuration files for information on the new settings, and changes you need to make to upgrade services.
Release Notes - Version 4.1¶
Changed collation of all emails columns to case-insensitive (REGSERVER-1480).
All input email are converted to lower-case: in import, and email addresses from external authentication services (REGSERVER-1479).
Fixed format of output on “Download Client Log Files” page. Long “words” are are now wrapped as required (REGSERVER-1481).
RedirectorProtocolserver setting which can be used to specify the protocol of the “redirect URL” (REGSERVER-1473).
Fixed a problem that prevented update notifications to the TeamDrive clients from working (REGSERVER-1474).
Added a new provider setting:
UPDATE_TEST_VERSIONwhich can be used to set the version to be used testing an update notification (see UPDATE_TEST_VERSION).
Admin Console: fixed problem with Provider Codes that consist only of digits (REGSERVER-1028). This caused various problems, for example, it was not possible to create an inbox.
Fixed a problem that caused the “Expire Licenses” auto-task to fail when a license belonging to an inbox user expired. The error generated was “The inbox user must have a license with the inbox feature” (REGSERVER-1466)
Fixed the “Lock wait timeout exceeded” errors, that occurred due to an UPDATE to the TD2Message that was performing a table scan (REGSERVER-1465).
Change required for compatible with yvva 1.5.2.
Added documentation for web portal settings. The setting
API_WEB_PORTAL_IPhas been moved to the WEBPORTAL settings section.
Admin Console: the Manage Licenses page now includes the option to search for “Inbox” licenses (REGSERVER-1436).
Admin Console: the License Report page was not working due to an error when retrieving the report list from the database (REGSERVER-1444).
When moving spaces to another depot, it was possible to move a space to a depot to which the account manager did not have access (REGSERVER-1442).
Corrected email template usage when forcing re-login or reseting a user’s password. The email templates sent for these actions were reversed.
Admin Console: corrected “Force Re-Login/Invalidate Password” functionality in the case where
USE_AUTH_SERVICEis set to
AUTH_LOGIN_URLremains blank. In the case, external authentication is not being used (since
AUTH_LOGIN_URLis required for external authentication, instead the Registration Server Portal login pages have been activated.
As a result, the “Force Re-Login” button should read “Invalidate Password” in this case. This is due to the fact that invalidating the user’s password has a different effect, depending on whether external authentication is being used or not.
This will be changed in Registration Server 4.5, where only the “Force Re-Login” functionality will be provided, in both cases, i.e. whether external authentication is being used or not.
Admin Console: fixed crash when logging in with email address, instead of username.
[account] in redirector URL will now be replaced with blank, if the user has no account.
CSV import results displayed on the “CSV User Imports” page in the Admin Console, can now be viewed in the browser rather than downloaded directly. A success and/or error file is only available for viewing if at least one success or failure occurred during the import (REGSERVER-1398).
In the Admin Console, the selection method used in dialogs has changed. If multi-select is allowed, then the checkbox are used to indicated which items have been selected. In the single selected case, radio buttons indicate which item has been selected.
Currently adding members to an account and users to a license allow multi-select. A “Select All” button is also available in these cases. An extra dialog, confirming your selection is presented when adding more than 15 users (REGSERVER-1397/REGSERVER-1418).
In addition, the paging section above search results has been improved to provide more options. You can now jump to the beginning or end of the result, and also move ahead or back a number of pages by clicking ”...” (which is only available when sufficient pages are available).
Since version 4.0 the Registration Server is compatible with PHP 7.2 / 7.3. However, the Admin Console may have problems after upgrading PHP due to the fact that the “mysql” extension has been removed from PHP 7 and later. Documentation has been added to help users solve this problem: Using version 4.0 with PHP 7.2 / 7.3.
Added Web Access to the account-level client settings. The default values of the account-level client settings are now determined by the provider setting
In the Admin Console, on the Depots page, you can now search for the depot owner’s email in addition to the owner’s username. The owners email address is also display in the list (REGSERVER-1411).
Added “web-user-deleted” email templated which is sent to the user after the user’s account has been deleted (REGSERVER-1405).
On login to the Admin Console the username is now case-insensitive (REGSERVER-1406).
Template names are now displayed in the Admin Consoles email queue (REGSERVER-1409).
An “inbox” type license can now be created in the Admin Console (REGSERVER-1414).
Registration Server API¶
- Emails sent by the API may now include the following email template
[ORIGIN-USERNAME-AND-EMAIL]. These variable will be empty unless the
<changeuser>tag has been set in the API call. The “web-activationsetpassword” template has been changed to include a reference to the originator of the email, if the
<changeuser>tag is set (REGSERVER-1413).
- Added an option to change a user’s account in the Admin Console (REGSERVER-1407).
This function is supported by the addition of the
<removemembership>tag to the “addusertoaccount” API call.
- Added documentation for the “updateuser” API call (REGSERVER-1408).
- Fixed a error that prevented users from being removed, after the Provider was deleted. The problem occurred after the Provider was removed from TDNS (which is required in order to delete a Provider).
- Added the provider setting required to connect the Registration Server to a web portal API. This API can now be used to create an inbox service for an account. The user which is hosting the inbox needs a license with the inbox feature.
- Removed the banner management page in the Admin Console. The Banner administration of banners. This includes the Banner feature bit used by licenses. This feature is still displayed for licenses with this feature bit, but the feature can no longer be set.
- The Personal license feature is no longer supported by version 4.1 of the Registration Server. This feature was only used by TeamDrive 3 clients. Users must now use the Professional license feature instead of the Personal license feature.
- Changes to provider settings are now recording in a change history. The change history of provider settings can be viewed in the Admin Console.
Release Notes - Version 4.0¶
- [account] can now be used in the help redirect URL
- Several bug fixes and improvements to version 4.0.0
Registration Server Functionality¶
Removed the provider setting:
HOST_SERVER_URL. This is no longer required, the Host Server to be used is specified by
Added support for accounts (REGSERVER-1229). Accounts belong to a provider and include a number of users, groups, depots and licenses. An account is administered by a number of managers. A user can only belong to one account, but may be manager of a number of accounts. Accounts are explained in the the new chapter Account Concept and in a adminconsole chapter Accounts.
Added support for groups (REGSERVER-1196). Users can be invited to join a group, which is administrated by a Group Manager. The user receives an email, which contains a link for joining the group and another link for rejecting the invitation. Users that have rejected invitation 3 or more times can no longer be invited to a group.
Users can only belong to one group, so when the join a group they are automatically removed from any other group.
The Manager of a group can assign a license and a Host Server Depot to the group. The group license and the group Depot are used by all members of the group, and have priority over the user’s default license and Depot.
Please notice that group functionality is not available in the 4.0 release of the Admin Console. This will be added in version 4.1.
UserNameCaseInsensitivehas been deprecated. All Registration Servers now use case-insensitive usernames. The TDNS entries will be automatically updated of your server had
The Registration Server now uses a new mechanism to synchronise the Depot usage with the Host Server and the TeamDrive Client. The mechanism ensures that changes to Depot usage on the Registration Server is always reflected in the Depot list in the TeamDrive Client, and in the Depot access list on the Host Server.
Previously, it was possible that there were differences in the Depot configuration for a user between the TeamDrive Client, Registration Server and Host Server. This was due to a number of factors:
- The Host Server access list for a Depot was previously not updated by the Registration Server API.
- By setting
<sendtoclient>false</sendtoclient>in an API call the user could previously specify that the changes to the Depot configuration of a user are not sent to the TeamDrive Client. This tag is now deprecated (see below).
- If a TeamDrive Client device was not in use for a long time it was possible that changes to the Depot configuration were lost.
The following characters are never allowed in usernames: ‘$’, ‘;’, ‘,’, ‘@’ ‘”’ and the single quote (“’”).
When setting up a Registration Server, the server name is not allowed to contain a ”.”, or any spaces. The server domain must be valid, and contain at least one ”.”.
DEFAULT_ACCOUNT_FEATUREprovider setting which is identical to the
LICENSE_FREE_FEATUREbut applies to users that belong to an account (REGSERVER-1253). If
DEFAULT_ACCOUNT_FEATUREis empty then the Admin Console will not allow managers to create a new license when adding a user.
ACTIVE_SPACES_LIMITprovider setting which determines the maximum active spaces for users with a restricted license (REGSERVER-1257).
PROVIDER_LOGIN_IDsetting which is a list of IP addresses of users that may login with provider level or higher privileges (REGSERVER-1333). On upgrade this setting is set to the value of the
LOGIN_IPvalue, if this value is not empty. Providers that wish to allow normal users or account managers to access the Admin Console from any IP address must set
License that expire are now also valid on the “Valid Until” date (REGSERVER-1389).
The Registration Server was sending an incorrect result to the client when a disabled user requested a temporary password (REGSERVER-1237).
Removed deprecated auto task: “Move Store Forward Messages”.
Fixed possible deadlock involving the Devices table and the “Delete Client IPs” auto task (REGSERVER-1464).
Registration Server API¶
The output parameter
<number>in the searchuser API call, and the getlicensedata API call has been deprecated and will be removed in a future version. Use the license key number now returned in the
The Host Server API URLs returned by the API will now begin with “https://”, if the provider setting
API_USE_SSL_FOR_HOSTis set to
Added “createdepot” API call.
Added API calls to support account functionality: “createaccount”, “deleteaccount”, “addusertoaccount”, “removeuserfromaccount”, “assignaccounttolicense”, “removeaccountfromlicense”, “setdepotaccount”, “removedepotaccount”, “setgroupaccount”, “removegroupaccount”, and “getaccountdata”.
Added API calls to support group functionality: “creategroup”, “deletegroup”, “inviteusertogroup”, “removeuserfromgroup”, “setgrouplicense”, “removegrouplicense”, “setgroupdepot”, “removegroupdepot”, “userjoinedgroup”, “setgroupclientsettings”, and “getgroupdata”.
A number of API calls now also return group related information: “loginuser”, “searchuser”, “getuserdata”, “getlicensedata”, “getdefaultdepotdata”.
The “getuserdata” call now return account and group information by default. Set the input tags:
falsein order to exclude this information. This call also returns license currently assigned to the user in the
<license>block in the
truethen this is the group license if the user belongs to a group with a license.
The calls: “loginuser” and “getlicensedata” return the user’s group information by default. Set the input tag:
falsein order to exclude the group information.
The calls “searchuser” and “getdefaultdepotdata” do not include group related data by default. In this case you must explicitly set
trueto receive this information.
<depot>block returned by the calls “getuserdata” and “getdefaultdepotdata” calls includes a number of new tags:
<globalid>is the global identifier of the depot.
<iscloud>is set to
trueif the depot is the user’s default cloud storage.
<isaccount>is set to
trueif the depot is set on the account level.
<isgroup>is set to
trueif the depot belongs to the user’s group.
When returning information about licenses (
<isgroup>tag is now included. This tag is set to
trueif the license belongs to the user’s group.
In the “registeruser” API call new supports a number of new tags:
<sendmail>(see registeruser for details).
<sendtoclient>tag is the API calls: “setdepotforuser” and “removedepotfromuser” is deprecated. If present, the tag is now ignored by the Registration Server. Changes to the usage of a Depot are now always sent to the TeamDrive Client.
Added API calls: “syncdepotdata” and “getdepotdata”.
API calls that send emails now support the
<sendmail>tag. This allows the caller to override the
API/API_SEND_EMAILsetting, to determine whether an email is sent or not.
<changeuser>tag is used to specified the username of the user that is making changes to depots.
<setpassword>tag to the “registeruser” API call. When set to
false), this will send an email using the web-activationsetpassword template to the user. This email contains a link to the set-password HTML template, which allows the user to set his password, and activate his user account (REGSERVER-1320).
Rearranged the menu of the Admin Console and extended the user right levels for viewing, creating, editing and deleting objects (see User Rights).
Restricted the view presented by the Admin Console to only those pages that a user has the right to view. Any TeamDrive user with login privileges may login to the Admin Console, and view and manage their resources.
Added a global provider drop-down menu, so that users with access to more than one provider can select a Default Provider for all operations.
Added account management.
Added new categories for Registration Server settings: API, Proxy, RedirectURL and TDNS (REGSERVER-1227).
Added an automatic redirect to the login page when the login session expires.
If a Depot is deleted and then undeleted on the Host Server, an “Undelete Depot” button is available in the Admin Console to make the depot available again.
The “Force Re-Login” function is not always available on the Edit User page. Previously this function was only available if external authentication was in use (REGSERVER-1469).
The function to “Invalidate Password” is available, in addition if the Super PIN functionality is not enabled, and external authentication is not in use.
“Force Re-Login” is also available in the Manage Users page, where it effects all user in the selection.
Forcing a re-login will require the user to login again on all installed devices.
All external authentication services (except
vasco) now use the same functions to evaluate input and generate the authentication token.
The services can now be deployed by following the instructions in the
*_config.php.examplepage to create a configuration file, and then customising the HTML in the
However, be careful to preserve the PHP dynamic tags in these files, which all have the form:
<?= .... ?>and
<?php ... ?>.
Future upgrades will be done (in most cases) by simply replacing all files accept
Note that the
authdirectory is now used by all authentication services, and
auth\vendoris used by the Google and Azure services.
Added support for Google and Azure OAuth2 external authentication. To use these services:
- follow the instructions in the
*_config.php.examplepage to create a configuration file, and
- customise the
*_login.phppage to suite your purpose.
- follow the instructions in the
Added domain-based selection of the external authentication service (
domaindirectory). The initial page of this service requests the user’s email address. Based on the domain of the email address the user is forwarded to the appropriate authentication service.
The mapping from domains to authentication services is configured in the
dom_config.ini.examplefor notes on how to created this file.
Using this service, the users of a single provider can use various authentication services. If this is the case, then each authentication service must be given a unique name, which is used as a prefix to the external authentication (External Auth. ID) of the user to avoid duplicate IDs.
The LDAP external authentication has been updated to evaluate options from various clients, including: the TeamDrive client, the Web Portal, and the TeamDrive agent.
As a result, the
ldap_login.phppage can be used in all cases, and the
ldap_agent_login.phppages, are no longer needed, and have been removed.
Follow the instructions in the
ldap_config.php.examplepage and read the information about the LDAP encryption parameters (see Encryption Parameters) when upgrading from an older version of the LDAP authentication service.
In addition, the
$provider_codesetting has been deprecated. When upgrading, copy the value of this variable to the position of the first URL in
$allowed_origins(see Agent/Portal Parameters for details).