JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for JISC-SHIBBOLETH Archives


JISC-SHIBBOLETH Archives

JISC-SHIBBOLETH Archives


JISC-SHIBBOLETH@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

JISC-SHIBBOLETH Home

JISC-SHIBBOLETH Home

JISC-SHIBBOLETH  May 2008

JISC-SHIBBOLETH May 2008

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: LA (Re: Progress towards the federated goal. Or otherwise.)

From:

Alistair Young <[log in to unmask]>

Reply-To:

Discussion list for Shibboleth developments <[log in to unmask]>

Date:

Wed, 7 May 2008 10:26:41 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (291 lines)

I'm not sure pressured is the entirely correct word but to maintain  
continuity of service one must go with OpenAthens. EZProxy was bandied  
around for a bit then dropped with the advice that institutions should  
do it themselves. However, with user personalisations of electronic  
resources to worry about, ezproxy is an unknown as the access method  
is being changed from Athens to IP. As we've already seen, changing  
the access method from AthensLA (Gateway) to UK Federation (although  
they both use Shibboleth) results in loss of user personalisations.  
Some suppliers are addressing this though. So to maintain the user  
experience for Athens based resources that are not federation  
compliant, OpenAthens is the only route available. So we have to pay  
for access to resources that were previously funded. Does that  
constitute being pressured?

As for who's in and who's not in the fed, I rely on the federation  
metadata. If a supplier isn''t in there, they're not in the fed, no  
matter what any other document states.

Nicole's right about the organisation, IT, librarians etc and that's  
what we're doing. Should non tech people know about shibboleth? IMHO  
no. It's just another way of accessing electronic resources. What's  
more important is the use of the institutional credentials to access  
those resources. That's what we're promoting. Documentation isn't  
helped by the weird and wonderful versions of WAYFs out there though.  
Some have WAYF-less URLs, some use the fed wayf, others have their own  
versions and most call it something different.

Alistair


On 7 May 2008, at 10:00, Andrew Anderson wrote:

> >> A number of institutions have indicated that they have felt  
> pressure
> >> from Eduserv to enter into deals by the end of May. Can we get the
> >> message out, that they should feel no requirement to rush into  
> signing
> >> up to anything prior to the July 31st funding cut off date.
>
> Since OpenAthens is being priced as a shared service and the final  
> price is based on how many institutions commit by the end of May,  
> institutions may well feel they should commit by then as doing so  
> would benefit not just them but the whole community if we can get  
> past a threshold. If any institutions do feel that they have been  
> inappropriately pressurised, please do let us know.
>
> Naturally we won't be turning anyone away after May 31st, however as  
> Nicole suggests: waiting till the end of July wouldn’t be pragmatic.
>
> Andy
>
> --
> AJ Anderson
> Eduserv
> [log in to unmask]
>
> tel: +44 (0)1225 474303
> fax: +44 (0)1225 474301
>
> http://www.eduserv.org.uk
>
> From: Discussion list for Shibboleth developments [mailto:[log in to unmask] 
> ] On Behalf Of Nicole Harris
> Sent: 07 May 2008 09:20
> To: [log in to unmask]
> Subject: LA (Re: Progress towards the federated goal. Or otherwise.)
>
> Hi Bruce
>
> I will do my best to reply to your concerns.
>
> As we have mentioned several times, the definitive list of Service  
> Provider information is here: http://access.jiscinvolve.org/federated-access-and-publishers/ 
> .  We update this daily.  However, at the end of the day if a  
> publisher's timetable slips, the publishers timetable slips. As soon  
> as we are aware of this, we update the list.  We also recommend that  
> people sign-up to [log in to unmask] where  
> announcements about new services are made with full information  
> about how and what to do to sign up.
>
> In terms of signing up to Athens, you will effectively be signing a  
> contract for a service that is already in operation in your  
> organisation, so I don't see why a 6-8 week lead time would be  
> necessary.  Institutions already have to sign-up to the Athens Terms  
> and Conditions - it is just that this will now come accompanied by  
> an invoice.  Clearly you don't want to leave it until 31st July for  
> pragmatic purposes - Mark was merely responding to a message from  
> several institutions that they were feeling pressurised and saying  
> that they shouldn't ever feel pressurised by any supplier.  His  
> message is not particularly helpful here taken out of context.
>
> JISC has put significant effort in to working with publishers and  
> has definitely stepped up to the mark in taking responsibility for  
> primary negotiations.  We have one FTE who is purely dedicated to  
> working with publishers on this issue - and that is a significant  
> resource as JISC would not normally be able to shoulder an overhead  
> of this type.  JISC Collections has also played a significant role  
> and all new licenses ask for SAML compliance.  They also have daily  
> conversations with publishers and also put significant pressure on  
> for their services to be SAML compliant.   We take full  
> responsibility for this, but expect community support if this is  
> something you want to happen.
>
> Publishers do need to hear this directly from their customers and it  
> is necessary that institutions ask for SAML compliance as well.   
> This is not 'passing the buck', but just a necessary and pragmatic  
> step.  We have encouraged all libraries to take on this role and  
> Jane Charlton has provided a template of information that should be  
> included in messages to publishers.   We hope that all libraries are  
> engaged in this process.
>
> We have always been clear that this is not a 'techie' problem or a  
> library problem, but one that has to be worked on together.  The  
> first recommendation for institutions considering federated access  
> management has always been to form a working group of all the  
> relevant parties including technical staff, library staff and senior  
> management.
>
> I agree that the library role is significantly important at the  
> moment, and this is why we are running joint workshops with SCONUL  
> for librarians.  There is another SCONUL event next week.  I will be  
> giving a presentation describing the steps that JISC has had to go  
> through to set up its own directory service, IdP and set up access  
> to its own publisher and internal resources for federated access.   
> This will include pragmatic examples of library type activities that  
> we have undertaken like creating a wiki page called 'My Collections'  
> with embeddded WAYFless URLS to all our publisher resources, and how  
> we have tackled granularity issues as we do take out subscriptions  
> on a departmental basis.  I will circulate to the list as it sounds  
> like it will be useful to show a live example of what can be done.
>
> Let's not also forget the wider Service Provider development that  
> might fall outside of the library remit.  At the moment, we have a  
> programme of work internally to federate the JISC filestore, JISC  
> Wikis, JISC Involve and several JISC information systems.  This is  
> where some of the real benefits of federated access can be felt -  
> and it would be a pity to miss out on these.   I would expect these  
> type of services to be considered by the above mentioned working  
> group just a prominently as the third-party library resources.
>
> I hope this helps clarify.  Don't forget that my team is here to  
> help and answer questions whenever possible (although the team will  
> only be in place until December 2008 at the latest).  We are happy  
> to provide direct institutional advice as much as we can so please  
> ask!
>
> Best wishes
>
> Nicole
>
> ---------------
> JISC Executive
> JISC London office
> 1st Floor, Brettenham House South
> 5 Lancaster Place
> London WC2N 7EN
>
> tel: +44 (0)20 3006 6035
> mobile: +44 (0)7734 058308
> fax: +44 (0)20 7240 5377
>
>
> Bruce Rodger wrote:
> I've just come from an (internal) meeting on "our shibboleth
> position", with Library and IT people involved. It appears that we
> are all sharing the same frustrations. I feel obliged to write them  
> down.
>
> More importantly, I suspect that virtually every other University
> in the country is having similar meetings, with similarly depressing
> outcomes.
>
>
> This morning, I was forwarded a message from Mark Williams at JISC,  
> via the RSC.
>
> It says: (apologies for selective quoting - I'm endeavouring to keep  
> this message as short as possible. I do not believe I have quoted  
> out of context)
>
>
>
> A number of institutions have indicated that they have felt pressure
> from Eduserv to enter into deals by the end of May. Can we get the
> message out, that they should feel no requirement to rush into signing
> up to anything prior to the July 31st funding cut off date.
>
> While this is undoubtedly good advice in principle, I would be a
> little concerned about hanging back until the very last minute.
> It's only good advice if you are the only institution to take it!
> If a large number of institutions were to "sign up" on the very
> last day, who knows how long it would take Eduserv to process these
> applications. My experience is that software & services agreements
> of this type can easily take 6-8 weeks to put in place. If you were
> to "sign" on 31 July, would you still have service on 1st August?
>
>
> The status of publishers membership of the
> UK Federation and Shibboleth compliance is becoming clearer everyday
>
> Is it? It's certainly not becoming clearer to us! Even the list of
> suppliers compliance levels which we were given by JISC is confusing
> and contradictory.
>
> Is there a definitive public list of service providers who have (a)
> committed to be shib-compliant by midsummer and (b) who have
> categorically stated that they will not be compliant by this time?
> Note that this list is NOT the same as simply looking at the
> membership of UKfederation.
>
> This is an area where we should be sharing experiences.
>
> I get the feeling that there is still a certain amount of  
> brinksmanship
> going on - a game of "chicken", in which there will be no clear-cut
> winners or losers.
>
>
> So, at a practical level, how can we move matters forward? My own
> feeling is that for too long the community has regarded the "shib
> problem" as being largely a technical one. It's now clear that this
> isn't the case - the technology isn't a problem. The difficulties
> are procedural, commercial and political.
>
> To me, it appears that the concerted pressure that the community
> was supposed to be applying to individual suppliers to hasten their
> migration towards federated access just isn't happening. The word
> from JISC is for individual institutions - the customers - to apply
> such commercial pressure, but the feeling from the community is
> that JISC should be the ones doing the pushing. I don't know who is  
> right.
>
> But everyone seems to think that it's Someone Else's Job. Who is  
> taking responsibility?
>
>
> Does anyone have any comments on what I've said? Am I, and my
> colleagues, completely out of step? Or are you all as confused and
> concerned as us?
>
> At the end of the day, I'm not going to lose too much sleep over
> this - it's another of those "Someone Else's Problems". At first I
> thought my job was the difficult bit - delivering the tools (an
> IdP) which are necessary at our end. But it's now clear that that
> was the easy task; the real difficulties have just begun, and it's
> the library people, not IT, who will have the most difficult task
> over the coming months.
>
> Bruce.
> -- 
> Bruce Rodger                      [log in to unmask] Network  
> Manager, IT Services      |http://www.strath.ac.uk/IT/People/bruce.html
> The University of Strathclyde     | +44 (0)141 548 3300
> Glasgow G4 0LN, Scotland.         | Fax        553 4100
>
> "The University of Strathclyde is a charitable body, registered in
> Scotland, number SC015263."
>
> ----------------------------------------------------------------------
> Anything in this message which does not clearly relate to the official
> work of the sender's organisation shall be understood as neither given
> nor endorsed by that organisation.
>
>
> ----------------------------------------------------------------------
>
>
>
>
> Unless otherwise agreed expressly in writing by a senior manager of
> Eduserv, this communication is to be treated as confidential and the
> information in it may not be used or disclosed except for the purpose
> for which it has been sent.
> If you have reason to believe that you are not the intended recipient
> of this communication, please contact the sender immediately.
> No employee or agent is authorised to enter into any binding agreement
> or contract on behalf of Eduserv or Eduserv Technologies Ltd., unless
> that agreement is subsequently confirmed by the conclusion of a  
> written
> contract or the issue of a purchase order.
> Eduserv (Limited by Guarantee) – company number 3763109 - and
> Eduserv Technologies Ltd – company number – 4256630 - are both
> companies incorporated in England and Wales and have their registered
> offices at Queen Anne House, 11 Charlotte Street, Bath, BA1 2NE.
>

--------------
mov eax,1
mov ebx,0
int 80h

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

November 2023
February 2023
January 2023
November 2022
October 2022
September 2022
June 2022
January 2022
November 2021
October 2021
September 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
June 2019
May 2019
March 2019
February 2019
January 2019
November 2018
July 2018
June 2018
May 2018
April 2018
March 2018
January 2018
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
March 2017
February 2017
January 2017
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
March 2016
February 2016
January 2016
December 2015
November 2015
September 2015
August 2015
June 2015
April 2015
March 2015
February 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager