The production release of v7 is here with version 7.73.146, with multilanguage support and PHP 7 support.
Here you have the most important new features of the new v7 version:
As we're closing 2016 we'd like to present you a new beta version of Team Password Manager, specifically version 7.72.144 (Beta v7/3), with the following new features:
- Multilanguage support. Read this document to see how languages work in Team Password Manager: http://teampasswordmanager.com/docs/languages. Basically multi language support is complete except for the EULA, help pages and other minor strings, which will be ready for the production release.
- PHP 7 support.
- Date and time format parameter.
- Corrected bugs and the two latest patches from the previous version (22.214.171.124 and 126.96.36.199).
We've recently released two patches for version 6.68.138:
• Patch 188.8.131.52: this patch solves a vulnerability found in import (normal and my passwords) in which an attacker could create a remote code execution exploit.
• Patch 184.108.40.206: This patch makes error/exception dumps shorter so that no internal information is exposed.
We recommend you apply them if you have version 6.68.138. If you have an older version we encourage you to update it to 6.68.138 and apply them.
Some days ago we released two new products that work with Team Password Manager: an extension for Google Chrome and an importer for passwords (and projects) stored in the popular KeePass Password Safe password manager. Both products are still in Beta.
This is a free extension for Google Chrome that connects web login forms to Team Password Manager, allowing the user to:
- Automatically fill the username/email and password fields of these login forms, getting the data from Team Password Manager.
- Save web credentials (URL, username/email, password) to Team Password Manager.
Here you have a screenshot of the screen used to save a password:
Today we're releasing a new version of Team Password Manager (6.68.138) with the following features:
- Multiple LDAP servers: you can now define up to 3 servers to authenticate users against.
- LDAP timeout: parameter to set a timeout for LDAP authentication.
- Proxy settings for the version checker.
- Inactive users do not take up a license: this will allow you to just disable a user instead of deleting her.
- Modal screen to select the manager in project and password security: in installations with many users, a dropdown was just impractical.
- Integrate Patch 220.127.116.11, which corrects a security bug.
Like we did with 2013 and 2014, we take a moment today to review what we did in 2015 and also to tell you what we have planned for 2016.
Review of the year 2015
In 2015, Team Password Manager underwent some big structural changes. We spent several months developing hierarchy in projects, a new permissions system and an improved UI. As a result, V6 was born.
Today's new release of Team Password Manager (6.63.136) doesn't have any new feature but it has lots of improvements on existing ones. Read on.
Copy to Clipboard
Today we're releasing the final version of V6 (6.56.118). This version has lots of changes, but the two most important ones are: projects hierarchy and a new permissions system.
Now you can organize projects in a hierarchy. You can use the tree on the new left sidebar to see the hierarchy:
Today we're (finally!) releasing a general public version of Team Password Manager V6. V6 Beta 5 is possibly going to be the final beta, with an estimated production release at the end of August. We'd prefer you didn't use this version in production, but you can use it to test the loading of data and its functionality. The software it's fully usable, but we're going to take some more days to polish it even more, specially the UI.
Here's a general screenshot of how it looks:
As we've been announcing before, V6 brings the following new features:
Some of you have asked us what changes will V6 bring to the API. If there'll be a new API version. If the current API versions will work. And so on. So we've decided to write this post explaining these changes:
1. API v1 and v2 will no longer be available
These have been available for a long time and maintaining them doesn't make sense with the new permissions and hierarchy model. Also, you can easily convert v1 and v2 projects to v3 without much hassle.
2. API v3 (the latest API version) will still be available
But it will be marked as deprecated and will be discontinued in future versions of Team Password Manager. Internally, to adapt to the new permissions and hierarchy model, some changes have been made. The interface will basically be the same, but its functionality will be limited with the new model. These are the things you'll need to consider (you might want to check the screenshots at the end of the post to understand some of the new features):