- Idpy-discuss - lists3.sunet.se

Fwd: Announcing the first Trust & Identity Hackathon - 23 September 2019 @ Copenhagen, Denmark

by hlflanagan＠sphericalcowgroup.com

You probably saw this on the REFEDS mailing list, but just in case... > > **Please share among your (human) networks!** > > The R&E community, from the scholarly information world to research communities to universities, all depend on digital identity and trust models. Come join us to work on the code that will grow the capabilities in the trust and identity arena at the first T&I Hackathon, offered in conjunction with the NORDUnet Technical Workshop and brought to you by REFEDS, Identity Python, and NORDUnet. > > As with any Hackathon, this is about developers. It is not a day of tutorials and sessions - it’s about code. Do you have ideas for Identity Discovery? Join the seamlessaccess.org <http://seamlessaccess.org/> table to work on thiss.io <http://thiss.io/>. Do you have an idea for a new Satosa microservice? Join the Satosa developers table. Do you have some other idea for integrating new functionality to support assurance levels? Strong authentication? Come with your ideas and set up a table to start the work! Ideas are already being recorded on the REFEDS wiki: https://wiki.refeds.org/x/AwauAg <https://wiki.refeds.org/x/AwauAg>. > > Registration for the Hackathon is part of the overall NORDUnet Technical Workshop (http://www.ntw2019.net <http://www.ntw2019.net/>). The NORDUnet Technical Workshop (NTW) is is held every two years in Copenhagen. The main event (24-26 September 2019) features a series of workshops on subjects related to research and education networks, including a full day of trust & identity workshops. The NTW brings together 150-200 practitioners from research and education networking communities in the Nordic countries and beyond. The event is held a 5-minute metro ride from Copenhagen airport, 10 minutes from central Copenhagen. > > We look forward to seeing you there! > > Heather Flanagan, REFEDS coordinator

5 years, 10 months

1
0
0 0

Agenda: idpy Developers call, 25 June 2019

by hlflanagan＠sphericalcowgroup.com

Date: Tuesday, 25 June 2018 Time: 06:00 PT | 09:00 ET | 15:00 GMT https://bluejeans.com/163562895 Regrets: Heather Agenda: 0. Agenda bash 1. Anything interesting from TNC? 2. GitHub review a. pySAML2 - https://github.com/IdentityPython/pysaml2 b. Satosa - https://github.com/IdentityPython/SATOSA c. pyFF - https://github.com/IdentityPython/pyFF d. ... 3. AOB Thanks! Heather Sent from my iPad

5 years, 10 months

2
2
0 0

Agenda: idpy Developers call, 11 June 2019

by hlflanagan＠sphericalcowgroup.com

Date: Tuesday, 11 June 2018 Time: 06:00 PT | 09:00 ET | 15:00 GMT https://bluejeans.com/163562895 <https://bluejeans.com/163562895?src=join_info> Agenda: 0. Agenda bash 1. Use case discussion: SAMLVirtualCoFrontend (https://github.com/IdentityPython/SATOSA/wiki <https://github.com/IdentityPython/SATOSA/wiki>) 2. Discontinuing Python 3.4 3. GitHub review a. pySAML2 - https://github.com/IdentityPython/pysaml2 <https://github.com/IdentityPython/pysaml2> b. Satosa - https://github.com/IdentityPython/SATOSA <https://github.com/IdentityPython/SATOSA> c. pyFF - https://github.com/IdentityPython/pyFF <https://github.com/IdentityPython/pyFF> d. ... 4. AOB Thanks! Heather

5 years, 11 months

2
2
0 0

Satosa and JWTConnect-Python

by roland＠catalogix.se

Hi! Since we haven’t even begun the work on building a front-end based on JWTConnect-Python to Satosa I guess the chance that we have something working before TNC19 is very slim indeed. Is there any documentation anywhere on what to think about when building a new front-end ? Or should I just use the front-end based on pyop as a pattern ? — Roland The higher up you go, the more mistakes you are allowed. Right at the top, if you make enough of them, it's considered to be your style. -Fred Astaire, dancer, actor, singer, musician, and choreographer (10 May 1899-1987)

5 years, 11 months

1
0
0 0

Agenda: idpy Developers call, 28 May 2019

by hlflanagan＠sphericalcowgroup.com

Date: Tuesday, 28 May 2018 Time: 06:00 PT | 09:00 ET | 15:00 GMT https://bluejeans.com/489221749 <https://bluejeans.com/489221749> Regrets: Heather Agenda: 0. Agenda bash 1. GitHub review a. pySAML2 - https://github.com/IdentityPython/pysaml2 <https://github.com/IdentityPython/pysaml2> b. Satosa - https://github.com/IdentityPython/SATOSA <https://github.com/IdentityPython/SATOSA> c. pyFF - https://github.com/IdentityPython/pyFF <https://github.com/IdentityPython/pyFF> d. … 2. OIDC libraries - status 3. AOB

5 years, 11 months

1
0
0 0

Draft Pull Requests

by ivan.kanak＠gmail.com

Hello everyone, we discussed on the biweekly whether there is a way to have pull requests marked as not-ready to merge. Gitlab supports this: if you prefix the merge request with "WIP:" (work in progress) it will disable the merge button. Github has a similar feature called draft pull requests. You can read more about it here: https://help.github.com/en/articles/about-pull-requests#draft-pull-requests I suggest we make use of this wherever needed ;) Cheers, -- Ivan c00kiemon5ter Kanakarakis >:3

5 years, 12 months

1
0
0 0

Status CMService

by rainer＠hoerbe.at

I have a use case for SATOSA + a consent service. There was a discussion about moving CMService to IdPy at the Meeting from 6 March 2018[1], and Roland merged SURFnet’s updates into the its-dirg repo later (27 May 27 2018). There was no further activity afterwards. Is someone using CMService, and possibly interested in moving it into IdPy? Cheers, Rainer [1] https://lists.sunet.se/pipermail/idpy-discuss/2018-March/000114.html <https://lists.sunet.se/pipermail/idpy-discuss/2018-March/000114.html>

5 years, 12 months

2
2
0 0

idpy Developers call - alternate time

by hlflanagan＠sphericalcowgroup.com

Hola a todos! Thank you for filling out the poll. The best time (but not perfect) is Thursday, 16 May 2019 @ 14:00 UTC. I’ve sent a calendar invitation to the individuals who usually attend the calls; if you have not received one and would like a calendar invite, please let me know! Connection details for the call are below. I will send out an agenda on Tuesday. Meeting URL https://bluejeans.com/163562895?src=join_info Meeting ID 163 562 895 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 Thanks! Heather

6 years

1
0
0 0

Doodle Poll - alternate day/time for the next idpy dev call

by hlflanagan＠sphericalcowgroup.com

Hola a todos! Several people have let me know that they are not available during our usual call window on 14 May 2019. I’ve put together a doodle poll to try and find an alternate time; we’ll try and get back to our usual call cycle on 28 May 2019 (pending participants’ availability). https://doodle.com/poll/rdfawvpi78ce8p9h If you would fill that out ASAP, I would appreciate it! Some options are for this Friday, so the sooner we have a list of viable choices, the better. Thanks! Heather

6 years

1
0
0 0

pysaml2 PR 613 more flexible entity category import

by skoranda＠gmail.com

Hi, I just pushed pysaml2 PR #613 to enable more flexible entity catetory support: https://github.com/IdentityPython/pysaml2/pull/613 Before this PR entity category modules to be used to help configure attribute release for an IdP could only be imported from the name space saml2.entity_category. This is cumbersome and made overlaying new entity category modules or custom versions of existing entity category modules difficult. With this PR entity category modules are first searched for on the general module import path. If they are not found there then the current default of importing from saml2.entity_category.<module> is used. Thanks, Scott K

6 years

1
0
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

Idpy-discuss