Page History

...

Features

Security

...

1.1.0 (Ad libitum)

Release date: Q3 2012

Issues

...

1. Realm-based authorization (GoogleCode issue 272, Mail thread 1, Mail thread 2)
2. PDC-based authentication (GoogleCode issue 96)
3. Passthrough authentication (GoogleCode issue 273)
5. Avoid duplication in console's authorization management
6. Policy-compliant random password generation
7. Password change on an external resource only
8. Remove MD5 as a supported password cipher algorithm (SYNCOPE-51)
9. Manage creator, lastmodifier and approvers information about each SyncopeUser bean (SYNCOPE-15)
10. Documentation: Derived and Virtual attribute use cases
11. Documentation: Sequence tables documentation and their initialization for import
12. Documentation: Workflow - concepts, how to customize and how to trace

1.2.0 (Intermezzo)

Release date: Q4 2012

Issues

1. Delegation (GoogleCode issue 102)
2. 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
3. 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.
4. Assign membership and role schemas to either all memberships / roles or only some memberships / roles
5. Don't expose some REST list methods for anonymous (currently needed for self-registration)
6. Add UserRequestController.execute() that will execute the provided UserRequest and remove it on success
7. Allow user, role and membership properties (like as id and name, for example) to be used in derived schema definition
8. Password reset
9. Password required for resource subscription (GoogleCode issue 264, Mail thread)
10. Remove MD5 as a supported password cipher algorithm (SYNCOPE-51)

...

1.3.0 (Jazz)

Release date: Q1 2013

Issues

1. Support more than one local connector bundles directory and zero or more ConnId's connector servers (GoogleCode issue 168)
2. Scripted SQL connector bundle (GoogleCode issue 277)
3. Investigate support for OpenICF connector bundles
4. Dynamic role memberships (GoogleCode issue 219)
5. Add the option 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.
6. 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.
7. Add support to execute propagations asynchronously (request handle, local update and return, resource provisioning performed in background - giving the possibility to manage background activities, provisioning result notification).
8. Support more than one local connector bundles directory and zero or more ConnId's connector servers (GoogleCode issue 168)
9. Scripted SQL connector bundle (GoogleCode issue 277)
10. Investigate support for OpenICF connector bundles

...

1. Allow more notification mechanisms besides e-mail
2. Introduce notification chains

Roles

1. Role/membership attributes synchronization (SYNCOPE-26)

1.4.0 (Preludio)

Release date: Q2 2013

Issues

1. Add ability to search for Roles via the REST API (SYNCOPE-44)
2. Dynamic role memberships GUI installer (GoogleCode issue 219)
3. Role propagation / synchronization (GoogleCode issue 22)
4. Role workflow (GoogleCode issue 23)
5. Assign membership and role schemas to either all memberships / roles or only some memberships / roles

REST

1. 99)
2. Provide Task entities a name and an optional description
3. Make configurable whether UserRequest objects (create / update / delete) need to be approved or not and under which conditions (including membership of certain role(s))
4. Documentation: Self-registration
5. Refresh button in console task modal windows (GoogleCode issue 248)
6. Cancel button for console modal windows

2.0.0 (Virtuoso)

Release date: Q3 2013

Issues

1. Don't expose some REST list methods for anonymous (currently needed for self-registration)
2. Easier and cleaner way to override REST methods (for WAR overlays)
3. Rich client library, hiding REST call details (GoogleCode issue 104)
4. Enlist RESTful methods (GoogleCode issue 250)
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)
10. Add UserRequestController.execute() that will execute the provided UserRequest and remove it on success

...

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.

Management

4.0.0 (Notturno)

Release date: Q4 2014

Issues

1. Allow more notification mechanisms besides e-mail
2. Introduce notification chains
3. Role propagation / synchronization (GoogleCode issue 22)
4. Role workflow (GoogleCode issue 23)
5. JMX support (GoogleCode issue 95
6. JMX support (GoogleCode issue 95)
7. Upgrade tools (GoogleCode issue 98)
8. Command-line tool to manipulate configuration (GoogleCode issue 28)
9. GUI installer (GoogleCode issue 99)
10. End-user JSR-286 portlet (GoogleCode issue 103)
11. Android / iPhone end-user app (GoogleCode issue 107)
12. Use logback-audit for auditing

General improvements

1. Manage creator, lastmodifier and approvers information about each SyncopeUser bean (SYNCOPE-15)
2. Virtual attribute cache (GoogleCode issue 276)
3. Better way to override console components (for WAR overlays)
4. Avoid duplication in console's authorization management
5. Refresh button in console task modal windows (GoogleCode issue 248)
6. Cancel button for console modal windows
7. General console code reorganization
8. Provide Task entities a name and an optional description
9. Allow user, role and membership properties (like as id and name, for example) to be used in derived schema definition
10. 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
11. Make configurable whether UserRequest objects (create / update / delete) need to be approved or not and under which conditions (including membership of certain role(s))

Improve documentation

1. Self-registration
2. REST interface (GoogleCode issue 250)
3. Derived and Virtual attribute use cases
4. Sequence tables documentation and their initialization for import
5. Workflow: concepts, how to customize and how to trace

Versions

...