This page/section needs content clean up and new materials: it's time for community to review this content for currency and accuracy.
The InCommon Federation is by-community, for-community endeavor aimed to streamline cross-organization research and scholarly collaboration. The following recommended practices help all federation participants improve interoperability and streamline implementation and operations while working with federated partners.
Maintaining complete and accurate information in InCommon metadata is important so systems from other federation participants can best engage with your site's services.
See X.509 Certificates in Metadata, particularly:
The certificates registered by a participant contain at least 2048-bit RSA public keys, are self-signed, are not expired, and do not carry revocation-related extensions.
See Endpoints in Metadata, particularly:
See IdP Endpoints, particularly:
See SP Endpoints, particularly:
A site supplies values for each of the user interface elements to maximize the user experience.
SPs that seek a wide audience of IdPs without explicit contracts or arrangements ahead of time specify the attributes they need in order to facilitate consent-driven user interfaces.
See Maintaining Supported Software, particularly:
See Protect Against Failed Metadata Processes, particularly:
Allocate at least 1500MB of heap space in the JVM
Enable DEBUG-level logging on selected Java classes
See Federated User Experience with particular attention to the following.
See Attribute Release Process, particularly:
See Persistent Identifier Support, particularly:
Can't find what you are looking for?