4 This release represents a fully compatible minor update
5 to the Shibboleth 1.0 release, and is considered to be
6 ready for production use.
13 Multi-federation support. Most origin configuration,
14 including signing credentials and identifiers, can be
15 overriden depending on the recipient of the assertions.
17 Simplified application architecture. Both origins
18 and targets are now referred to using a single
19 identifier called a "provider id".
21 The Attribute Authority can be configured to answer
22 requests with multiple SAML Subject formats,
23 increasing interoperability with other SAML-based
26 Signing credentials can now be loaded from a variety
27 of formats, including those commonly used with OpenSSL.
29 The origin now validates all requests from 1.2+ targets
30 against federation metadata.
32 Compatibility with 1.1 targets.
34 Separate logs are created for errors and transaction
37 Easier logging configuration.
39 Support is included for pulling attribute data from SQL
40 databases using JDBC. The JDBC Data Connector includes
41 support for conection pooling and prepared statements.
43 Mechanism for throttling requests to the Handle Service.
44 This improves performance by preventing the server from
45 becoming saturated with signing requests.
47 Support for signatures on all SAML Assertions and
48 Responses, which allows for more interoperability
49 with other SAML-based software.
51 Attribute Release Policies can contain match functions
52 on attribute values. This allows the release of specific
53 values based on regular expression.
55 Support has been added to the Attribute Authority for
56 using alternate data connectors in the event of a
59 The resolvertest program can now process and enforce
60 Attribute Release Policies.
62 Updated library dependencies, including OpenSAML and XML
65 Many important bug fixes