- Satosa-dev - lists3.sunet.se

by hlflanagan＠sphericalcowgroup.com

Hello all, The process of setting up a call fell off the radar, but hopefully the poll results for a decent time slot for a regular, biweekly call still works for most. The proposal is to have a a biweekly call starting Tuesday, December 5 @ 15:00 GMT+1. This will give us four calls (five if we really want to meet on January 2) between now and TIIME. DRAFT AGENDA (Please add your topics to the thread) * Introductions * Planning for the TIIME workshop (what do you want to get out of it?) * Project governance status * Current coding priorities Does anyone have a particular preference for video conference tools? We could use Google Hangouts, Skype, or someone could volunteer something (Lifecloud?)

8 years, 5 months

6
6
0 0

Bi-weekly call schedule

by ivan.kanak＠gmail.com

Hi all, I will not be available before 11/12 because I'm traveling. Other than that, I had troubles with Skype group chat too. On 30 Nov 2017 13:12, "Leif Johansson" <leifj at sunet.se> wrote: On 2017-11-30 14:45, Ioannis Kakavas wrote: > I prefer not to use Skype if possible. We have had very decent > experience with https://appear.in/ <https://appear.in/>for the amount > of people we foresee in these calls. > I have zoom zoom usually rocks _______________________________________________ Satosa-dev mailing list Satosa-dev at lists.sunet.se https://lists.sunet.se/listinfo/satosa-dev

8 years, 5 months

3
2
0 0

Default value semantics

by ivan.kanak＠gmail.com

Hello all, Across the satosa codebase there are places where a default behaviour is needed. There are two ways we signify this: - Using the empty string as a dictionary key - Using the string "default" as a dictionary key (where other keys define behaviour/settings for specific entities.) I am not sure how the project ended up with two ways to signify a default set, but it is annoying. In terms of the chosen strings to represent the default set, "" seems to be a valid choice, as no entity (usually entityid) should be empty. "default" on the other hand, is more descriptive and self documenting, and hopefully nobody uses that to describe and entity (or as an entityid). In terms of handling this, there is currently a function under `src/satosa/util.py` namely `get_dict_defaults()` that favours "" over "default" – it fallbacks to "default" if "" is not set. While this is fine and works, it is not used across the codebase. I would like this to be resolved and have a single way to signify a default behaviour. What are your opinions? Do you think this should settle to a single way of representing a default set, even if that means that people using "" or "default" will have to migrate (this would be a breaking change for their configs)? Which is the most appropriate way to go? Cheers, PS: This discussion was triggered by skoranda's PR here: https://github.com/IdentityPython/satosa_microservices/pull/6/files#r148260… -- Ivan c00kiemon5ter Kanakarakis >:3

8 years, 6 months

3
2
0 0

setting the IdP Discovery Profile common domain cookie

by skoranda＠gmail.com

Hi, The Shibboleth IdP has the nice feature [1] that it can be configured to set the IdP Discovery Profile common domain cookie [2] after receiving a valid assertion from an IdP. It can be useful because only IdPs that a user has actually successfully used are recorded and then later revealed as choices to the user in a subsequent flow. I have a use case where it would be helpful if the SP side of SATOSA could do the same thing. I ran find . -type f -exec grep -l _saml_idp {} \; on the SATOSA source and it did not return anything, so I suspect this functionality is not currently supported by SATOSA. Would anybody object to adding it? It would of course be "off" by default and would only set the cookie (with configurable properties) when configured to do so. Thoughts? Thanks, Scott K P.S. I understand that new approaches to discovery that will likely come out of the RA21 effort will probably supplant this functionality, but as usual the use case I need to support needs this "right now"... [1] See idpHistory and idpHistoryProps at https://wiki.shibboleth.net/confluence/display/SHIB2/NativeSPSessions [2] See section 4.3 of http://docs.oasis-open.org/security/saml/v2.0/saml-profiles-2.0-os.pdf

8 years, 6 months

1
0
0 0

Announcement - project PM

by leifj＠sunet.se

Dear all, I am pleased to announce that Heather Flanagan [1] has been funded by the National Institute of Health's National Institute of Allergies and Infectious Diseases (NIH NIAID) to act as the project manager for the Identity Python project. This represents a major step for the project and will enable us to move forward more quickly and will also help us establish the Identity Python governance and organizational structure needed for long-term sustainability of the project. [1] https://www.linkedin.com/in/hlflanagan/ Cheers Leif

8 years, 6 months

1
0
0 0

SATOSA dev meeting

by leifj＠sunet.se

Folks, I'm thinking it might be a good idea to have a dev meeting soon to discuss progress and some of the recent development efforts that have been very active recently. Who would be interested in (and able to) come to Stockholm for a (say) 2 day workshop sometime in the Oct-Nov-Dec time frame (when Sweden really shines as a warm and sunny place you really want to travel to) ? Cheers Leif

8 years, 6 months

7
19
0 0

Transfered SATOSA to IdentityPython

by lundberg＠sunet.se

Hello, Just to inform you I have just transfered SATOSA from SUNET to IdentityPython on github. Br -- Johan Lundberg SUNET Tulegatan 11 113 53 Stockholm +46730714375

8 years, 7 months

1
0
0 0

[Idpy-discuss] SATOSA dev meeting

by skoranda＠gmail.com

Actually it is a little late. Anytime after 6 am Chicago time works for me. Thanks, Scott On Oct 12, 2017 3:56 AM, "Roland Hedberg" <roland at catalogix.se> wrote: > Works for me. > > So, 6-7pm CEST ? Or is that to early for you Scott ? > > > 12 okt. 2017 kl. 10:52 skrev Leif Johansson <leifj at sunet.se>: > > > > On 2017-10-12 10:43, Scott Koranda wrote: > >>> Looking at calendars I don't believe we can pull this together > >>> sufficiently soon for it to make sense to have a dev meeting > >>> before TIIME. > >>> > >>> So I think we should just talk to Rainer, reserve a full day > >>> of work at TIIME and maybe try to have a couple of VCs (maybe > >>> even a regular bi-weekly project call) until then. > >>> > >>> What say you all? > >> > >> I think that will work. > >> > >> When should the VCs start? I propose we aim for the week of October 30. > >> > >> To help organize an agenda, I also propose we start using the GitHub > >> wiki for SATOSA at > >> > >> https://github.com/SUNET/SATOSA/wiki > >> > >> Thoughts? > > > > Yeah that works. How about 25:th ? > > > > _______________________________________________ > > Satosa-dev mailing list > > Satosa-dev at lists.sunet.se > > https://lists.sunet.se/listinfo/satosa-dev > > -- Roland > "Education is the path from cocky ignorance to miserable uncertainty.” - > Mark Twain > > > >

8 years, 7 months

1
0
0 0

Ioannis moving to elastic

by nroy＠internet2.edu

Hi all, I noticed that Ioannis accepted a job at elastic. Ioannis, congrats! Will you still be working on PySAML stuff? Best, Nick

8 years, 7 months

2
2
0 0

https://github.com/rohe/pysaml2/issues/463

by rainer＠hoerbe.at

The SAML backend breaks on loading metadata from a URL if it contains non-ASCII characters (https://github.com/rohe/pysaml2/issues/463) After analyzing the cause I found that this has already been fixed in pysaml2 since 4.4.0. My preferred option would be to nudge pysaml2 maintainers to release a new pypi version. It could save other developers from hunting bugs that have been fixed. If that is not feasible, the docker installation option should be changed to install the current version from github. Cheers, Rainer

8 years, 7 months

2
3
0 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

Satosa-dev