...
- Accessing the (unsupported) InCommon WAYF
- Deploying an Unsupported Version of Shibboleth / OS / etc.
- Expired Certificates in Metadata
- SAML 2.0 Support
- IdPs with TLS-protected HTTP-Redirect SSO
- SPs that support SAML 2.0 should indicate so in metadata
- SPs with TLS-protected HTTP-POST ACS and an encryption key
- SAML 1.1 Support
- SPs with TLS-protected HTTP-POST ACS
- Support for SAML 2.0 persistent NameIDs or eduPersonTargetedID
- Perhaps support for other attributes are worth noting?
- Full saml2int conformance
- Consent-based support for particular attributes (i.e., no admin involvement needed)
- Keys of less than a certain age
- We should consider what, if any, age is actually "too old"
- Appropriate error pages
- Perhaps subjective, but I'd start with having actual contact info for users and a reasonable indication of what to do, maybe not using the Shibboleth logo?
...