The main purpose of identity management systems is to manage user and role provisioning. Provisioning operations can act on Apache Syncope only or be propagated towards external resources as well (propagation). Provisioning will occur on a certain external resource every time the operation involves users or roles assigned to that resource.
End of year is time for balance, and mailing list discussion is probably the most important metrics of an open source project, at least when such project is part of The Apache Software Foundation, whose motto is Community over code. So why don't take a look at mailing list archives? Rob Weir did it recently for Apache OpenOffice and this was of inspiration for applying the same approach to Apache Syncope, using some good old shell scripting and Wordle app. Let's take a look at the results.
The Apache Syncope team is pleased to announce the release of Syncope 1.1.5 (Ad libitum). This fifth maintenance version fixes few important bugs and introduces some interesting improvements: more details below.
Apache Syncope can manage users, groups and memberships (memberOf/members attribute) on external Active Directory via ConnId's Active Directory (JNDI) connector. Think you manage users and roles on Apache Syncope as centralized IdM, and have all these entities automatically kept in sync with your Active Directory users and groups: few simple steps onto the Apache Syncope administration console will help you to succesfully aim your goals ....
Before storing/propagating/synchronizing a specific user or role, a pre-processor can be called in order to allow any kind of manipulation before any actual operation takes place.
I've a keen interest in IAM solution also because I think that my first qualification is simply: IAM specialist. Today, googling idm open source I noticed that the first result occurrence (also in paid search results) is openiam identity manager, so, out of curiosity, I decided to install it.