Dear all,

I'd suggest to add following guidelines for libraries, universities at our FIM4L Guidelines and recommendations:

- register IdP in eduGAIN - support CoCo and SIRTFI - release NameID/eduPersonTargetedID, eduPersonScopedAffiliation, schacHomeOrganisation, eduPersonEntitlement to publishers SPs as basic set of attributes allowing publishers to carry out authorisation, handling security incidents and provide personalisation - release other attributes such as Display/Common name or Email described in the eduGAIN Attribute Profile for the best user experience with personalisation of a service

Looking forward to discuss it in our call, so far Tuesday next week 10-11 is the best fit - https://doodle.com/poll/rxemq8remn858qd7

Sunny regards from Prague

Jiri

On Wed, Feb 13, 2019 at 10:03 AM Jiri Pavlik jiri.pavlik@mzk.cz wrote:

Dear all,

I added more time slots for FIM4L next call in the Doodle poll - https://doodle.com/poll/rxemq8remn858qd7 There are also Europe late afternoon time slots so American colleagues could join us for the call in not so early morning hours.

Thanks a lot Jos, for the update and Raoul for the recommendations and guidelines draft.

Best regards

         Jiri

On Fri, Feb 8, 2019 at 12:45 PM Jos Westerbeke jos.westerbeke@eur.nl wrote:

...

Hi everyone,

We set up a Google Team Drive where we can store our documents. The "proto-charter" and "guidelines" G-docs are already in it.

Since we have G-suite at Erasmus university, we can offer this kind of storage (it's covered by much better "Terms of services" than the free version of Google docs).

I would like to invite you all to this Team Drive. If you send me or Jiri your Google Gmail address, we can add you to our Team Drive "FIM4L workgroup", with edit rights.

Once you have permission, the Team Drive will appear in your Google Drive https://drive.google.com/. And you can find all our files there.

For those who don't want to get actively involved, we can/will let the public files stay public with access for everyone with the link plus comment. (not edit)

*Next step*

I'm trying to find out how we can start working towards our goal. Obviously, we have to define our goal first ;)

Should our first goal be something like the following?

• A reference with recommendations for establishing SSO authentication

between libraries and publishers.

It would be very beneficial for libraries if we could say to a publisher: "We want the establish SSO according the FIM4L recommendations, option 1, which you can find at <common FIM4L URL>." for example.

Steps we can take: (supposedly)

• Formulate a 'minimal disclosure policy'.

• Build an 'SSO reference' for e-resource suppliers.

• Build a FIM4L website/page where we can publish our

recommendations/guidelines/references.

Raoul already wrote a draft policy/recommendation/guideline based on the document and input from Jiri.

Here is the new "FIM4L Guidelines and recommendations https://docs.google.com/document/d/1pIaEXfw9ZWnXM4p6Dd2Lri7RFWKgr7ObKLEGfUy2nck/edit" document proposal by Raoul.

( https://docs.google.com/document/d/1pIaEXfw9ZWnXM4p6Dd2Lri7RFWKgr7ObKLEGfUy2... )

Jiri will add some more dates to the doodle poll https://doodle.com/poll/rxemq8remn858qd7. Please check it, and subscribe to be notified for any changes to the Doodle. There are still people coming on board, so we probably have to move the next meeting a bit forward.

Feel free to comment on the text in the documents!

What we have so far:

FIM4L proto-charter https://docs.google.com/document/d/17EllwItlnB3fYhJ2ZNpX6Z1gUfF1948ORRvtbIA_l88/edit (With the Problem Statement)

FIM4L Guidelines and recommendations https://docs.google.com/document/d/1pIaEXfw9ZWnXM4p6Dd2Lri7RFWKgr7ObKLEGfUy2nck/edit (new version)

With kind regards

Jos

Jos Westerbeke

Library IT Specialist / Demandmanager | Erasmus University Rotterdam, Library | Burgemeester Oudlaan 50 | 3062PA Rotterdam | jos.westerbeke@eur.nl | +31 640295513

---

Fim4l mailing list Fim4l@lists.daasi.de http://lists.daasi.de/listinfo/fim4l

Dear all,

the next FIM4L call is scheduled for tomorrow 10-11 a.m. CET. I am sorry to hear, Licia, that you cannot join the call, but happy that Peter Gietz will manage to join the call.

Thanks a lot for the comments, Licia. There is a challenge for libraries, universities from countries where there is no national federation which can register their IdP in eduGAIN. From R&S definition publishers are not allowed to register their SP in in the R&S category - "Example Service Providers may include (but are not limited to) collaborative tools and services such as wikis, blogs, project and grant management tools that require some personal information about users to work effectively. This Entity Category should not be used for access to licensed content such as e-journals."

Looking forward for the call tomorrow morning, all the best

Jiri

On Sun, Feb 17, 2019 at 10:33 PM Licia Florio licia.florio@geant.org wrote:

Dear all,

Sadly I won’t be able to join this call, due to other conflicting calls.

I have just a small comment on the agenda: I think that the item “register IdP in eduGAIN” is misleading. IdPs register with a federation and via the federation they are exposed to eduGAIN.

Also I wonder if it would not be more practical to discuss about the deployment of REFEDS R&S instead than discussing individual attributes.

Cheers, Licia

Sent from my iPad

On 15 Feb 2019, at 11:00, Jiri Pavlik jiri.pavlik@mzk.cz wrote:

Dear all,

I'd suggest to add following guidelines for libraries, universities at our FIM4L Guidelines and recommendations:

• register IdP in eduGAIN
• support CoCo and SIRTFI
• release NameID/eduPersonTargetedID, eduPersonScopedAffiliation,

schacHomeOrganisation, eduPersonEntitlement to publishers SPs as basic set of attributes allowing publishers to carry out authorisation, handling security incidents and provide personalisation

• release other attributes such as Display/Common name or Email described

in the eduGAIN Attribute Profile for the best user experience with personalisation of a service

Looking forward to discuss it in our call, so far Tuesday next week 10-11 is the best fit - https://doodle.com/poll/rxemq8remn858qd7

Sunny regards from Prague

       Jiri

On Wed, Feb 13, 2019 at 10:03 AM Jiri Pavlik jiri.pavlik@mzk.cz wrote:

...

Dear all,

I added more time slots for FIM4L next call in the Doodle poll - https://doodle.com/poll/rxemq8remn858qd7 There are also Europe late afternoon time slots so American colleagues could join us for the call in not so early morning hours.

Thanks a lot Jos, for the update and Raoul for the recommendations and guidelines draft.

Best regards

         Jiri

On Fri, Feb 8, 2019 at 12:45 PM Jos Westerbeke jos.westerbeke@eur.nl wrote:

...

Hi everyone,

We set up a Google Team Drive where we can store our documents. The "proto-charter" and "guidelines" G-docs are already in it.

Since we have G-suite at Erasmus university, we can offer this kind of storage (it's covered by much better "Terms of services" than the free version of Google docs).

I would like to invite you all to this Team Drive. If you send me or Jiri your Google Gmail address, we can add you to our Team Drive "FIM4L workgroup", with edit rights.

Once you have permission, the Team Drive will appear in your Google Drive https://drive.google.com/. And you can find all our files there.

For those who don't want to get actively involved, we can/will let the public files stay public with access for everyone with the link plus comment. (not edit)

*Next step*

I'm trying to find out how we can start working towards our goal. Obviously, we have to define our goal first ;)

Should our first goal be something like the following?

• A reference with recommendations for establishing SSO authentication

between libraries and publishers.

It would be very beneficial for libraries if we could say to a publisher: "We want the establish SSO according the FIM4L recommendations, option 1, which you can find at <common FIM4L URL>." for example.

Steps we can take: (supposedly)

• Formulate a 'minimal disclosure policy'.

• Build an 'SSO reference' for e-resource suppliers.

• Build a FIM4L website/page where we can publish our

recommendations/guidelines/references.

Raoul already wrote a draft policy/recommendation/guideline based on the document and input from Jiri.

Here is the new "FIM4L Guidelines and recommendations https://docs.google.com/document/d/1pIaEXfw9ZWnXM4p6Dd2Lri7RFWKgr7ObKLEGfUy2nck/edit" document proposal by Raoul.

( https://docs.google.com/document/d/1pIaEXfw9ZWnXM4p6Dd2Lri7RFWKgr7ObKLEGfUy2... )

Jiri will add some more dates to the doodle poll https://doodle.com/poll/rxemq8remn858qd7. Please check it, and subscribe to be notified for any changes to the Doodle. There are still people coming on board, so we probably have to move the next meeting a bit forward.

Feel free to comment on the text in the documents!

What we have so far:

FIM4L proto-charter https://docs.google.com/document/d/17EllwItlnB3fYhJ2ZNpX6Z1gUfF1948ORRvtbIA_l88/edit (With the Problem Statement)

FIM4L Guidelines and recommendations https://docs.google.com/document/d/1pIaEXfw9ZWnXM4p6Dd2Lri7RFWKgr7ObKLEGfUy2nck/edit (new version)

With kind regards

Jos

Jos Westerbeke

Library IT Specialist / Demandmanager | Erasmus University Rotterdam, Library | Burgemeester Oudlaan 50 | 3062PA Rotterdam | jos.westerbeke@eur.nl | +31 640295513

---

Fim4l mailing list Fim4l@lists.daasi.de http://lists.daasi.de/listinfo/fim4l

---

Fim4l mailing list Fim4l@lists.daasi.de http://lists.daasi.de/listinfo/fim4l

Hi,

there are 3 options as we discussed on the last FIM4L call.

1. maximum privacy for users - just transient nameID is released on top of attributes for authorisation (eduPersonScopedAffiliation, eduPersonEntitlement, schacHomeOrganisation)

2. possible service personalisation for users - eduPersonTargetedID is released on top of attributes for authorisation, users can voluntarily fill out name, e-mail address and any other info at a profile page within the service for personalisation

3. seamless single sign-in for users - eduPersonTargetedID, name (displayName or givenName+sn) and mail attributes are released on top of attributes for authorisation just like with R&S, data protection is secured thanks to CoCo

Libraries are free to choose any o the 3 options. Libraries in Germany and Netherlands tend to prefer 1 or 2, libraries in Italy and Czech Republic tent to prefer 3.

Providers with no service personalisation are fine with attributes for authorisation released in all three cases. Providers with service personalisation are supposed to handle any of the 3 options which library choose.

Makes sense?

You may like to have a look at OpenAIRE - https://www.openaire.eu/. OpenAIRE is supporting CoCo, requested attributes are eduPersonTargetedID, mail and displayName, optional attributes are cn, givenName, sn -

https://met.refeds.org/met/entity/https%253A%252F%252Fwww.openaire.eu%252Fsi...

All the best

Jiri

On Tue, Feb 19, 2019 at 11:09 AM Raoul Teeuwen raoul.teeuwen@surfnet.nl wrote:

Sounds great (as recommendations, I assume).

Re attribute release: I assume, just like with R&S, we recommend libraries to be able to release the mentioned attribute set, but only release the attributes the SP states as required in it’s metadata?

Re release attributes for personalization: do we want libraries want to be able to release those, or is our recommendation that if an SP wants to do personalization, it should offer a ‘profile page’ within it’s service, where a user can (voluntarily) fill out any info for personalization?

Kindest regards,

Raoul

tel:+31641195989

On 15/02/2019, 11:00, "Fim4l on behalf of Jiri Pavlik" < fim4l-bounces@lists.daasi.de on behalf of jiri.pavlik@mzk.cz> wrote:

Dear all,

I'd suggest to add following guidelines for libraries, universities at our FIM4L Guidelines and recommendations:

• register IdP in eduGAIN
• support CoCo and SIRTFI
• release NameID/eduPersonTargetedID, eduPersonScopedAffiliation,

schacHomeOrganisation, eduPersonEntitlement

to publishers SPs as basic set of attributes allowing publishers to carry out authorisation, handling security incidents

and provide personalisation

• release other attributes such as Display/Common name or Email described

in the eduGAIN Attribute Profile

for the best user experience with personalisation of a service

Looking forward to discuss it in our call, so far Tuesday next week 10-11 is the best fit -

https://doodle.com/poll/rxemq8remn858qd7

Sunny regards from Prague

       Jiri

On Wed, Feb 13, 2019 at 10:03 AM Jiri Pavlik jiri.pavlik@mzk.cz wrote:

Dear all,

I added more time slots for FIM4L next call in the Doodle poll - https://doodle.com/poll/rxemq8remn858qd7 There are also Europe late afternoon time slots so American colleagues could join us for the call in not so early morning hours.

Thanks a lot Jos, for the update and Raoul for the recommendations and guidelines draft.

Best regards

         Jiri

On Fri, Feb 8, 2019 at 12:45 PM Jos Westerbeke jos.westerbeke@eur.nl wrote:

Hi everyone,

We set up a Google Team Drive where we can store our documents. The "proto-charter" and "guidelines" G-docs are already in it.

Since we have G-suite at Erasmus university, we can offer this kind of storage (it's covered by much better "Terms of services" than the free version of Google docs).

I would like to invite you all to this Team Drive. If you send me or Jiri your Google Gmail address, we can add you to our Team Drive "FIM4L workgroup", with edit rights.

Once you have permission, the Team Drive will appear in your Google Drive https://drive.google.com/. And you can find all our files there.

For those who don't want to get actively involved, we can/will let the public files stay public with access for everyone with the link plus comment. (not edit)

*Next step*

I'm trying to find out how we can start working towards our goal. Obviously, we have to define our goal first ;)

Should our first goal be something like the following?

• A reference with recommendations for establishing SSO authentication

between libraries and publishers.

It would be very beneficial for libraries if we could say to a publisher: "We want the establish SSO according the FIM4L recommendations, option 1, which you can find at <common FIM4L URL>." for example.

Steps we can take: (supposedly)

• Formulate a 'minimal disclosure policy'.

• Build an 'SSO reference' for e-resource suppliers.

• Build a FIM4L website/page where we can publish our

recommendations/guidelines/references.

Raoul already wrote a draft policy/recommendation/guideline based on the document and input from Jiri.

Here is the new "FIM4L Guidelines and recommendations https://docs.google.com/document/d/1pIaEXfw9ZWnXM4p6Dd2Lri7RFWKgr7ObKLEGfUy2nck/edit" document proposal by Raoul.

( https://docs.google.com/document/d/1pIaEXfw9ZWnXM4p6Dd2Lri7RFWKgr7ObKLEGfUy2... )

Jiri will add some more dates to the doodle poll https://doodle.com/poll/rxemq8remn858qd7. Please check it, and subscribe to be notified for any changes to the Doodle. There are still people coming on board, so we probably have to move the next meeting a bit forward.

Feel free to comment on the text in the documents!

What we have so far:

FIM4L proto-charter https://docs.google.com/document/d/17EllwItlnB3fYhJ2ZNpX6Z1gUfF1948ORRvtbIA_l88/edit (With the Problem Statement)

FIM4L Guidelines and recommendations https://docs.google.com/document/d/1pIaEXfw9ZWnXM4p6Dd2Lri7RFWKgr7ObKLEGfUy2nck/edit (new version)

With kind regards

Jos

Jos Westerbeke

Library IT Specialist / Demandmanager | Erasmus University Rotterdam, Library | Burgemeester Oudlaan 50 | 3062PA Rotterdam | jos.westerbeke@eur.nl | +31 640295513

---

Fim4l mailing list Fim4l@lists.daasi.de http://lists.daasi.de/listinfo/fim4l