I'm pleased to announce the release of PicketLink 2.5.0.Beta3. This release is actually the successor to 3.0.0.Beta2 - we've changed the version number to help avoid confusion going forward, if you want the nitty gritty details about this decision then you can find out more below.
In case you don't know what it is, PicketLink is a security framework for Java EE applications. If you are already familiar with Seam Security, then you might consider PicketLink to be its spiritual successor. For more info about its features check out this overview.
As always, here's the direct links to the various resources for this release:
For those of you that use Maven, we've made a slight change to the artifact ids - from now on a typical application will only need to declare the following dependencies:
<dependency> <groupId>org.picketlink</groupId> <artifactId>picketlink-api</artifactId> <version>2.5.0.Beta3</version> </dependency> <dependency> <groupId>org.picketlink</groupId> <artifactId>picketlink-impl</artifactId> <version>2.5.0.Beta3</version> <scope>runtime</scope> </dependency> <!-- Optional database schema when using Identity Management with JPA based Identity Store --> <dependency> <groupId>org.picketlink</groupId> <artifactId>picketlink-idm-schema</artifactId> <version>2.5.0.Beta3</version> <scope>runtime</scope> </dependency>
For this release, the reference documentation has received some special attention and so should be significantly more informative than previous betas. With that being said, the team is constantly improving the docs and will continue to add more content right up to the final release. There are also numerous quickstarts planned to help you get up and running quickly with the many security features provided by PicketLink - I'll be posting some more info about some of these shortly so keep an eye on this space.
There have also been a substantial number of bug fixes, new features and improvements made since the last beta release, the details of which you'll find in the release notes below.
As always, the PicketLink team is available to chat with at various times of the day on the #picketlink IRC channel at freenode.net; also feel free to drop them a line at the PicketLink Forums if you need help using PicketLink in your own application.
If you've been following any PicketLink-related news lately, you'll know that the PicketLink team has been working hard towards releasing PicketLink 3 in the very near future. It has recently come to the team's attention though that there is some confusion surrounding the versioning of PicketLink, which is due to a couple of reasons; firstly, there is an existing committment to support PicketLink Federation 2.1 in EAP (the supported version of JBoss Application Server, recently renamed to WildFly). Secondly, there was never an actual 2.x release of PicketLink IDM (it was only ever officially released as version 1.x). Because of this, and since the PicketLink Federation that was planned to be released as 3.0 is actually backwards compatible with 2.1, the team has decided to rename the 3.0 release to 2.5. So what does this mean exactly? Well, besides the change in version number, not much at all really - PicketLink 2.5 will still include all of the next generation security features that the PicketLink team have been working on over the past months. We apologise for any inconvenience that this change might have caused, however the team felt it was best to resolve this confusion now, before the final release.
- PLINK-116 - Change scope for JBoss Logging dependency in picketlink-common module to provided
- PLINK-119 - DefaultIdentity is considering the User.id when comparing with the DefaultLoginCredentials.userId
- PLINK-131 - Signed logout request does not contain the "Destination" attribute
- PLINK-132 - PicketLink based SP's need to support different login and logout URLs
- PLINK-136 - The IDM subsystem is always initialized even when a custom Authenticator is provided
- PLINK-137 - Change the scope for CDI dependencies in picketlink-api and picketlink-impl to provided
- PLINK-126 - Introduce individual annotations for JPA schema entities and properties
- PLINK-135 - Add type parameters to CredentialHandler
- PLINK-113 - Users should be able to use a IdentityManager for any of the configured realms.
- PLINK-117 - The API documentation should aggregate the javadocs for the modules
- PLINK-118 - Update documentation with the File and LDAP stores configuration
- PLINK-120 - Login logic is not considering when the user is disabled/locked
- PLINK-121 - Throw a specific exception when the user tries to authenticate twice using the same credentials
- PLINK-124 - Add credential storage retrieval methods to IdentityManager
- PLINK-127 - CredentialHandler implementations should check if the Agent is disabled
- PLINK-128 - Refactor the Configuration API to provide a Fluent API using the build pattern
- PLINK-142 - Provide more examples about how to mix identity stores
- PLINK-92 - Container Bindings Project
- PLINK-122 - Provide test cases for the base module
- PLINK-125 - Umbrella task for 2.5.0.Beta3 documentation issues
- PLINK-129 - Import the container bindings modules from PicketLink v2
- PLINK-133 - Use getAgent() instead of getUser() throughout authentication API
- PLINK-138 - Change project version from 3.0.0 to 2.5.0