| Table of Contents | ||
|---|---|---|
|
Information about Project Access
All public Shibboleth project services (website, download site, wiki, svn, git, issue tracking, and maven repository at the time of this writing) may be accessed anonymously in a read-only capacity.
Contributions and Write Access
We have configured the new Confluence and Jira sites to allow anyone using an email address from a non-public domain to obtain access via Atlassian's standard workflow (if you’re logged into their platform, you should be able to request automatic user-level access). Access to the site includes the ability to comment or add/edit pages, create issues, etc., though we reserve the right to limit this if we encounter spam problems. Any contributor posting to the wiki or creating an issue agrees to license their provided content under the same license noted above.
If you would like to contribute to the documentation or file an issue via an account using a public email domain (or you just don’t see the request option for whatever reason), you can contact us for now to get access, but we may do additional follow up to ensure the request is legitimate.
As we go forward we will adjust based on demand and the capabilities of the product, which are more limited and not geared toward the way we did things in the past.
| Note |
|---|
The services are now cloud-hosted and, due to the limitations of Atlassian's SAML support, no longer relies on federated access generally. As such, we no longer control the information collected, nor how it may be used. Refer to Atlassian's policies for information on these matters. Anyone with attributed content that wishes to be removed from the list of known past users is welcome to contact us. |
Wiki Service Information
The wiki (https://shibboleth.atlassian.net/wiki) provides the currently available documentation for all the Shibboleth projects as well as information about the project plans and management.
All information within the Wiki is licensed under the Creative Commons AttributeAttribution-ShareAlike 34.0 Unported International (CC BY-SA 34.0) license.
Per the terms of the CC BY-SA 34.0 license, the content of this wiki may be used by others, without seeking permission of the author, as long as this wiki is attributed as the source of the material and any resulting work is licensed under the CC BY-SA 34.0 license or a similar license. Attribution are is best performed by providing a URL to the wiki page(s) containing the source material.
| Note |
|---|
The wiki is now cloud-hosted and, due to the limitations of Atlassian's SAML support, no longer relies on federated access generally. As such, we no longer control the information collected, nor how it may be used. Refer to Atlassian's policies for information on these matters. Anyone with attributed content that wishes to be removed from the list of known past users is welcome to contact us. |
Contributions and Edit Access
We have configured the site to allow anyone using an email address from a non-public domain to request access via Atlassian's standard workflow. Any routine request for access will generally be approved, and access to the site includes the ability to comment or add/edit pages. Any contributor posting to the wiki agrees to license their provided content under the same license noted above.
If you would like to contribute to the documentation via an account using a public email domain, you can contact us for now to get access, but we may do additional follow up to ensure the request is legitimate.
As we go forward we will adjust based on demand and the capabilities of the product, which are more limited and not geared toward the way we did things in the pastWe also have a WikiStyleGuide available to aid in maintaining consistency.
Issue Tracking Service Information
The issue tracking service (https://issues.shibboleth.net) provides a place to view and track bugs, tasks, and feature/improvement requests for the Shibboleth software. We are in the midst of a transition from the old hosted instance (https://issues.shibboleth.net) to the cloud instance (https://shibboleth.atlassian.net/jira) but at this time all software projects, old and new, have been migrated to the cloud instance and are read-only on the old system.
All issue descriptions and comments within the issue tracking service are licensed under the Creative Commons AttributeAttribution-ShareAlike 34.0 Unported International (CC BY-SA 34.0) license.
All code/patches submitted to the issue tracking service are must be licensed under the Apache License, version 2 and or otherwise contributed to the Shibboleth project Project per the terms set out in the Internet2 Intellectual Property Framework.
The system is still (temporarily, pending the move to the cloud) SAML-enabled and users wishing to post, comment on, or be informed of changes to data will need to log in via an acceptable IdP. The IdP must release:
- a required unique identifier for the user (see below)
displayNameif the user wishes to have a human-readable name suitable for display or searchmailif the user wishes to receive notifications (e.g., changes in issue status or updates to wiki pages) via email
Note that users may modify their profile name or email address, but it will be reset to an IdP-supplied value each time they login.
The preferred identifiers supported include the legacy eduPersonPrincipalName attribute and the newly-proposed SAML subject-id attribute. The latter is ideal if a name and email address are included, while EPPN is best if provided by itself because of the strong need to publically identify contributors in these collaborative tools.
If use of a public identifier is a problem due to privacy restrictions, we tolerate use of the newly-proposed SAML pairwise-id attribute, but we do not encourage it. For historical reasons, we do support the legacy pairwise identifiers that fall under the eduPersonTargetedID and SAML persistent NameID headings, but they are strongly discouraged.
The precise set of SAML 1.1 attributes supported is:
urn:mace:dir:attribute-def:eduPersonPrincipalName(preferred)urn:oasis:names:tc:SAML:attribute:subject-id(SAML Subject ID, new proposed standard, preferred)urn:oasis:names:tc:SAML:attribute:pairwise-id(SAML Pairwise ID, new proposed standard, discouraged)urn:oid:1.3.6.1.4.1.5923.1.1.1.10(targetedID as SAML attribute, strongly discouraged)urn:mace:dir:attribute-def:displayName(preferred)urn:mace:dir:attribute-def:cnurn:mace:dir:attribute-def:mail
For SAML 2.0:
...
by the project’s Contribution Policy.
Member Support Desk
Member support has also been migrated to the Jira Cloud tenant and http://support.shibboleth.net is the best method to use to access that platform, as it will redirect to a dashboard that provides direct access to a Jira project set up for each member to raise requests. Access to the support feature is limited to Atlassian accounts identified by one or more access managers identified within each member organization to identify the people with access.