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 now reference each other 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 using a "legacy" or
33 "default" configuration.
35 Separate logs are created for errors and transaction
38 Easier logging configuration.
40 Support is included for pulling attribute data from SQL
41 databases using JDBC. The JDBC Data Connector includes
42 support for conection pooling and prepared statements.
44 Mechanism for throttling requests to the Handle Service.
45 This improves performance by preventing the server from
46 becoming saturated with signing requests. Throttle can
47 be adjusted based for servers with more than two CPUs.
49 Support for signatures on all SAML Assertions and
50 Responses, which allows for more interoperability
51 with other SAML-based software and profiles.
53 Attribute Release Policies can contain match functions
54 on attribute values. This allows the release of specific
55 values based on regular expression.
57 Support has been added to the Attribute Authority for
58 using alternate data connectors in the event of a
61 The resolvertest program can now process and enforce
62 Attribute Release Policies.
64 Updated library dependencies, including OpenSAML and XML
65 Security, with substantial performance improvements when
68 Many important bug fixes
74 New XML-based configuration system supporting runtime
75 adjustment of many settings and better integration with
76 supplemental configuration files
78 Ability to partition deployment into "Applications" at the
79 vhost, path, or document level
81 "Lazy" sessions allow applications to redirect browser
82 to initiate a session, allowing content to decide it
83 needs authentication or attributes at runtime
85 Flexible support for multi-federation deployment, including
86 selection of credentials and authorities based on the request
87 and the origin site or federation
89 Support for more types of key and certificate formats
91 Improved pluggability for many aspects of system, including
92 access control modules
94 Clearer trace logging and support for a transaction/audit log
96 Pooling and caching of HTTP and TLS connections to origins
98 Support for alternative SAML name formats for intra-enterprise
99 deployments and better interoperability with SAML products
101 Support for tailoring attribute query behavior, particularly
102 non-fatal failure modes for intelligent applications prepared
103 to deal with missing information
105 Updated library dependencies, including OpenSAML, Xerces parser,
106 XML Security, and support for all GCC 3.x compiler versions
108 Support for Apache 2.0 as well as Apache 1.3 and IIS
110 Many important bug fixes