Differences Between Shares 1.x and Shares 2.x
Architecture
The table below shows the major architectural differences between Shares 1.x and Shares 2.x.
| Shares 1 | Shares 2 |
|---|---|
| Flat structure of Shares | Hierarchical structure of organizations, projects and shares |
| System admin and share manager | System, organization and project level administration. User manager role for administering users |
| System admin manages everything | Resources (users, groups, teams, nodes) can be made available to lower level admins by higher level admins |
| Nodes can be made available to organizations and projects with docroots | |
| Basic Auth | Authentication system is entirely OAuth based |
| Username is the unique user identifier for all users. Email uniqueness not enforced | Email address is the unique user identifier. Supports username for remote users if email is not present |
| Separate API code | First class RESTful JSON API: UI and API use the same code, all actions are accessible via API |
Feature Support
The following features are not supported in this version of Shares 2.x.
- Home Shares
- Bookmarks
- Adding default shares for all directory service users
- Activity log in the UI
- Backup and restore in the GUI
- Backup and restore functionality for Windows
- Per Share Notifications. Instead, Shares 2.x has two options:
- Global setting for the entire system
- Per-user setting that users can change themselves
- IBM Aspera Console integration with Shares (API logins)
- Transfer control (pause / resume for share to share transfers)
Note: If you require a feature in Shares 1.x that is not supported in Shares 2.x, you should not
upgrade at this time.