News

News and announcements concerning the South African Identity Federation.

SAFIRE Website Update

SAFIRE’s website was originally created using Wordpress, something that was inherited when custodianship of the federation passed to TENET. For various reasons we have decided to abandon Wordpress in favour of a modern static site generator, and have chosen to adopt Hugo.

One substantial benefit of this approach is increased transparency, particularly around changes to policies. The Hugo source is stored in a public GitHub repository, thus allowing Participants to peruse the commit history of any document.

NWU joins SAFIRE

North West University (NWU) has signed the Participation Agreement and joined SAFIRE as a full participant. NWU completed technical integration some time ago, and so are able to immediately take advantage of the services provided by their federation. Their first login happened within ten minutes of updated metadata being published.

Support for eduPersonEntitlement added

In our ongoing work to integrate library journal and platform providers, it has become apparent that we need to support the eduPersonEntitlement attribute. Support for this attribute has therefore been added to the Federation hub, as well as the test identity and service providers.

To ease transition and to lower barriers to entry, the Federation hub may automatically generate a value for eduPersonEntitlement from eduPersonAffilation if none is supplied by the identity provider. Details of this are in the attribute definition. (You can avoid having eduPersonEntitlement auto-generated by supplying more accurate value(s).)

Monitoring of Identity Providers

As a courtesy, we monitor the reachability of the various South African identity providers and make that information available at monitor.safire.ac.za.

The monitoring system initiates a single sign-on request, and reports the outcome as follow:

  • Green means that we completed all the tests and found something that looked like a login page.

  • Yellow means that we got as far as what we think should be a login page, but didn’t find a username field on it. The institution’s own monitoring or I.T. help desk may be able to provide more information.

  • Red means that we weren’t able to contact the identity provider for some reason. This could be because there’s a network problem or that the there’s some problem with the identity provider (service not running, certificates expired, metadata expired, etc).

The monitoring output shows the hosts we passed through on the way to what we believe is the login page. It may also give details of any problem(s) that were encountered.