November 2017 - Satosa-dev - lists3.sunet.se

by ivan.kanak＠gmail.com

Hey everyone, Now that satosa-microservices are split into their own repository we should set the process which acquires them back to the setup. There are many options here: - have each microservice be its own python package and selectively install it using pip - have the microservices repo be a package itself and use pip to install it - have microservices repo as a git module under satosa (not suggested) - have microservices as something completely external and fetch using http/git (as shown below). This could mean a lot of different things - ie, should microservices use code from satosa? if so, satosa is a dependency to microservices and as such this makes microservices a package with dependencies, etc. - (more options?) Skoranda mentioned that > If you need the LDAP Attribute Store microservice you must also install ldap3 using pip: This indicates that certain microservices have their own dependencies. Users cannot guess what dependencies are needed for a certain microservice. This information should be explicit and automatically resolved by the microservice installation process. This leads me to think to having each microservice as a separate (python) package, with its own dependencies and deployment process, is the way to go. This is not a simple decision to make. Let's have a discussion on how the dev-community think it is better to be solved. Cheers, PS: This discussion was triggered by skoranda's PR here: https://github.com/IdentityPython/SATOSA/pull/168#discussion_r149634137 -- Ivan c00kiemon5ter Kanakarakis >:3

6 years

4
6
0 0

Bi-weekly call schedule

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?)

6 years, 4 months

6
6
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

6 years, 5 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

6 years, 5 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

6 years, 5 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

6 years, 5 months

7
19
0 0

2024

2023

2022

2021

2020

2019

2018

2017

Satosa-dev November 2017