Hi,
I would like to hear opinions about (rejected) Satosa PR #237. Can we put this on the agenda?
Today I can talk only the first 20 minutes and will switch to listening only afterwards.
Cheers, Rainer
> Anfang der weitergeleiteten Nachricht:
>
> Von: Rainer Hoerbe <rainer at hoerbe.at>
> Betreff: Granular Logging control
> Datum: 14. Juli 2019 um 22:04:55 MESZ
> An: satosa-dev at lists.sunet.se
> Kopie: Ivan Kanakarakis <ivan.kanak at gmail.com>
>
> If would like to discuss a logging feature that I would like to see in Satosa. I proposed with PR 237 to add a log filter that would enhance satosa's logging capabilities. Ivan rejected it for the (in general good) reason that the proxy should log everything and log processing should be external.
>
> I agree in general, but there are bits where I still think that they would be useful in satosa. These are:
>
> 1. In production environments it is unlikely to push the full set of debug information to a logging service. However, it might be useful to get debug level data on certain selections. Usually that would be based in IP addresses, which should not be too complicated to implement.
> 2. In a dev environment one is easily inundated with debug data. Shibboleth has a nice feature providing logging levels for certain aspects, such as XML tooling, SAMl message de-/encoding. I find this capability quite useful, because in my dev environment I do not have an elaborate log processor. Attribute configuration in satosa could be helped by selected messages.
>
>
> If done properly, this change has following impact on all modules that instantiate a logger:
> 1. refactor the satosa_logger wrapper back to the native logger with similar signature
> 2. add a log filter after each get_logger()
>
> The logfilter (logging.Filter) is orthogonal to structured logging, or may even help to improve it.
>
> see: https://github.com/IdentityPython/SATOSA/pull/237 <https://github.com/IdentityPython/SATOSA/pull/237>
>
> Cheers, Rainer
Hola a todos!
We have a call on the calendar for tomorrow, 9 July 2019. This will likely be a fairly informal call.
I will be unable to attend, but I strongly encourage those of you who can make it to talk about Satosa/pySAML2 items, and to talk about what to do at the upcoming Hackathon (https://wiki.refeds.org/x/AwauAg)
Thanks! Heather
Hi everybody,
I'm happy to announce the first release candidate of a new OpenSource
Identity Provider called uniAuth, built on top of pySAML2 and Django
Framework.
https://github.com/UniversitaDellaCalabria/uniAuthhttps://uniauth.readthedocs.io/en/latest/index.html
First of all I want to thanks Identity Python initiative, for giving us the
tools to build something useful, with adequate adherence to standards.
I had a lot of fun in developing it, now it's time to share and to fill up
curiosity topics about any usage or implementation questions if they come,
thanks a lot and hear you back soon
____________________
Dott. Giuseppe De Marco
CENTRO ICT DI ATENEO
University of Calabria
87036 Rende (CS) - Italy
Phone: +39 0984 496945
e-mail: giuseppe.demarco at unical.it
--
------------------------------------------------------------------------------------------------------------------
Il banner è generato automaticamente dal servizio di posta elettronica
dell'Università della Calabria
<http://www.unical.it/5x1000>
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
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)
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
