Roadmap

This page is a scratchpad for ongoing discussion at syncope-dev@incubator.apache.org

Features

Authentication chain (GoogleCode issue 274)
Pluggable authentication modules (GoogleCode issue 274)
Realm-based authorization (GoogleCode issue 272, Mail thread 1, Mail thread 2)
PDC-based authentication (GoogleCode issue 96)
Passthrough authentication (GoogleCode issue 273)
Delegation (GoogleCode issue 102)
Enhance password management (GoogleCode issue 218)
1. Policy-compliant random password generation
2. Password change on an external resource only
3. Password reset
4. One-time password
Password required for resource subscription (GoogleCode issue 264, Mail thread)
Remove MD5 as a supported password cipher algorithm (SYNCOPE-51)

Support more than one local connector bundles directory and zero or more ConnId's connector servers (GoogleCode issue 168)
Scripted SQL connector bundle (GoogleCode issue 277)
Investigate support for OpenICF connector bundles

Role/membership attributes synchronization (SYNCOPE-26)
Add ability to search for Roles via the REST API (SYNCOPE-44)
Dynamic role memberships (GoogleCode issue 219)
Role propagation / synchronization (GoogleCode issue 22)
Role workflow (GoogleCode issue 23)
Assign membership and role schemas to either all memberships / roles or only some memberships / roles

Don't expose some REST list methods for anonymous (currently needed for self-registration)
Easier and cleaner way to override REST methods (for WAR overlays)
Rich client library, hiding REST call details (GoogleCode issue 104)
Enlist RESTful methods (GoogleCode issue 250)

Manage creator, lastmodifier and approvers information about each SyncopeUser bean (SYNCOPE-15)
Virtual attribute cache (GoogleCode issue 276)
Better way to override console components (for WAR overlays)
Avoid duplication in console's authorization management
Refresh button in console task modal windows (GoogleCode issue 248)
Cancel button for console modal windows
General console code reorganization
Provide Task entities a name and an optional description
Allow user, role and membership properties (like as id and name, for example) to be used in derived schema definition

Investigate using Apache Shiro to provide Syncope AM features
Add functionality to map a role to a "resource", which is a String or URI. There may also be a permission associated with this mapping such as "read", "write" or "execute", etc. In this way we can use Syncope to see whether the authenticated user has the correct permissions to access a local resource.

Add support for "bulk" operations via the REST API. For example, creating/deleting/reading a set of users/roles/resources with one operation.
Since bulk operations apply for huge number of entries, take care in dividing responsibilities between REST controllers and REST client code

Add the possibility to execute propagations in parallel. Consider that we must continue to propagate towards primary resources sequentially, in respect of the specified priority. May be propagations towards non-primary resources can be executed sequentially in respect of the priorities specified and in parallel in case of resources with the same priority.
Modify propagation mechanism in order to avoid to propagate useless update operations in case of no changes happened. By adding this feature we should resolve problems related to circular synchronization calls.