Conversation
|
Gave it a quick shot and I was able to go through the whole flow including duo push and get logged in. Unfortunately that's all I'll be able to get to today. That said, there is an error in JSON decoding (that ends up getting ignored) that i have not looked into other than to see that it's happening in the try/except you added: Again, it ultimately lets me in with a push even with the above error. |
|
I get the same error - initially I thought it happened because I used the wrong response for it. Since I can reproduce with our setup as well - I can try to debug this. It would be nice if we could get the trace (run with debug logging) of the http request just before this error happens. Would be interesting to see the comparison between our two environments. - I think the error happening does mean, that it should work for your setup even if nothing is done with the response from this callback. I'll try to add a few command line switches or sth. to let us experiment with different procedures without requiring code changes every time. Thanks for taking the time to test this. |
|
Sure, np. You just looking for the block starting with something like |
|
That would be sufficient. I tried to reproduce the issue somewhat and improve logging but could not reproduce this anymore. I'd be looking for this part specifically, to understand why the response is not parsable as json "sometimes": |
|
Here you go |
|
Thanks for the confirmation. Seems in your case, the callback returns a webpage instead of json. Anyhow, if this works for both our setups, it's time to start discussion with maintainers if any of this approach can be accepted. It would be quite awesome to have a few "supported" setups of AD FS + other services in some test environment, but I guess the cost and effort to maintain a windows environment + bunch of other SaaS is beyond what most could contribute. |
|
Pulled and seems to be working here. I'll get another tester onboard, but expect the same results. |
Co-authored-by: Patrick Decat <pdecat@gmail.com>
Use raw string for regex.
|
Ok to merge and release this when you are ready. |
|
For me it looks good, then our users can install the latest version again. |
In #440 / #441 a callback was introduced. Using the response of the callback causes issues for our setup.
This MR is an attempt to debug the situation and hopefully finding a way that works for @thecaffiend as well as our setup.