November 2018 - Idpy-discuss

Notes: idpy developers call, 13 November 2018

by hlflanagan＠sphericalcowgroup.com

Notes: Attending: Heather, Ivan, Roland, Jonas L., Davide Regrets: Scott, Martin, Christos 0. Agenda bash 1. Governance update Board has the kick off call today. 2. idpy developers meeting @ TIIME - agenda building Handling of micro services (Satosa) Handling logging, esp. with plugins (Satosa) Handling of XML (pySAML) Action: Heather to ask Rainer about having a side meeting 3. PR review - Satosa (Satosa PRs - https://github.com/IdentityPython/SATOSA) Ivan has been working on changing the internal hashing mechanisms; it is all backward compatible but you will get deprecation warnings (PR 196). Now have a new micro service called “hasher”. Also worked on OIDC frontend/backend and using self-signed certificates. (PR 197) eduTEAMS now only has one commit difference from main branch. (PR 182) Ivan will be working on that soon so that eduTEAMS can be using the main Satosa repository. A new Satosa version will be released tomorrow; big change log. - pySAML2 (https://github.com/IdentityPython/pysaml2) Johan had two PRs regarding Unicode attribute values that needed to be either encrypted or signed. There may be some refactoring of this in the future. Ivan is now working on PR 396, related to having the ability to specify which signature or digest method you want to use (right now you can only do that via the configuration file). Martin has a new PR (556) around the internal attribute conversion between names and friendly names. Ivan agrees with those changes and will be merging soon. Scott has added tests to PR 485. Ivan will be merging this soon and cutting a release. Some new issues have been reported. 555 suggests that we put every name in the root name space, but that doesn’t quite work in real life. XML and XML operations - Ivan had proposed we use a separate module to handle XML operations, which would also allow us to switch XML back ends. - pyFF (https://github.com/IdentityPython/pyFF) Leif will be working on separating this code into more discrete components (e.g., discovery will become separate). - Governance docs (https://github.com/IdentityPython/Governance) 4. AOB OIDC federations - would like to run pilots soon. There is a python implementation, but that’s it. Would like to have Satosa be able to handle OIDC federations. If there is a priority list of what will be done soon, Roland would like to see OIDC federations high up on that list. Roland has running flask instances for the RP and OP; it should be fairly straightforward to do something. Not sure about the interface between the front end and Satosa itself. Ivan would like to see this too, though it hasn’t been prioritized yet. Note that Davide is also interested in this effort. Suggest Roland and Ivan have a separate call next week to discuss further. Another project is underway within AARC that will depend on Satosa: Evaluating assurance. Expect additional PRs related to this effort.

5 years, 5 months

4
7
0 0

Notes: idpy developers call, 27 November 2018

by hlflanagan＠sphericalcowgroup.com

Attendees: Christos, Johan L, Roland, Heather, Martin, Ivan, Rainer Notes: 0. Agenda bash 1. Introductions (if needed) 2. Project review - Satosa (Satosa PRs - https://github.com/IdentityPython/SATOSA) Roland still waiting to hear from Ivan on creating a federation aware front end to satosa; they will discuss at a f2f meeting next week. Many things are on the list. Ivan has been working on the configuration options, which have been intermixed with config options for pySAML. The way we specify how we want to sign an assertion is also messes up with the other options. Satosa should only dictate what values go to the configurations and pySAML should handle the encryptions. Ivan will roll out the small changes separately, then will later start deprecating the current options in Satosa and only use the pySAML options. Ivan will discuss this further with Johan. After the options are sorted out, will work on logging (which will also impact pySAML - want to use the same logger, using the same format, throughout the whole stack). Martin has an issue regarding creating a better, default/common template for direct user interfacing. This starts again through pySAML and how it handles exceptions; this needs to surface up to Satosa for interpretation, otherwise Satosa doesn’t actually know anything about this. Does Satosa actually need to handle the error, or can it just present a static error page? Maybe. Rainer points out that SAML has an error URL in metadata; it shouldn’t be the responsibility for a transparent proxy to engage in user interactions. Ivan suggests that the error should be in a JSON format that can be presented to something else for handling (e.g., display or redirection, etc) Instrumentation discussion: instrumentation is different than error handling; it is more like log handling. Ivan will probably define various stable things during execution (e.g., PID, statistics of system, request ID) and then provide more context as things are processed. The logging will (probably) be in JSON format. This is higher priority than error handling. If we go forward with structured logging, we have more options for monitoring the service. - pySAML (https://github.com/IdentityPython/pysaml2) PR 485 - may be able to do this in a more efficient way, but it works as is. Ivan will likely refactor in a future release. In particular, handling redirect binding request with Satosa. Other small changes around general code quality, and updates on examples to make them work with Python 3. It is a big question about moving from Python 2 to Python 3 exclusively. Python 2 will no longer be updated past 2020 (see https://pythonclock.org). Would like to reach out to other projects using pySAML; there is something in GitHub (https://github.com/IdentityPython/pysaml2/network/dependents) that would help with this, but that list needs to be cleaned up. Can there be a deprecation warning that appears during pySAML upgrades? Not sure; Ivan will follow up. Alternatively, put a warning in the install log and have the install fail, redirecting the user to another package. PR 556 and PR 548 and Issue 549 - name handling. Ivan will be going forward with this, but via a transition phase. Some changes will be made to make warnings surface. - pyFF (https://github.com/IdentityPython/pyFF) Martin opened two PRs for pyFF last week. Reloading metadata, and fixing the command line parser. Leif is still working on splitting the pyFF code to separate the discovery component from the metadata handling component. Still hoping that Leif moves away from CherryPi to flask. - Governance docs (https://github.com/IdentityPython/Governance) Had the first governance meetings. No hard decisions yet, but hopefully by the next meeting we will have decisions re: the CLA and the IPR home. Notes are in the mailing list archive (https://lists.sunet.se/pipermail/idpy-board/). 3. AOB TIIME - Rainer has reserved a room for us.

5 years, 5 months

1
0
0 0

Agenda: idpy developers call, 27 November 2018

by hlflanagan＠sphericalcowgroup.com

Date: Tuesday, 27 November 2018 Time: 14:00 UTC https://bluejeans.com/655841213 Agenda: 0. Agenda bash 1. Introductions (if needed) 2. Project review - Satosa (Satosa PRs - https://github.com/IdentityPython/SATOSA) - pySAML (https://github.com/IdentityPython/pysaml2) - pyFF (https://github.com/IdentityPython/pyFF) - Governance docs (https://github.com/IdentityPython/Governance) 3. AOB

5 years, 5 months

1
0
0 0

PySAML v4.6.4

by ivan.kanak＠gmail.com

Hi everyone, PySAML2 v4.6.4 was just released and includes the long wanted want_assertions_or_response_signed configuration option. See the changelog[0] for details on the latest changes and try it out ;) [0]: https://github.com/IdentityPython/pysaml2/releases/tag/v4.6.4 Cheers, -- Ivan c00kiemon5ter Kanakarakis >:3

5 years, 5 months

1
0
0 0

Agenda: idpy developers call, 30 October 2018

by hlflanagan＠sphericalcowgroup.com

Date: Tuesday, 30 October 2018 Time: 13:00 UTC (note time zone changes!) https://bluejeans.com/655841213 Agenda: 0. Agenda bash 1. Governance update 2. PR review - Satosa (Satosa PRs - https://github.com/IdentityPython/SATOSA) - pySAML (https://github.com/IdentityPython/pysaml2) - pyFF (https://github.com/IdentityPython/pyFF) - Governance docs (https://github.com/IdentityPython/Governance) 3. AOB

5 years, 5 months

5
5
0 0

Agenda: idpy developers call, 13 November 2018

by hlflanagan＠sphericalcowgroup.com

Date: Tuesday, 13 November 2018 Time: 14:00 UTC (back to our usual schedule) https://bluejeans.com/655841213 Agenda: 0. Agenda bash 1. Governance update 2. idpy developers meeting @ TIIME - agenda building 3. PR review - Satosa (Satosa PRs - https://github.com/IdentityPython/SATOSA) - pySAML (https://github.com/IdentityPython/pysaml2) - pyFF (https://github.com/IdentityPython/pyFF) - Governance docs (https://github.com/IdentityPython/Governance) 4. AOB

5 years, 5 months

3
2
0 0

2024

2023

2022

2021

2020

2019

2018

2017

Idpy-discuss November 2018