December 2019 - Idpy-discuss

Notes: idpy dev call, 17 December 2019

by hlflanagan＠sphericalcowgroup.com

Attendees: Giuseppe, John P , Johan, Hannah Sebuliba, Antonis, Nikos, Ivan, Hanna Short, Christos, Heather Regrets: Roland 0. Agenda bash 1. OIDC Federation update a. OIDF poll open until 7 January 2020 (https://openid.net/foundation/members/polls/196 <https://openid.net/foundation/members/polls/196>) Requires OIDF membership to vote, but that isn’t expensive for individuals 2. GitHub review a. OIDC implementations Idpy Board agreed last week to take the OIDC python libraries under idpy. Roland and OIDF have to make sure IPR is clear and Roland will then move the GitHub repositories into idpy. Over time, we will deprecate the pyOP libraries. b. Satosa - https://github.com/IdentityPython/SATOSA <https://github.com/IdentityPython/SATOSA> New front end for Satosa being worked on by Antonis and Nikos. The initial work is being done outside GitHub (because it is part of another project). New Satosa release - includes a (potentially) breaking change around how we map to OIDC claims that have multiple values. When we create a new response towards an RP, the internal representations have multiple value (e.g., given name has 2 values). The OIDC spec does not dictate how to handle multiple values; that must be defined per claim. Sometimes the values are separated by a space, sometimes an array. The core claims in Satosa are now defined, and other claims are also being defined. See the documentation for more detail. Next on the list for development: https://github.com/IdentityPython/SATOSA/pull/280 <https://github.com/IdentityPython/SATOSA/pull/280> https://github.com/IdentityPython/SATOSA/pull/279 <https://github.com/IdentityPython/SATOSA/pull/279> https://github.com/IdentityPython/SATOSA/issues/179 <https://github.com/IdentityPython/SATOSA/issues/179> https://github.com/IdentityPython/SATOSA/issues/148 <https://github.com/IdentityPython/SATOSA/issues/148> Also a request by Giuseppe to look at: https://github.com/IdentityPython/SATOSA/pull/220 <https://github.com/IdentityPython/SATOSA/pull/220> - These require some architectural decisions about if/how to create new hooks in modules. Ivan will consider the options. https://github.com/IdentityPython/SATOSA/pull/216 <https://github.com/IdentityPython/SATOSA/pull/216> - Should be easy to merge. https://github.com/IdentityPython/SATOSA/pull/214 <https://github.com/IdentityPython/SATOSA/pull/214> - Ivan needs to review this one in more detail. c. pySAML2 - https://github.com/IdentityPython/pysaml2 <https://github.com/IdentityPython/pysaml2> Next on the list for development: https://github.com/IdentityPython/pysaml2/pull/647 <https://github.com/IdentityPython/pysaml2/pull/647> https://github.com/IdentityPython/pysaml2/pull/518 <https://github.com/IdentityPython/pysaml2/pull/518> https://github.com/IdentityPython/pysaml2/pull/602 <https://github.com/IdentityPython/pysaml2/pull/602> Will also start looking at signing and encryption. Hannah Short is willing to assist. d. pyFF - https://github.com/IdentityPython/pyFF <https://github.com/IdentityPython/pyFF> Leif is working on the PR for pyFF 2.0. This will drop the front end from the pyFF repo; the front end and UX will be under thiss.io (which is not an idpy project). 3. AOB Hackathon - did not get a lot of people; having it overlap the sessions did not work well. Suggestion was made to make another hackathon on 23 March, immediately before the eduGAIN town hall. Tutorial - rather than dev work, suggest we try this at the BoF planned for TNC Workshop - suggest we try a more focused dev day where we define in advance what things people will work on; this will require a bit more framing but has the possibility of more code as an outcome. Maybe use the TIIME meeting for this? Heather to send out a poll to see what idpy developers would be interested in. Next call scheduled for January 7. Ivan (and other team members) will be traveling that day to an eduTEAMS meeting; Ivan to verify whether he can make that day or if we need to move the call.

4 years, 9 months

5
9
0 0

Reminder: idpy dev call (off week) 17 December 2019

by hlflanagan＠sphericalcowgroup.com

Meeting URL https://bluejeans.com/252755948 <https://bluejeans.com/252755948> Meeting ID 252 755 948 Agenda: 0. Agenda bash 1. OIDC Federation update a. OIDF poll open until 7 January 2020 (https://openid.net/foundation/members/polls/196 <https://openid.net/foundation/members/polls/196>) 2. GitHub review a. Oidc implementations: b. Satosa - https://github.com/IdentityPython/SATOSA <https://github.com/IdentityPython/SATOSA> c. pySAML2 - https://github.com/IdentityPython/pysaml2 <https://github.com/IdentityPython/pysaml2> d. pyFF - https://github.com/IdentityPython/pyFF <https://github.com/IdentityPython/pyFF> 3. AOB

4 years, 9 months

2
1
0 0

Shift in time/format for the idpy dev call, 10 December 2019

by hlflanagan＠sphericalcowgroup.com

Hola a todos! As discussed on the last call, rather than have a conference call tomorrow, we will be encouraging people to tune into the Identity Python slack channel to participate in the Hackathon. The hackathon starts at 09:00 UTC -6 (an hour after our usual call time), and the slack channel can be found here: https://join.slack.com/t/identity-python/shared_invite/enQtNzEyNjU1NDI1MjUy… I look forward to “seeing” you tomorrow! -Heather Sent from my iPad

4 years, 9 months

1
0
0 0

OSS IAM Track @ TIIME 18.2.2020

by rainer＠hoerbe.at

Hi group, Peter Gietz is again convening an OSS workshop track. Please see his invitation to give a talk and volunteer in numbers! Cheers, Rainer > Hi all, > > since last meeting in Vienna seems to have been successful > (unfortunately I was knocked out by a pneumonia, and couldn't attend), > I am planning to organize a follow up event next February again adjunct > to the TIIME workshop (see https://tiimeworkshop.eu/) > > Thus it will take place *Tuesday Feb. 18th in Vienna* and all of you are > cordially invited to participate. Since the TIIME organisation has > changed, there will be a participation fee of € 150 early bird and € 180 > regular for this day. If you also attend the TIIME unconference (most > recommended) the price per day gets down. Presenters will have the fee > waived. > > As the last time, this should not be about every one telling the others > about their wonderful product, but rather should focus on technical > aspects, standardization, interoperability, cooperation models, etc. It > is again called (un)conference, since it should be a compromise between > conference and unconference, i.e. only short presentations and most of > the time of each slot devoted to discussion. Last time it was invitation > only, but I am thinking about publishing the program to advertise more > participation, but I am still unsure and would like to hear your > opinions on this. > > Please get back to me with comments, proposals for slots, presentations, > panel discussions, statement of willingness to participate without > presenting and the like. If you think, I left some one out here, please > notify me and I will send this invitation and follow ups. > > Looking forward to seeing you in Vienna! > > Cheers, > > Peter >

4 years, 10 months

1
0
0 0

2024

2023

2022

2021

2020

2019

2018

2017

Idpy-discuss December 2019