Mismatch when deploying nginx-uwsgi about fedservice HOT 4 CLOSED

Just back from a funeral so give me a day or so and I'll get back to you.

from fedservice.

Oops, sorry! sad to hear so :-(
Thanks!

from fedservice.

Sorry about not getting back to you sooner.
The funeral and all the things surrounding it affected me more than I thought it would.

Anyway, back to business.
As a background I've never had to run a service using nginx-uwsgi so I've never felt comfortable using that setup.
I only made it available since I had users that pestered me about providing it.
During my only usage of the library, the interoperability testing, it wasn't really needed since the traffic was very low and not time critical in any way.
So, I reverted back to running the scripts from the command line and not through nginx-uwsgi. As you pointed out leading to changes in the scripts that was not reflected back into the nginx-uwsgi setup. I should be able to go back and correct the dependencies and usages of the APIs. But don't look to me to get support for the setup as such since I'm way out of my depth on nginx-uwsgi.

The fedservice implementation are always going to be of the latest (unpublished) version OIDC federation specification.
The one you can find at https://github.com/rohe/fedservice.

Having said that, right now I have a small set of modifications to JWTConnect-Python libraries that I have to turn into releases before I can point you to an up-to-date stable version.

from fedservice.

Ok, thanks, i will use the command-line scripts for now, till you point me to a stable up to date version. Thanks again !

from fedservice.