Mar 10, 2015
For a complete list of issues addressed in this release, see https://issues.shibboleth.net/jira/issues/?filter=10673
The following new properties have been added in this release (defaults in parentheses):
- idp.consent.storageRecordLifetime (P1Y)
- idp.replayCache.StorageService (shibboleth.StorageService)
- idp.artifact.StorageService (shibboleth.StorageService)
- idp.attribute.resolver.LDAP.searchFilter ("(uid=$requestContext.principalName)")
- idp.service.attribute.resolver.maskFailures (true)
- idp.service.attribute.filter.maskFailures (true)
- idp.httpclient.useTrustEngineTLSSocketFactory (false)
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 store 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 plugin 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.
Several bugs (IDP-588) were fixed to support using server-side storage such as MySQL or other databases for storage of consent decisions.
Per IDP-560, the default/example view templates include a few improvements, so you may wish to review those changes if you have a previous install, as the original files will not be overwritten.
220.127.116.11 (Windows Only)
Feb 25, 2015
This is a service release of the 3.0.0 Windows Installer that updates Jetty to 9.2.9.v20150224 to address a Jetty security issue. If you did not install Jetty via the Shibboleth installer, then this update is not required (but of course you may still be affected by the issue if you have an affected Jetty version in use).
As noted on the WindowsInstallation page, service releases (represented by the fourth version number) do not indicate an actual update to the Shibboleth software, only to third party components we support.
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.