Just a minor correction to the state of affairs:
The CMService PR is backwards compatible, it only introduces a new request
type POST, but still supports original GET. The Satosa PR otoh breaks consent
if CMservice isn't updated as well.
So: CMservice PR is safe, Satosa PR needs CMservice PR.
Best regards,
Martin
On Tuesday, May 15, 2018 3:18:29 PM CEST Heather Flanagan wrote:
Attendees: Martin, Heather
No word from Ivan, so not sure about the status of today’s call
https://github.com/IdentityPython/satosa_microservices/pull/11
Martin made a minor pull request around consent service (microservice). To
really fix the problem Satosa has to be changed to accept HTTPS POST
requests. Not sure if/how this is handled by idpy.
If you update this microservice without Satosa being changed, then Satosa
will break. This is not a backwards compatible change.
Any issues with the template for the PR? It was a bit heavier weight than
was necessary for such a small change, a bug fix. This was also already
fixed in SURF’s own branch, so they’ve already got it running.
Sent from my iPad