...

1.1.0 (Ad libitum)

Release date: Q3 2012

Issues

See updated list on project's JIRA.

1. [SYNCOPE-119] Realm-based authorization
2. [SYNCOPE-120] Avoid duplication in console's authorization management
3. [SYNCOPE-121] Policy-compliant random password generation
4. [SYNCOPE-122] Password change on an external resource only
5. [SYNCOPE-51] Remove MD5 as a supported password cipher algorithm
6. [SYNCOPE-100] Add more password encryption options
7. [SYNCOPE-15] Manage creator, lastmodifier and approvers information about each SyncopeUser bean
8. [SYNCOPE-123] Support binary schema for user, role and membership attributes
9. [SYNCOPE-124] Prevent task execution request for running tasks
10. [SYNCOPE-125] Derived and Virtual attribute use cases
11. [SYNCOPE-126] Database import / export and related tasks
12. [SYNCOPE-127] Workflow: concepts, how to customize and how to trace
13. [SYNCOPE-128] Self-registration

1.2.0 (Intermezzo)

...

4.0.0 (Notturno)

Issues

See updated list on project's JIRA.

1. [SYNCOPE-129] Delegation
2. [SYNCOPE-130] Avoid propagating useless update operations
3. [SYNCOPE-131] Assign membership and role schemas to either all memberships / roles or only some memberships / roles
4. [SYNCOPE-132] Don't expose some REST list methods for anonymous
5. [SYNCOPE-133] Add UserRequestController.execute() that will execute the provided UserRequest and remove it on success
6. [SYNCOPE-134] User, role and membership properties for derived schemas
7. [SYNCOPE-135] Password reset
8. [SYNCOPE-136] Password required for resource subscription

1.3.0 (Jazz)

Release date: Q1 2013

Issues

See updated list on project's JIRA.

1. [SYNCOPE-137] Support more than one local connector bundles directory and zero or more ConnId's connector servers
2. [SYNCOPE-138] Scripted SQL connector bundle
3. [SYNCOPE-139] Support OpenICF connector bundles
4. [SYNCOPE-140] Dynamic role memberships
5. [SYNCOPE-141] Parallel propagation ops
6. [SYNCOPE-142] Asynchronous propagation ops
7. [SYNCOPE-26] Role/membership attributes synchronization

1.4.0 (Preludio)

Release date: Q2 2013

Issues

See updated list on project's JIRA.

1. [SYNCOPE-44] Add ability to search for Roles via the REST API
2. [SYNCOPE-143] GUI installer
3. [SYNCOPE-144] Provide Task entities with a name and an optional description
4. [SYNCOPE-145] Configurable user request approval
5. [SYNCOPE-146] Provide asynchronous refresh of tasks and reports list
6. [SYNCOPE-147] Provide refresh button in task and report modal windows
7. [SYNCOPE-148] Provide cancel button for all modal windows

2.0.0 (Virtuoso)

Release date: Q3 2013

Issues

1. Easier and cleaner way to override REST methods (for WAR overlays)
2. Rich client library, hiding REST call details (GoogleCode issue 104)
3. Enlist RESTful methods (GoogleCode issue 250)
4. Support SCIM REST API
5. Use logback-audit for auditing
6. Virtual attribute cache (GoogleCode issue 276)
7. Better way to override console components (for WAR overlays)
8. General console code reorganization
9. Documentation: REST interface (GoogleCode issue 250)

2.1.0 (Rapsodia)

Release date: Q4 2013

Issues

1. Upgrade tools (GoogleCode issue 98)
2. Command-line tool to manipulate configuration (GoogleCode issue 28)
3. 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

3.0.0 (Maggiore)

Release date: Q1 2014

Issues

1. Authentication chain (GoogleCode issue 274)
2. Pluggable authentication modules (GoogleCode issue 274)
3. PDC-based authentication (GoogleCode issue 96)
4. Passthrough authentication (GoogleCode issue 273)
5. Investigate using Apache Shiro to provide Syncope AM features
6. One-time password
7. 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.

4.0.0 (Notturno)

Release date: Q4 2014

Issues

1. 168] Allow more notification mechanisms besides e-mail
2. [SYNCOPE-169] Notification chains
3. [SYNCOPE-174] JMX support
4. [SYNCOPE-176] Android / iPhone end-user app
5. [SYNCOPE-177] Interceptors
6. Allow more notification mechanisms besides e-mail
7. Introduce notification chains
8. Role propagation / synchronization (GoogleCode issue 22)
9. Role workflow (GoogleCode issue 23)
10. JMX support (GoogleCode issue 95)
11. End-user JSR-286 portlet (GoogleCode issue 103)
12. Android / iPhone end-user app (GoogleCode issue 107)
13. Interceptors, i.e. custom extension points to catch events (user creation, provisioning to resource, ...). An idea could be to implement this with AOP. Audit implementation could be refactored as specific interceptor.