Not Yet Released, Expected Feb 2015
For a complete list of issues addressed in this release, see https://issues.shibboleth.net/jira/issues/?filter=10673.
This is a bug fix release. Addressing IDP-573 which corrected a serious bug in the attribute resolver required the addition of new public APIs, necessitating a minor version change, but this is not a significant feature upgrade. A few new properties and Spring beans have been added, and these are denoted in the documentation with the superscript 3.1 to distinguish them. Anything so denoted will be ignored or fail if used with an earlier version. (This convention will be used going forward to denote anything introduced with new releases.)
New properties were added for configuring alternative storage services for the replay cache and artifact map for clustered deployments.
Per IDP-580, a syntax introduced in V3.0 to declare
<security:TrustEngine> elements inside
<metadata:MetadataProvider> elements has been deprecated in favor of declaring the trust engine element directly within a
metadata:SignatureValidation MetadataFilter, which is the only current filter implementation that supports such an object. The deprecated syntax will likely be removed promptly due to its limited usefulness and very recent introduction.
A bug (IDP-585) was fixed that prevented the use of caching in the attribute resolver. In conjunction with this fix, the deprecated
cacheResults LDAP/RDBMS data connector attribute is no longer honored (and a warning omitted). The
<dc:ResultCacheBean> elements are now the only supported mechanism for configuring caching.
Dec 22, 2014
This is the first release of the third-generation Identity Provider software. The key documentation links are located on the IDP30 space Home page, such as SystemRequirements, Installation, and UpgradingFromV2 material.
This release should interoperate with all previous releases of Shibboleth and other software that supports the same standards. As a major upgrade, the list of issues fixed and features added is numerous and you should refer to the documentation itself for information on what's changed or new.