==>short intro
Andreas Waldvogel, MAS LIS, Programme Executive Online Library
Globethics.net Library
Please see my profile on LinkedIn:
https://www.linkedin.com/in/waldvogelandreas/
Interested in RA21/Seamless Access and GetFTR
Though no experience with
Federated Identity Management (Shibboleth/Athens)
As we at Globethics.net (https://repository.globethics.net )
Still use EZproxy for managing remote or rather campus wide access to restricted resources
I fully support the LIBER recommendations for (minimum) attribute release
==> consent to publish your name on website (name and affiliation
only)
yes, do please use my name and affiliation on your website
with thanks and regards
Andreas Waldvogel
Programme Executive Online Library
Globethics.net
waldvogel(a)globethics.net
Tel.: +41 (0) 22 791 63 42
Skype: awaldvogel_ge
Globethics.net Head Office
150 route de Ferney, CH 1211 Geneva 2, Switzerland
www.globethics.net
Follow us: Facebook, Twitter and Linked In
-----Original Message-----
From: FIM4L <fim4l-bounces(a)lists.daasi.de> On Behalf Of fim4l-request(a)lists.daasi.de
Sent: 07 August 2020 08:37
To: Waldvogel Andreas <waldvogel(a)globethics.net>
Subject: Welcome to the "FIM4L" mailing list (Digest mode)
Welcome to the FIM4L(a)lists.daasi.de mailing list!
---------------------------------------------------------------------------
The email list of FIM4L is growing. That's a good thing; we get attention from libraries, NREN's, and many supportive partners, from EU, Africa and the US.
To keep track of all participants of FIM4L, we ask every participant for a short introduction. At least your name, function and affiliation. And why you're on FIM4L would be nice too. Just because many of the list don't know everyone involved.
We also want to ask you whether you're fine with publishing your institution and personal name on the http://fim4l.org website.
So, could you please write to the list:
short intro
consent to publish your name on website (name and affiliation
only)
---------------------------------------------------------------------------
To post to this list, send your message to:
fim4l(a)lists.daasi.de
General information about the mailing list is at:
http://lists.daasi.de/listinfo/fim4l
If you ever want to unsubscribe or change your options (eg, switch to or from digest mode, change your password, etc.), visit your subscription page at:
http://lists.daasi.de/options/fim4l/waldvogel%40globethics.net
You can also make such adjustments via email by sending a message to:
FIM4L-request(a)lists.daasi.de
with the word `help' in the subject or body (don't include the quotes), and you will get back a message with instructions.
You must know your password to change your options (including changing the password, itself) or to unsubscribe without confirmation. It is:
salam007
Normally, Mailman will remind you of your lists.daasi.de mailing list passwords once every month, although you can disable this if you prefer. This reminder will also include instructions on how to unsubscribe or change your account options. There is also a button on your options page that will email your current password to you.
Hola a todos!
This message went out to the SP Operators Group (forwarded with permission). I think members of this list might find the proposed federation baselines to be of interest, and I strongly encourage you to go take a look and offer comments. Additional information (including links) is below.
Heather Flanagan — Translator of Geek to Human
https://sphericalcowconsulting.com
---------- Forwarded message ----------
From: Alan Buxey <alan.buxey(a)myunidays.com>
Date: Jul 29, 2020, 8:29 AM -0700
To: spog(a)lists.refeds.org
Subject: [spog] REFEDS baseline expectations
> hi,
>
>
> Federated Access offers users a way to access online content in secure
> and privacy-preserving ways. Establishing a federated authentication
> workflow for Research and Education (R&E), however, requires trusted
> entities — R&E Identity Federations — to coordinate the necessary
> Trust, Scalability, and Interoperability. To enable this coordination,
> REFEDS (the Research and education Federations group,
> https://refeds.org) has launched a Baseline working group. The goal of
> this group is to create a minimal Baseline of technical and
> operational behavior that the Identity Providers (IdPs), Services
> Providers (SPs), and the Federation Operators themselves must follow.
> This baseline would be enforced by the Federation Operators. We are
> asking for your input to develop these baselines.
>
>
> The Baseline working group has been active since spring this year and
> has started to draft the REFEDS Baseline Expectations. These
> expectations will be described in a group of documents, the first
> being a high-level holistic document that defines the conceptual
> framework of the Baseline Expectations. After the group has finished
> with the holistic document, the working group will create additional
> documents that describe how the expectations will be applied in more
> detail for different federation technologies.
>
>
> The Baseline Expectations working group has its home in the REFEDS wiki space:
>
>
> https://wiki.refeds.org/display/GROUPS/Baseline+Expectations+Working+Group
>
>
> For the Baseline Expectations to be successful, we require the
> feedback and input of all stakeholders in the ecosystem. Service
> Providers and their customers are asked to read the current draft
> holistic Baseline Expectations to get an understanding of requirements
> and expectations that will be put to them going forward:
>
>
> https://docs.google.com/document/d/1u0XuvPRFKH5RaDEcgdp3jyfgNZbWAR4Q1yl0GzN…
>
>
> We are particularly interested in knowing if these requirements are
> sufficient, appropriate, and implementable, and if there are any gaps
> in the expectations.
>
>
> Whilst the REFEDS group is still working on the initial requirements
> and documentation, we hope that the first Baseline target will align
> fairly closely to what has already been achieved in the US with the
> InCommon Federation , their initial Baseline document is here:
>
>
> https://incommon.org/federation/baseline-expectations-for-trust-in-federati…
>
> If you are already an SP operating in InCommon, you will already be
> aware of these requirements and have undertaken work and processes to
> align to them. If not, please can you spend some time looking over
> this document and provide your feedback/views and opinions on the
> requirements and please feel free to expand with other requirements
> that you would like to see in future Baseline versions (InCommon are
> already working on their next level).
>
>
> Regards,
>
>
> Alan and Pål, REFEDS Baseline working group co-chairs
