Welcome to Hub 2018.2
Hub 2018.2 introduces SAML Authentication Module, Throttling by Login, Personal Data Management and other improvements.
Hub installation packages now provide out-of-the-box support for secure connections over TLS. Upload your server certificate during installation or upgrade and encrypt data in transit without setting up a reverse proxy.
This authentication module lets you configure Hub as a SAML service provider. This lets users log in to Hub with credentials from a third-party SAML identity provider.
In Hub 2018.2 the IP-based throttling feature has been replaced with the option to apply rate limits to failed login attempts per login. Use it together with a reCAPTCHA feature to protect your installation from brute-force attacks without blocking users who have simply forgotten their passwords.
The settings that affect user authentication were moved from the System Settings page to a single page that stores common settings for all authentication modules.
Hub 2018.2 comes with new options that help you comply with requests from users who want to access or erase their personal data.
Project Overview pages now show widgets and README files on separate tabs. This means that you can view widgets without scrolling to the bottom of the page.
New views on the Groups page show you a list of project teams and a mixed mode that shows both groups and teams. We also added an action on this page that lets you merge a group into a team. Use this operation to eliminate group assignments that duplicate permissions that are granted to a project team.
Create a role that is similar but not identical to an existing role with just a few clicks. Use this action to create a new role with a set of permissions that is identical to an existing role, then add or remove permissions as desired.
All authentication-related settings have moved from the System Settings page to a new Common Settings page for all authentication modules. This page also contains configuration options for the new login-based throttling feature and the input fields for connecting to Google reCAPTCHA.
When using Hub as a SAML identity provider, you now have the option to specify the attributes that the SAML service provider uses to store the user login, full name, and email address.