8:10 a.m.
Wrongly sent only to Christos.
Begin forwarded message:
From: Roland Hedberg <roland(a)catalogix.se>
Subject: Re: [Idpy-board] satosa - oidc
Date: 24 October 2022 at 15:20:06 CEST
To: Christos Kanellopoulos <christos.kanellopoulos(a)geant.org>
Christos,
It goes without saying that I’d prefer us to use the eduTEAMS implementation.
Given the effort you have put into it, it’s at the top of the list.
But, we need it to be public.
I’d prefer that you would just publish what you have and we can go from there.
That you have a private branch where your higher demands on software quality is met is
not a problem to me.
If you plan to wait until idpy-oidc has stopped changing then you will have to wait
forever. Or at least until I stop being
responsible for the package.
There is always going to be new RFCs, Internet drafts, OIDF standards and industry
specifications that we want/need to support
if we want to be noteworthy. And that forces us to add/rewrite/refactor idpy-oidc.
I try to keep people informed about such changes at the bi-weekly idpy meetings.
The standards I’m working on right now are CIBA and OIDC Federation. Both of which demand
some basic changes..
Please send me an invite to your Thursday call and let's go from there.
24 okt. 2022 kl. 14:56 skrev Christos
Kanellopoulos <christos.kanellopoulos(a)geant.org>:
Hello Roland,
Of course, we do not have to use the eduTEAMS implementation. Having said this, once
again we are hindered by the the changes in the underlying libraries. In September the
development team has migrated the frontend to the new OP library, but our testing has
showing that the new implementation is not stable for production use. At this point we are
not sure whether it is a problem in the OP libary or the way it was integrated. I believe
we will have more information on Thursday about this. Perhaps Ivan can say more about
this.
We have already given access to a number of people in the private repository, but we have
not seen any contributions yet. I would be happy to add you and/or other trusted people in
the private repository and also invite you in our Thursday call if you have the time to
help in realising a stable version that we can open source.
Christos
On 24 Oct 2022, at 14:34, Roland Hedberg wrote:
Sorry for the confusion! I meant satosa-pyoidc
not satosa-oidcop.
24 okt. 2022 kl. 10:23 skrev Roland Hedberg
<roland(a)catalogix.se>:
Hi!
This situation with EduTEAMs not releasing their satosa-idpy-oidc integration is really
hurting IdPy.
I think we should give up on EduTEAMs and instead bring in Giuseppe’s implementation.
As long as we keep satosa-oidcop on line as the ‘official’ IdPy SATOSA-OIDC package we
loose a lot of
help in making our own OIDC implementation better.
— Roland
_______________________________________________
Idpy-board mailing list -- idpy-board(a)lists.sunet.se
To unsubscribe send an email to idpy-board-leave(a)lists.sunet.se