Release Notes - Version 1.0¶
Key features and changes¶
This is the initial release of the Web Portal.
Change Log - Version 1.0¶
After updating docker to version 1.12.6 the docker service might not
start anymore as described in the docker release notes:
Please remove the file
and add the
--host=tcp://0.0.0.0:2375 instead to the OPTIONS parameters in
/etc/sysconfig/docker as described in the docker configuration
Installing Docker chapter.
- Removed support for CentOS 6
- Fixed docker configuration
- Fixed PDF creation for this documentation
- Fixed download links for VM-Ware images
- Increased MinimumAgentVersion to 188.8.131.529 to support email notifications
- Fixed docker configuration
- Fixed apache 2.4 configuration
Updating the Host Server on CentOS 7 with “yum update” might
update the apache to a newer version. This update could re-install the
deleted “conf”-files in the folder
/etc/httpd/conf.modules.d/ and will
prevent starting the apache. Please follow the modified instruction to
disable all modules in the “conf”-files instead of deleting them as
described in Apache 2.4
Improved Docker installation documentation (WEBCLIENT-219, WEBCLIENT-223).
The Web Portal now checks if the user is authorised to access a Web Portal. A user is authorised to access a Web Portal if the Provider setting:
ALLOW_WEB_PORTAL_ACCESSis set to
ALLOW_WEB_PORTAL_ACCESSis set to
peruserand the user’s “Web Portal Access” capability bit is set (a user-level setting).
When using external authentication, the same check is done if the Registration Server is version 3.6 or later. When using a Registration Server 3.5 or earlier, the Web Portal will not check the user’s Web Portal access permissions (in the case of external authentication).
AllowedProviderswhich is a list of Provider codes of the users that are allowed to login to the Web Portal.
An input field on the setup page allows this variable to set during installation of the Web Portal.
https://webportal.yourdomain.com/portal/authservice.htmlis now the target URL for external Authentication Services acting on behalf of the Web Portal.
In other words, in successful authorisation by an external Authentication Service, the user is redirected back to this page.
The Web Portal will may add certain arguments to
- “portal=true”: This argument is always added to the URL. This is useful, in the case when the same Authentication Service is called by the TeamDrive Client and the Web Portal. The argument can be used to determine whether to redirect on successful login or not.
- “cookie=?”: This argument will be added if the Authentication Service provided a cookie after the last successful login. The cookie is stored by the TeamDrive Agent.
- “error=?”: This argument indicates that the Web Portal encountered an error after successful authorisation by the Authentication Service. It is a base-64 (URL) encoded string containing the error message. The error should be displayed in the login page served by the Authentication Service.
Support CentOS 7 with Apache 2.4
Increased MinimumAgentVersion to 184.108.40.2060 to support the space activities
False). This value must be set to
Trueto allow registration of users directly via the Web Portal.
Added login and registration pages: All of these pages redirect to the associated pages on the Registration Server. After login, or registration, the Registration Server redirects back to the Web Portal.
https://webportal.yourdomain.com/portal/login.htmlThis page allows users to login using two-factor authentication, if this has been configured.
/portal/login.htmlis now the default for the
https://webportal.yourdomain.com/portal/register.htmlUsing this page a user can register as a TeamDrive user without installing the TeamDrive Client. After registration the user has access to the Web Portal.
/portal/register.htmlis now the default for the
https://webportal.yourdomain.com/portal/lost_pwd.htmlThis page sends a temporary password to the user and allows the user to login and set a new password. The page is linked from
https://webportal.yourdomain.com/portal/setup-2fa.htmlUsing this page the user can configure two-factor authentication using the Google Authenticator App.
- The default of the ``AuthTokenVerifyURL` setting is now:
- Fixed a problem on login with a user registered via the Registration Server API using email address as identification (WEBCLIENT-205).
- Use the -v option when removing containers. This ensures that the container volume is also removed (WEBCLIENT-204).
- Framework synced with Host- and Reg-Server
- Added setting
MinimumAgentVersionwhich specifies the minimum version of the TeamDrive Agent that will work with the Web Portal. Upgrade to this version of the Agent is forced as soon as the new version of the Web Portal is online (WEBCLIENT-194).
- Updated documentation for Docker version 1.7.1
- Fixed Internet explorer caches API calls. (WEBCLIENT-186)
- Added description about the dependencies between Webportal, Provider and Reg-Server and normal and external Authentication. (WEBCLIENT-176)
- The performExternalAuthentication redirects to http:// instead of https://. (WEBCLIENT-182)
- The getLoginInformation() API call now returns “registerUrl” if the setting RegistrationURL, is set on the Web Portal. (WEBCLIENT-179)
- Redirect to the login page when a request to an agent returns a 503 code. This requires a manual update to the ssl.conf, refer to the documentation on server installation and configuration. (WEBCLIENT-198)
Fixed container language settings so that Spaces with non-ascii characters in the name now work.
Corrected redirect to external login pages under certain circumstances.
Login with an email address now works.
The Portal no longer creates containers based on the case of the input username, instead the actual username is used. This prevents the creation of duplicate containers for the same user.
The Web Portal session will now timeout after 15 minutes idle time. The user is then required to login again.
Implemented reset password functionality. Login after password has been forgotten now works. The user will receive a temporary password via email which is used to set a new password and login.
Note, new re-write must be added to
RewriteRule ^/requestResetPassword /yvva/requestResetPassword [PT] RewriteRule ^/tempPasswordLogin /yvva/tempPasswordLogin [PT]
Fixed loading of favicon
- OldImageRemovalTime setting was not visible.
- Updated Web Portal GUI to the latest 4.1.x version from the webfrontend branch.
- Initial public release
- Web Portal 1.0 requires TeamDrive Agent version 220.127.116.112 or later.