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