web analytics

Single Sign-On – taking it to the desktop – or not? #EDUScotICT

A core service of the Glow Learning Platform is the Single Sign On (SSO) service.  Arguably, this is the absolute core of Glow and one of the services which in concept should always be preserved irrespective of the other services which constitute the complete platform.  When Glow was originally conceived this was taken by some to mean that once a pupil or teacher signed into the network, that they would not need to offer any further authorization credentials.  Sadly, it was not possible to achieve this level of SSO because every local authority at the time operated its own network access control system.   So the current position is that any school-based user must pass through two authentication gates before they can access the Glow Service.  This requires that every user needs to maintain two user names (UID) and password (PWD) combinations.

Time has passed and I wonder if the value of a true single sign -on solution is now generally appreciated where users can achieve access to all the resources both at a local and national level without the need to authenticate twice.  Seems to me that this could be set down as a requirement and revisited in the context of the next iteration of Glow.

I don’t intend to offer a technical solution here but I am prepared to raise a few issues need to be considered whilst working towards a true SSO solution for Glow users.

Who owns the User Identity?
As previously stated each user in the current setup will have at least two UIDs to access the school network and Glow.  Glow through its membership of the UK Access Management Federation (UKMAF) also extends SSO to a number of federated content providers including SCRAN and Scholar.

The users local network UID and PWD provide access to both the Local Area Network and the services which are associated with it.  These services could include file storage, printer services and applications which are stored locally.  Where the LA provides onward access to the internet this will be another service which is accessible through the network login.  As discussed in my previous article access to the internet may well be filtered according to the school or LA policy.

Once connected to the internet the user can then access any service which the filter permits – which will include Glow – this is based on a second UID and PWD of course.

The two UID/PWD combinations will in the worst case be completely separate.  In some cases a LA may have decided to follow advice given early in the Glow project to use the same UID for Glow as for the local network.  Further more users could manually synchronize both passwords making it easier for end users to gain access although they will still have to pass thought the UID/PWD gate for both the local network and Glow.

In the above scenario there are two identities and two identity owners which are the school (LA) and Glow.  As already stated, Glow is the identity owner for Federated access to third party content which prevents users needing to remember other UID/PWD combinations for third party federated services.

Could this be further simplified?
In short the answer is yes, and this can be achieved in a number of different ways.

One approach is to make even more use of the UKAMF by making Glow a Federated service and having each Local Authority become an Identity Provider (IdP) in the context of the Federation.  This would ultimately put some additional responsibility on the LA as they would need to maintain their Authorization service on a 24/7 basis and setup and maintain the Shibboleth IdP service.

Each time a user tries to access a UKAMF federated service, be it Glow, SCRAN or any other, the process of authentication will involve some interaction with the users home local authorities IdP service.  This of course applies when the user is either accessing via the school network or from some other location.

Because of that way that the Shibboleth system operates there is one further stage needed when the user is away from home – ie accessing from a location out with their LA network.

The Where Are You From service (WAYF)

The WAYF service is needed when a user is accessing a federated service when they are not connected to their LA network.  For this illustration we consider the LA network to be the primary network for our users and this is where the user UID/PWD are maintained.  Consequently, a user trying to access a federated service from their domestic/home network or from any other network, roaming public WiFi access points etc, will need to use the WAYF service to ascertain the organization which maintains their IdP service.

In reality this will be fairly straightforward as the user will be given a choice from the list of LAs participating in the scheme.

Users with a National ID?

The effect of this approach is that the school user could through the use of on UID/PWD combination have access to the School internal resources and also have access to third part resources which are federated using the UKAMF.

What if Glow was the IdP for local authority network access?

In this scenario all LAs would have to agree to using the national authentication service for permitting access to the local network.  Once a user has authenticated to Glow the user will be permitted access to the local network.  In this case each user connecting to the LA network would be presented with a prompt for UID/PWD which would be their Glow credentials.

So what are the issues?

As I stated at the start of this post it is not my intention to offer a solution to country wide SSO.

  • Trust is always an issue when dealing with controlling access to resources.
  • An organisation will generally trust its own authentication system – but may be reluctant to trust a third party system.
  • If LA is IdP – this is responsibility to provide 24/7 service which might not be desirable or possible – are LAs setup to provide 24/7 supported services?.
  • Having true SSO to the desktop is definitely desirable (my view!)
  • Is there a case for making a admission control to the network or applications a shared service so same approach it taken throughout UK
  • What are the educational benefits of making access easier for all users – certainly will take one barrier away – what value do we put on easier access?.
  • Once established – why not use the authorization service for other proposes/applications – no suggestions here but many mush exist!
  • What are the implications for FE and HE if they were also to make use of the Glow service package?

 

 

 

Wireless Roaming for Scottish Education users.

Note: this post concerns the provision of a facility that will allow users to benefit from wireless access whilst attending council or school sites – I intend to discuss internet filtering in a subsequent post.

I want to start this post by quoting Charlielove.org as follows

“And the most useful input of the whole day? From the pupils and they said what I (and many others) have been saying for a long time: allow open and free access to Wi-Fi for all devices, allow them to connect and allow learners the same freedom in school as they have at home, in McDonalds, in Cafe Nero etc. etc.”

He goes on to say

“Why are local authorities terrified of this? It isn’t rocket science to configure a Wi-Fi network so that the corporate infrastructure is hidden from the person just connecting to access the web.  Maybe it’s because we need investment in the links between schools and the national Interconnect because LAs are concerned that the network can’t cope with the traffic levels?”

http://charlielove.org/?p=6580 click here for the full quote in context.

The following comments are set against my own experience of trying to establish a system for this in Scotland starting with LTScotland – sadly, I failed at the first hurdle.

The need for pervasive WiFi access seems to be a recurring issue for users in today’s IT landscape were wireless connectivity is very often free at the point of use (yes indeed many hotels do make charges still).  As a frequent international traveler I know that I now instinctively look for a wireless connection for my laptop at every stop.  Most places I visit have such a facilit although it is not always free!  I also have an iPASS account which allows me to access paid WiFi services with all costs being passed to my centralized the iPass account.

The purpose of this post is to present some thinking about how wireless access can be made a reality for school users in Scotland.  I have seen the need for Wireless connectivity raised a few times during the course of the Glow Future debate.  This is nothing new, for many years there has been discussion around the need to support the connection of personal devices to school (or institutional networks in general).  By devices here I include smart phones, pads, net books and of course laptops.  Portable computing devices are now owned by an increasing proportion of users it seems to me that the time is right to include access to the learning platform from mobile devices on an any time any where basis to be a basic requirement.  I consider schools to be in scope in the context of my previous statement.

This same issue that was considered when Glow was first conceived but that general view at the time was that mobile devices were still in the minority and first priority should be given to supporting institutional owned equipment and personal devices connecting from the home. Hence the primary emphasis on support for desktop and laptop computers etc.

Why should School WLANs not be opened up to personal mobile devices?

Its all about trust in my view.  If we allow access then we have a situation where any user (with no connection with teaching and learning) can connect – this would include any person within range of the school wifi network.  I trust that I do not need to develop that line of thinking further at this point – I think that the implications are quite clear.

It’s really the use (and optionally the users devices) that need to be validated.  So my starting point here is that any authorized user should be able to connect-provided that the user as been pre-authorized the network owner (school or local authority).  We should also add to this primary set of user the concept of trusted visitors – ie users who have been authorized by other trusted schools.

If such a system was in place we increase access for all school users and it would be possible to extend the range of available hot spots to include other public places including libraries, hospitals and FE and HE institutions.  So what is proposed here is to put in place a WiFi roaming arrangement that provides pupils and school staff with the ability to connect wirelessly using either school owned devices or their own devices.

Where a user wants to use his/her own device it would optionally be possible to expect that the device meets certain basic standards in relation to virus protection etc. – this would need to be confirmed before the device would be allowed to connect to the network.

Any user who is known and trusted by any co-operating group of schools ( other organizations ) should be able to connect to the wireless network at any of the schools and other premises by authenticating using their user ID and password.  Such a system can formally be described as federated access control allow that would grant any authorized and trusted user access anywhere throughout all the federated locations.

The level of service being offered could be restricted based on the credentials of the user and their role.

None of what I have described above is new in concept but currently I am not aware that any such facility exists in any Scottish Schools.

How can this be achieved practically?

One approach is to setup a new wireless roaming federation for this purpose.  It would be necessary to have all schools (perhaps via their Scottish Local Authorities) to join this federation.  This will involve a great deal of effort.

An alternative route would be to join an existing federation.  For this purpose I would propose that there is a ready made solution called EduRoam (see link at and of post).  In an ideal world, every Scottish school would join EduRoam and this would have the effect of allowing authenticated access any schools wireless network with the option of granting full or partial access to the network and related service.  Of course the decision about how much access users are given will rest with the school ( or Local authorities)  I would however suggest that if there are basically two levels of access which are full and internet only that would suffice for all users types.

What would this look like in practice?

Imagine a situation where a pupil arrives at school, opens up his/her personal laptop the following demonstrates how this might work.
1               Pupils open laptop
2               Attempt to join wireless network
3               User challenged for UID and PWD
4               User it authenticated against his home authentication system
(which could be a school, LA or national system)
5               User is granted access to the network with appropriate rights.

Where the user is a visitor, the user will effectively given what is equivalent to a standard route to the internet, no more no less.  This route my well be restricted and internet safety filter to ensure that the connection cannot be abused etc.

Could this be done today?

Clearly there is a need to enter into an agreement with EduRoam to use such a service.  This could be done in a number of ways including at the national, regional (LA) and school level.  Practically, it would be ideal if this was done at national level.

School wireless network would need to be quality assured and the accompanying network admission system checked to ensure that it can support a federated authentication approach.

EduRoam uses a RADIUS based system to facilitate user authentication and network admission which sends authentication requests back to a users home authority (which could be Glow in the context of the scenario outlined here)  The EduRoam site provides an excellent description of how this works – note that the video on the front page is HE centric.  I suppose we need to use imagination to see how this might work in a Scottish schools environment.

www.eduroam.org

 

#EduScotICT – recurring themes

I was involved in the early stages of Glow and still have a detailed understanding of the technical architecture of Glow and how it came be as it is.  I sat through yesterday’s (17th October 2011) webcast about its future and was interested to hear the presentations whilst also monitoring the #EduScotICT twitter stream.  I was less than satisfied with the experience as it was impossible to gauge any sense of the mood of the event – I think that would have been driven through the discussions off camera – but viewers were only able to see a static screen with no audio at these important times.  However, I was interested to hear what I was able to!  For me the web cast worked perfectly from start to finish although I know other people had issues from time.  Well done to those who made the technical arrangements to achieve the live feed.

I note that through this event and also on the EduScotICT wiki there have been some recurring themes.  I have listened to the discussion over the weeks and I now feel moved to comment on some of the recurring themes which I plan to do here through a series of posts.

I do find it surprising that a decision was taken, rather late in the day, to cancel the Glow Futures procurement process.  In my opinion this seems to be a very risky move at a key time in the evolution of Glow and more generally the progress of the use of ICT in Scottish classrooms.  I believe Scotland needs to move Glow forward in an evolutionary way to return maximum benefit.  I certainly feel that there are some aspects of Glow which need to be improved and I do feel that the procurement if well managed and driven by a clear set of objectives was and is the best way to achieve this result.

Glow when initially conceived was a very brave initiative and built upon 10+ years of progress/experience in the use of ICT in Scottish classrooms.  This also coincided with the advent of Web2.0 which at the time was in its infancy.  At the time I think that the process of consultation, which took about 2 years and involved representation from all parts of Scotland and its education system, was comprehensive and detailed.  The product was a statement of requirements, drawn up as a result of a truly collaborative and lengthy discussion involving workshops, seminars and technical meetings, which was used to drive an EU negotiated procurement process. This resulted in Glow as we know it today – allowing for the fact that some new features were brought in later in the project’s history.  Because of the rigours of the original procurement process it was not possible mandate any specific application, the specification had to be “output based”.  MS Share Point provided the core portal which each of the final three bidders judged to be appropriate at the time bearing in mind the technology landscape at the time.  I take the view that this is now history and there is little point in criticising decisions made then in the light of today’s perceived wisdom.

There were some surprises in store – one that comes to mind was the purchase of Marratech ( the original desktop collaboration tool – Glow Meet ) by Google.  Google wanted it for its own internal use.  That had a devastating effect on the availability of support for the product meaning that no code updates where available from that point forward, so no maintenance updates or bug fixes.  I was always disappointed that a large company like Google could impose this position on what did turn out to be a corner stone feature of Glow.  Perhaps we need to keep this in mind when we consider putting our trust on Google ( Google Apps seems to be very much discussed in relation to Glow Futures) for the future.  Thankfully it was possible to replace Marratech with another tool after a couple of years service.

I do feel that we need to take stock of what worked and learn lessons in light of what could be described as the successes and failures resulting from Glow to date.  I am very aware of the fact that Scotland achieved something back then which was unprecedented.  I know that some people took a negative stand on Glow from day one – but I am also now very aware that many teachers in Scotland have embraced the platform (warts and all) with a positive and persistent attitude and as a result have improved learning opportunities for their pupils.

My wish is that in moving to the next stage Scotland does not “throw out the baby with the bathwater” and takes an evolutionary approach to moving forward and builds on the good whilst pruning the weak.  Let us also be very careful to protect the massive investment made by teachers who have adopted Glow, in terms of time spent in training and development and on adapting their teaching practice to gain maximum benefit from the platform.  Many of these people will have had to over come significant hurdles in terms of their native classroom practice to reach their current position and to integrate ICT into their daily work – this cannot be assumed to be as natural and painless transition as some would have us believe.  It would be wrong to “pull the platform from under their feet” without a clear plan for progress in to the next stage and also provision of the necessary support needed to help them transition.

Just for the record I do not take the view that it is necessary to completely abandon the Glow platform as we know it to address its weaknesses.  I strongly believe that some elements of Glow worked very well and should be retained/replaced whilst others were less successful – lets move forward with a constructive approach which feeds strengths and prunes the weak components.

Let’s take stock and remember what the apostle Paul said in 1 Thessalonians 5:21

“Prove all things and hold fast to that which is good”