Changes to the Requirements for SAML2 Identity Providers that are purely technical in nature must reach rough consenus/no opposition at the SAFIRE Participants’ Forum. Changes to the administrative requirements are synchronised with the Metadata Registration Practice Statement. This version reached rough consensus on ….
The following describes the technical and administrative checks that will be made before an identity provider is admitted into the SAFIRE federation within the SAML2 Technology Profile.…
Changes to the SAFIRE Steering Committee’s Terms of Reference are approved by TENET’s Board of Directors on recommendation from the SAFIRE Steering Committee. This version was ratified on 26 September 2017.
Download Open at Google
Changes to the Attribute Release Policy are approved by the SAFIRE Steering Committee. This version reached rough consensus on 11 August 2017 and still needs to be ratified. As a revision to the previous version, it allows affiliation attributes to be released in the default ARP.
Management of attribute release to Service Providers has been delegated to the Federation Operator in terms of the Participation Agreement.
Attribute Release Profiles Through a community consensus process, the following attribute release profiles have been approved:…
This revision does not substantively change the ARP, but introduces a section that clarifies its interpretation with respect to inter-federation.
Management of attribute release to Service Providers has been delegated to the Federation Operator in terms of the Participation Agreement.
Attribute Release Profiles Through a community consensus process, the following attribute release profiles have been approved:
Default The Default release profile used when no other attribute release policy is defined:…
Changes to the Metadata Aggregation Practice Statement are announced to the SAFIRE Participants’ Forum.
SAFIRE generates a number of metadata aggregates for various purposes, including inter-federation and its own internal operations. This document gives a broad overview of how the aggregation process works. It is currently non-normative and will be refined over time.
Metadata aggregator SAFIRE makes use of WAYF’s PHPH (PHederation PHeeder) metadata aggregation software. An overview of the configuration of this aggregator and the aggregates it generates is publically available at https://phph.…
SAFIRE generates a number of metadata aggregates for various purposes, including inter-federation and its own internal operations. This document gives a broad overview of how the aggregation process works. It is currently non-normative and will be refined over time.
Metadata aggregator SAFIRE makes use of WAYF’s PHPH (PHederation PHeeder) metadata aggregation software. An overview of the configuration of this aggregator and the aggregates it generates is publically available at https://phph.safire.ac.za/.…
Changes to the Metadata Registration Practice Statement that are purely technical in nature must reach rough consenus/no opposition at the SAFIRE Participants’ Forum. All other changes are approved by the SAFIRE Steering Committee. This version reached rough consensus on 16 September 2016 and was ratified by the Steering Committee on …. There has been a subsequent minor revision to add acknowledgements.
Definitions and terminology The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 21191.…
The following describes the technical and administrative checks that will be made before an identity provider is admitted into the SAFIRE federation within the SAML2 Technology Profile. It also serves as a checklist for identity provider operators for assessing their readiness to participate.
Metadata MUST1 have an entityID that is a URL (well-known location). The URL SHOULD use the https scheme and it is RECOMMENDED that valid metadata be available at this URL.…
Changes to the Privacy Statement are approved by the SAFIRE Steering Committee. This version reached rough consensus on 21 December 2016 and still needs to be ratified. As a revision to version v20160622, it includes a new section about website analytics.
Introduction This document explains what personal information is collected by the South African Identity Federation (SAFIRE) and how it is used.
This document SHALL1 be published on the Federation website at https://safire.…
Changes to the Key Management Practice Statement must reach rough consenus/no opposition at the SAFIRE Participants’ Forum. This version reached rough consensus on ….
Definitions and terminology The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 21191.
Federation, Identity Federation: An association of organisations that come together to securely exchange information as appropriate about their users and resources to enable collaborations and transactions.…