- Idpy-discuss - lists3.sunet.se

Reminder: call cancelled for 7 January 2020

by hlflanagan＠sphericalcowgroup.com

Hola a todos! As a reminder, the idpy dev call is cancelled for 7 January 2020. We are pushing the call out one week; expect a SEPARATE calendar invitation for that call. Thanks, Heather

4 years, 4 months

1
0
0 0

uniAuth v1.0.0 release

by giuseppe.demarco＠unical.it

Hi everyone, I'm happy to announce the first official release of uniAuth (v1.0.0), a SAML2 IdP based on Django and pySAML2. https://github.com/UniversitaDellaCalabria/uniAuth/releases/tag/v1.0.0 Next minor releases will focus on the updates coming from pySAML2. Next major releases will introduce OIDC through django-oidc-op (oidcendpoint) https://github.com/peppelinux/django-oidc-op Thank you idpy community ____________________ Dott. Giuseppe De Marco CENTRO ICT DI ATENEO University of Calabria 87036 Rende (CS) - Italy Phone: +39 0984 496961 e-mail: giuseppe.demarco at unical.it

4 years, 4 months

1
0
0 0

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, 4 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, 5 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, 5 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, 5 months

1
0
0 0

Invitation: idpy Dev call (off-week) @ Tue Dec 17, 2019 6am - 7am (PST) (idpy-discuss@lists.sunet.se)

by hlflanagan＠sphericalcowgroup.com

You have been invited to the following event. Title: idpy Dev call (off-week) Meeting URL https://bluejeans.com/252755948?src=join_info Meeting ID 252 755 948 Want to dial in from a phone? Dial one of the following numbers: +1.408.740.7256 (US (San Jose)) +1.408.317.9253 (US (Primary, San Jose)) (see all numbers - https://www.bluejeans.com/premium-numbers) Enter the meeting ID and passcode followed by # Connecting from a room system? Dial: bjn.vc or 199.48.152.152 and enter your meeting ID & passcode When: Tue Dec 17, 2019 6am – 7am Pacific Time - Los Angeles Where: https://bluejeans.com/252755948 Calendar: idpy-discuss at lists.sunet.se Who: * hlflanagan at sphericalcowgroup.com - creator * idpy-discuss at lists.sunet.se Event details: https://www.google.com/calendar/event?action=VIEW&eid=MjJsczltcjM3dDk1a3Fyd… Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account idpy-discuss at lists.sunet.se because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to send a response to the organizer and be added to the guest list, or invite others regardless of their own invitation status, or to modify your RSVP. Learn more at https://support.google.com/calendar/answer/37135#forwarding

4 years, 5 months

1
0
0 0

Invitation: idpy Dev call (2020) @ Every 2 weeks from 6am to 7am on Tuesday from Tue Jan 7, 2020 to Tue Dec 29, 2020 (PST) (idpy-discuss@lists.sunet.se)

by hlflanagan＠sphericalcowgroup.com

You have been invited to the following event. Title: idpy Dev call (2020) Meeting URLhttps://bluejeans.com/567481057?src=join_infoMeeting ID567 481 057Want to dial in from a phone?Dial one of the following numbers:+1.408.740.7256 (US (San Jose))+1.408.317.9253 (US (Primary, San Jose))(see all numbers - https://www.bluejeans.com/premium-numbers)Enter the meeting ID and passcode followed by #Connecting from a room system?Dial: bjn.vc or 199.48.152.152 and enter your meeting ID & passcode When: Every 2 weeks from 6am to 7am on Tuesday from Tue Jan 7, 2020 to Tue Dec 29, 2020 Pacific Time - Los Angeles Where: https://bluejeans.com/567481057 Calendar: idpy-discuss at lists.sunet.se Who: * hlflanagan at sphericalcowgroup.com - creator * idpy-discuss at lists.sunet.se Event details: https://www.google.com/calendar/event?action=VIEW&eid=MW9jNXE4MmZ0aGtuYzFna… Invitation from Google Calendar: https://www.google.com/calendar/ You are receiving this courtesy email at the account idpy-discuss at lists.sunet.se because you are an attendee of this event. To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar. Forwarding this invitation could allow any recipient to send a response to the organizer and be added to the guest list, or invite others regardless of their own invitation status, or to modify your RSVP. Learn more at https://support.google.com/calendar/answer/37135#forwarding

4 years, 5 months

1
0
0 0

Notes: idpy dev call, 26 November 2019

by hlflanagan＠sphericalcowgroup.com

Attendees Giuseppe, John P, Scott, Heather, Ivan, Scott Notes: 0. Agenda bash 1. Hackathon @ TechEx https://wiki.refeds.org/pages/viewpage.action?pageId=44959235 <https://wiki.refeds.org/pages/viewpage.action?pageId=44959235> See: https://meetings.internet2.edu/2019-technology-exchange/detail/10005634/ <https://meetings.internet2.edu/2019-technology-exchange/detail/10005634/> 2. GitHub review There were new releases for both Satosa (two) and pySAML2. a. Satosa - https://github.com/IdentityPython/SATOSA <https://github.com/IdentityPython/SATOSA> Expect a new docker image. Tests also fixed. New merge requests for logging. Will be looking at scopes shortly, based on a PR from Scott. After this will be looking at PR 280 (from the NTW Hackathon). This will replace another option previously used by eIDAS. Expect a new release in the next few weeks. There is a collaboration between eduTEAMS, GRNET, and KIT, that will create a new OIDC front end for Satosa. See "AARC-G052: Specification for validating externally issued OAuth2 tokens" https://docs.google.com/document/d/11Amv6kjPvVVgWB71iEaj6NcrhlNzht7HP9GJK6c… <https://docs.google.com/document/d/11Amv6kjPvVVgWB71iEaj6NcrhlNzht7HP9GJK6c…> In the future, this will also allow for support of OIDC federations. This is not quite ready for developing against; it is a draft. Expectation is to take this to the broader OIDC community for general adoption b. pySAML2 - https://github.com/IdentityPython/pysaml2 <https://github.com/IdentityPython/pysaml2> One big development in pySAML2 - Ivan has pushed the commit to drop support for Python 2 Other changes have been about using extractor for metadata (particularly MDUI attributes). There was also a fix on how we select the bindings. Added support for IPv6 addresses enclosed in brackets. Current PRs in progress 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> https://github.com/IdentityPython/pysaml2/pull/647 <https://github.com/IdentityPython/pysaml2/pull/647> Expect a new release tomorrow. c. pyFF - https://github.com/IdentityPython/pyFF <https://github.com/IdentityPython/pyFF> 3. AOB Next call scheduled for Dec 10 during the Hackathon - we’ll open up a chat on Slack, rather than an actual call Suggest moving the Dec 24 call to Dec 17 and catch up on what came out of the Hackathon Heather will create new calendar entries for 2020 Heather to try and schedule a board meeting during TechEx An idpy BoF has been requested for TNC20

4 years, 5 months

1
0
0 0

Notes: idpy dev call, 12 November 2019

by hlflanagan＠sphericalcowgroup.com

(Really not sure why these didn’t go through when I sent them two weeks ago) Attendees: Roland, Giuseppe, John P., Scott K., Heather Notes: 0. Agenda bash 1. OIDC federation 1.0 draft updates 45 day review period has been announced. "We’ve published draft 10 of the OpenID Connect Federation Specification <https://openid.net/specs/openid-connect-federation-1_0-10.html> and started the 45-day review period for the proposed second Implementer’s Draft of the specification. This will be the version used for the hackathon at the Internet2 Technology Exchange <https://meetings.internet2.edu/2019-technology-exchange/> next month.” Voting closed on 11 November 2019 One area of concern is that the different areas of interest (e.g., higher ed vs commercial) are not aware of each other’s work One individual on the commercial side wants to see more trust and ad hoc federation put directly in the hands of the user, such that they could define trust and decide if they want to trust others. This may be something that can be built later on top of the existing proposal. Looking forward to testing out possible implementation ideas against the draft at the upcoming Hackathon See Roland’s implementation here: https://github.com/rohe/fedservice <https://github.com/rohe/fedservice> See also the OIDF OIDCRE working group - https://openid.net/wg/rande/ <https://openid.net/wg/rande/> 2. GitHub review a. Oidc implementations: a.1 oidcendpoint - a.2 jwtconnect-python-oidcrp - Roland has been focused on testing the tests. Giuseppe will look for time to build on services over Roland’s libraries Of interest: see OIDC Session Description <https://docs.google.com/document/d/1RdiQo4JNJOkbew19z57n7u4T2Xi2feZ3pa93orX…> documentation b. Satosa - https://github.com/IdentityPython/SATOSA <https://github.com/IdentityPython/SATOSA> Goal is still to get the OIDC libraries into Satosa as soon as possible; recognize there are other demands on Ivan’s time, so Roland may end up doing some of this and having Ivan refactor it as needed. 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, 5 months

1
0
0 0

2024

2023

2022

2021

2020

2019

2018

2017

Idpy-discuss