- FIM4L - lists3.daasi.de

Hello and brief intro
by Shillum, Chris (ELS-NYC) 12 Sep '19

12 Sep '19

Hi All My name's Chris Shillum. I'm VP of Identity Management and Platform Strategy at Elsevier, looking after Elsevier's access management system among other things. I'm also a member of the SeamlessAccess.org governance group and we co-chair of the RA21 project. I've been involved in federated authentication for many years and looking forward for joining the discussions of this group Happy for my name and affiliation to be published on the website. Cheers Chris _________________________ Chris Shillum VP Identity and Platform Strategy ELSEVIER | Research Products +1 212 462 1987 office +1 646 250 8029 mobile c.shillum(a)elsevier.com<mailto:email@elsevier.com> https://orcid.org/0000-0002-1108-3660<http://orcid.org/0000-0002-1108-3660>

3 3

Re: [Fim4l] Hello and brief intro
by Raoul Teeuwen 12 Sep '19

12 Sep '19

Hi Chris. Welcome, great you’re on board ... Not to ‘welcome’ you with a potential unpleasant discussion, and i do not know what you heard about the discussion after people saw what buttons Elsevier has put online at ScienceDirect, but: do you see any possibiity to either roll back the changes in access/sign in-buttons to a previous version (and maybe 1st have a discussion with people in the identity and access management field, or fix the current situation? Or is this a case of Elsevier balancing all aspects, of which ‘strategies to make money’ of course is one, which leads to, accorinding to many in our field, the strange current UI/UX? Redefining ‘access’ and ‘sign in’, and argumenting that it’s just a matter of users getting used to that, sounds a bit ... ‘unreal’... With kindest regards, met vriendelijke groet, Raoul tel:+31641195989 On 06/09/2019, 21:15, "FIM4L on behalf of Shillum, Chris (ELS-NYC)" <fim4l-bounces(a)lists.daasi.de<mailto:fim4l-bounces@lists.daasi.de> on behalf of c.shillum(a)elsevier.com<mailto:c.shillum@elsevier.com>> wrote: Hi All My name’s Chris Shillum. I’m VP of Identity Management and Platform Strategy at Elsevier, looking after Elsevier’s access management system among other things. I’m also a member of the SeamlessAccess.org governance group and we co-chair of the RA21 project. I’ve been involved in federated authentication for many years and looking forward for joining the discussions of this group Happy for my name and affiliation to be published on the website. Cheers Chris _________________________ Chris Shillum VP Identity and Platform Strategy ELSEVIER | Research Products +1 212 462 1987 office +1 646 250 8029 mobile c.shillum(a)elsevier.com<mailto:email@elsevier.com> https://orcid.org/0000-0002-1108-3660<http://orcid.org/0000-0002-1108-3660>

2 1

Elsevier unilaterally shutting down pseudonymous access to institutionally licensed resources?
by Peter Schober 04 Sep '19

04 Sep '19

Prompted by a local support request I tried to verify that federated logins to https://www.sciencedirect.com/ are still working -- only to find out that in order to log I'm requested to register an account (even after having logged in successfully via my institution[1]) by providing an email address and, later on, also my full name: "Enter your email to continue with ScienceDirect" "Email is required" "Your given name is required." "Your family name is required." I obviously didn't get the memo about how it was agreed that all anonmous/pseudonymous use of institutionally licensed resources has been shut down?! Best regards, -peter [1] The SAML IDP I used to log in has a contract with Elsevier and is sending the agreed upon data via SAML (the "common-lib-terms" entitlement as well as a "persistent" SAML NameID) -- same as it always had.

3 5

JISC/UKFAM
by Checkley, Caroline R 21 Aug '19

21 Aug '19

Dear all Jisc is setting up an advisory steering group for the UK federation (Single Sign On access and authentication via Shibboleth and OpenAthens etc) and they would like FIM4l to be a part of this. Personally I’m struggling to keep up with the discussions that have been occurring on the FIM4l list I’m not sure I would be the best person. The terms of reference are as follows: Jisc is establishing an advisory steering group to support the development of the UK federation. The aim is to provide advice and guidance on service and development priorities within the UK federation and complimentary aspects of the Jisc Trust & Identity area through a process that identifies and responds to UKf stakeholder needs and supports the implementation of the Jisc Strategic Plan (https://www.jisc.ac.uk/about/corporate/strategy). We hope we can include members from representative bodies such as UCISA, SCONUL, CILIP, National & Public libraries, Publishers Association, REFEDS as well as operational members of the academic library, research, IT and MIS communities. We anticipate the group being comprised of around 12-20 members and WILL NOT inherently have a technical focus. We are contacting the bodies above directly; however, we welcome individuals to put themselves forward if they participate in any of the sectors mentioned. The Advisory group will meet physically twice a year (with video conferencing as an option), however there is an expectation that offline discussion will occur as subjects arise. We hope to have the first meeting of the group on Tuesday October 8th in London and UKFADVISORYGROUP(a)JISCMAIL.AC.UK<mailto:UKFADVISORYGROUP@JISCMAIL.AC.UK> will be available as a discussion list. Terms of reference will be developed in consultation with participants however they are likely to include; • Provide advice and focus for the UK federation, designed to lower the cost of access and identity management, improve user experience and engage with future evolution. • Facilitate debate and where appropriate action to help support the community in its access and authentication requirements, reflecting the changing needs of said community and supporting the alignment of Jisc T&I activity with stakeholder need. • Work in collaboration with the rest of Jisc to support innovative T&I activity and act as a sounding board for new ideas and developments relating to Jisc T&I activity. • Widen the participation of the relevant interested communities • Communicate with all stakeholders in order to foster a mutual understanding of the issues surrounding T&I services and development. • Support Jisc in achieving and demonstrating value for money of the UK federation service. • Champion Jisc T&I activity within UK HE & Research, FE, Schools and local government communities. • The group will focus on the operational and strategic aspects of UKf T&I activity, although an expectation that technical issues will be surfaced for further detailed examination. • Maintain an overall watching brief on behalf of its stakeholders on all Jisc activity which can impact on the T&I space, as a result the group will request reports on these activities where required. If you are interested in participating in the UK federation Advisory Steering Group, please feel to contact me and we can discuss what membership of the working group would entail in further detail. Would anyone in the FIM4l group be willing to be a part of this steering group? All the best Caroline Caroline Checkley Digital Systems and Services Librarian Library Services University of Essex T 01206 873176 E checkc(a)essex.ac.uk ► library.essex.ac.uk<https://library.essex.ac.uk/> WE ARE ESSEX TOP 20 FOR RESEARCH EXCELLENCE TEF GOLD 2017 QAP WINNER 2017 [cid:image001.png@01D55806.05FD44B0] [cid:image002.png@01D55806.05FD44B0]<https://www.facebook.com/UniEssexLibrary>[cid:image003.png@01D55806.05FD44B0]<https://twitter.com/UniEssexLibrary>[cid:image004.jpg@01D55806.05FD44B0]<https://www.instagram.com/uniessexlibrary/>

1 0

Educational Technologies and Student Data - Briefing for Libraries
by Mimi Calter 02 Aug '19

02 Aug '19

This statement from IFLA is relevant for this group: https://www.ifla.org/publications/node/92339?og=30 Mimi ____________ Mimi Calter Deputy University Librarian Stanford Libraries 101 Green Library Stanford, CA 94305-6004 office: +1-650-725-5813 cell: +1-650-799-4515 fax: +1-650-725-4902 skypename: mcalter e-mail: mcalter(a)stanford.edu<mailto:mcalter@stanford.edu>

2 1

Scopus
by Jiri Pavlik 30 Jul '19

30 Jul '19

Dear all, Elsevier requests eduPersonTargetedID and eduPersonEntitlement attributes in metadata at eduID.at for Scopus and other services - https://met.refeds.org/met/entity/https%253A%252F%252Fsdauth.sciencedirect.… Requested attributes are missing in eduGAIN metadata - https://met.refeds.org/met/entity/https%253A%252F%252Fsdauth.sciencedirect.… At Scopus users can activate personalisation adding name and e-mail address. A screenshot attached. This is very close match with our FIM4L guidelines and recommendations. Have a great summer days Jiri

8 31

New Email Forum for Service Providers
by Laura Paglione 14 Jul '19

14 Jul '19

*[Please excuse the cross posting!]* Announcing a new discussion forum for Service Providers: the *Service Providers Operating Group* This forum is a mailing list that is open to Service Providers registered in any Federation - i.e., any system that uses Single Sign-On services from universities or other federated identity providers. We expect discussions to be non-technical, and focused on access and authorization topics of interest to services, for example, signing into your service, and using sign-in to gain access to appropriate resources and services. A small FAQ is included below, and more information can be found at the group's wiki page: https://wiki.refeds.org/display/GROUPS/SPOG *TO JOIN*: Send an email to the mailing list owners > spog-request(a)lists.refeds.org > <spog-request@lists.refeds.org?subject=Request%20Access%20to%20SPOG%20mailing%20list&body=I'm%20requesting%20membership%20into%20the%20Service%20Provider%20Operating%20Group%3A%0A%0Aemail%3A%20%3Center%20your%20email%20here%3E%0Aservice%20name%3A%20%3Center%20the%20name%20of%20your%20service%20here%3E%0Aevidence%20of%20registered%20service%3A%20%3Csuch%20as%20your%20EntityID%20from%20a%20site%20like%20https%3A%2F%2Fmet.refeds.org%2F%3E> > to request access. Also, see the wiki page for more information. *+=+=+ A SMALL FAQ +=+=+* *I'm not a Service Provider, how can I help?* If you are a Federation Operator, please share this opportunity with your Sevice Providers. If you are an Identity Provider, please encourage your key services to participate. *What do you mean, "Service Provider"?* Service Providers use federated sign-on services (for example, from universities and other institutions) to access their services. An important component of Federated Identity Management is the "dance" between Identity Providers and Service Providers that enable Single Sign-On services, and the exchange of information about the individual involved from the Identity to Service Provider. *But aren't all Service Providers different?* There is great diversity in Service Providers, though, at the core of the FIM integration, significant similarities exist for implementation, need for attributes, assurances, and more. *Why create a group?* While there are several specific-topic groups that advocate for the needs of Service Providers (e.g., FIM4R, FIM4L), there currently isn't an easy way to share information, understand needs, provide peer support or solicit feedback across the entirety of the Service Provider community. The inability to talk with this community as a whole can lead to assumptions about what this community needs, thinks, and knows, some of which are likely suffering from limited direct interaction. This group hopes to provide a larger, unified voice for topics where there is similarity across providers; we believe this will benefit the community as a whole. *Why are only Service Providers invited to join?* Participation is open to representatives from Service Providers from any Federation. We will use tools such as the Metadata Explorer Tool (MET) <https://met.refeds.org/> to verify participants. Our goal is to make this a safe, collegial and targeted place to have discussions specific to Service Providers. For this reason, it is only open to Service Providers. Those who represent different types of entities are encouraged to include someone who only works on the Service Provider work, or to FIRMLY wear their Service Provider "hat" when interacting in this community. ANY service provider can join. This group includes entities from commercial organizations to virtual organizations. *How much time is this going to take?* This is a mailing list; there are no specific time requirements to participate, and no work deliverables that you will be expected to contribute to. We expect discussions to be non-technical, and focused on access and authorization topics of interest to services, for example, signing into your service, and using sign-in to gain access to appropriate resources and services. Feel free to reach out to me if you have any questions -- <https://about.me/lpaglione?promo=email_sig&utm_source=product&utm_medium=em…> Laura Paglione about.me/lpaglione <https://about.me/lpaglione?promo=email_sig&utm_source=product&utm_medium=em…> Innovation • Technology • Creation lpaglione(a)SphericalCowGroup.com <lpaglione(a)sphericalcowgroup.com>

3 2

Charter published on the FIM4L website
by Jos Westerbeke 21 Jun '19

21 Jun '19

Hi all, I'm glad to inform that we have published our Charter document on http://fim4l.org. The website also has been updated. Have a look<http://fim4l.org/>! Within about 3 weeks we'll put the Guidelines and Recommendations<https://docs.google.com/document/d/1pIaEXfw9ZWnXM4p6Dd2Lri7RFWKgr7ObKLEGfUy…> also on the website. Please give your comments if you like. Have a wonderful weekend! Jos

1 0

Anouncement
by Jos Westerbeke 07 Jun '19

07 Jun '19

Dear participants of FIM4L, This week we (Jiri, Peter G, Raoul and me) have finished the Charter document and now it is ready to be published. We have a new public version: FIM4L charter - public version. New URL: https://docs.google.com/document/d/11KpYa84AsgWjiKnnRr1r6_zH2ynN9kv3pNP2hRv… Could you please check this version for a latest edit eventually? It is now a draft version 1.0 and we will publish it within a week or two in PDF format on the website. And remove the draft status. When published, the version on Google Docs will stay there for collecting public comments. An update of the website fim4l.org is on the way. We keep the old version<https://docs.google.com/document/d/17EllwItlnB3fYhJ2ZNpX6Z1gUfF1948ORRvtbIA…> for internal use. We also edited and cleaned up our other document, the FIM4L guidelines and recommendations<https://docs.google.com/document/d/1pIaEXfw9ZWnXM4p6Dd2Lri7RFWKgr7ObKLEGfUy…>. And will make it ready for publishing. Thank you all for the work already done! Jos

1 0

Fwd: Re: ICOLC & FIM4L
by Peter Gietz 28 Mai '19

28 Mai '19

Hi List, erroneously this discussion was without CC to the list. Well here it is. Cheers, Peter -------- Weitergeleitete Nachricht -------- Betreff: Re: ICOLC & FIM4L Datum: Thu, 23 May 2019 13:16:46 +0200 Von: Peter Gietz <peter.gietz(a)daasi.de> An: Hi Jos, Thanks a lot for this very interesting pointer. I think the ALR comments make the FIM4L activity even more important, since we address at least parts of the gaps analyzed by ALR. 1.) Obviously this is the case with regards to privacy and I feel encouraged to stick to our current recommendations but also to be more explicit and detailed about the potential privacy related consequences. To not further delay of the publication of the guidelines I would like to propose to star another document only dealing with privacy related consequences of FIM. The other two main subjects of the ALR gap analysis are: 2.) accessibility aspects, which are more directly directed to the RA21 Javascript-enhancements for easing the discovery process, where I am unsure whether FIM4L should take this up 3.) auditing and statistics: Here I do see FIM4L subject space and again I would recommend to write yet another document on that, instead of addressing too much more (than the already discussed attribute for statistics) in tzhe guidelines text. As to your question: I very much propose to try to get ALR into FIM4L. Cheers, Peter Am 22.05.19 um 09:33 schrieb Jos Westerbeke: > Hi, > > An interesting response from ARL to RA21: > https://www.arl.org/news/arl-news/4780-arl-comments-on-ra21-proposal-for-ac… > > Should we reach out to ARL? > > cheers, > Jos > -- Peter Gietz, CEO DAASI International GmbH Europaplatz 3 D-72072 Tübingen Germany phone: +49 7071 407109-0 fax: +49 7071 407109-9 email: peter.gietz(a)daasi.de web: www.daasi.de Sitz der Gesellschaft: Tübingen Registergericht: Amtsgericht Stuttgart, HRB 382175 Geschäftsleitung: Peter Gietz

1 0