Hi, It has being a while since our last release. The reason is we had some deep changes to the IDM API after some important feedback, in special from Bill Burke. We can summarize all changes as follows: - Runtime partitions support (as proposed from Bill and considering his PR); - Custom types (AttributedType, IdentityType and Partition) support; - New annotations that can be used with your custom types. Eg.: @IdentityPartition, which allows you to configure which types can be stored for a specific partition type. - Partitions are now supporting custom attributes; - More flexible and comprehensible mapping of JPA entities when using the JPA-store; - Decoupling of the built-in types (such as User, Role, Group, Grant, etc) from the API. Now they are fully optional and not required to get your use case working; - Improvements to the configuration of the JPA and LDAP stores. The main objective of this release is to give you a chance to take a look at all those changes, which is a result from the last discussions we had around the IDM API requirements and use cases. We're still working on some other important aspects, but they are not a blocking to start using this new version. The most visible change for who is already using the IDM is that all getAgent, getUser, getRole, grantRole, etc, methods were removed from the IdentityManager interface and moved to the org.picketlink.idm.model.sample.SampleModel class. We have also introduced a specific interface for relationship management, the org.picketlink.idm.RelationshipManager. Documentation is being updated, it will be published very soon. Also, the JDF quickstarts are updated to reflect this new version. Issues for this version: https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310923&v... Thanks. Pedro Igor _______________________________________________ security-dev mailing list security-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/security-dev

Hi, It has being a while since our last release. The reason is we had some deep changes to the IDM API after some important feedback, in special from Bill Burke. We can summarize all changes as follows: - Runtime partitions support (as proposed from Bill and considering his PR); - Custom types (AttributedType, IdentityType and Partition) support; - New annotations that can be used with your custom types. Eg.: @IdentityPartition, which allows you to configure which types can be stored for a specific partition type. - Partitions are now supporting custom attributes; - More flexible and comprehensible mapping of JPA entities when using the JPA-store; - Decoupling of the built-in types (such as User, Role, Group, Grant, etc) from the API. Now they are fully optional and not required to get your use case working; - Improvements to the configuration of the JPA and LDAP stores. The main objective of this release is to give you a chance to take a look at all those changes, which is a result from the last discussions we had around the IDM API requirements and use cases. We're still working on some other important aspects, but they are not a blocking to start using this new version. The most visible change for who is already using the IDM is that all getAgent, getUser, getRole, grantRole, etc, methods were removed from the IdentityManager interface and moved to the org.picketlink.idm.model.sample.SampleModel class. We have also introduced a specific interface for relationship management, the org.picketlink.idm.RelationshipManager. Documentation is being updated, it will be published very soon. Also, the JDF quickstarts are updated to reflect this new version. Issues for this version: https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310923&v... Thanks. Pedro Igor _______________________________________________ security-dev mailing list security-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/security-dev