Andrew Hodgkinson
Andrew Hodgkinson
@juliaducey Sorry for the delay here. Just as I was getting around to this some very valid points came up in #33 and I was thinking that this might all...
OK, merged, but due to logistics issues on our side, this is going to have to be in a V3 with rename for Entra. Totally understand if you prefer to...
So, sorry about that, hopefully V3 on release will be easy for you to use; either way, _thank you_ for the great submission.
@tom-brouwer-bex Thanks for the report and the details, including links. Sorry for the slow response here. Certainly can't see a way to fix this in a backwards-compatible way, so I...
@tom-brouwer-bex Well... * On the one hand, renaming can create big problems for migration - e.g. in our own database we store the name of the auth provider with which...
OK, so I think I can close this now - believed fixed by http://rubygems.org/gems/omniauth-entra-id. See [UPGRADING.md](https://github.com/RIPAGlobal/omniauth-entra-id/blob/master/UPGRADING.md) for migration.
Fixed by #40 - thanks!
As an additional note, should it be useful, we can fork the gem, revert any changes that might be suspected of causing the problem and run CI on a branch...
@route We've had two full successful CI runs on Cuprite 0.15.1 / Ferrum 0.15.0 using `flatten: false`. I'm re-running a couple more (since the failure rate wasn't 100% beforehand so...
Four passes now, so I'm confident that `flatten: true` makes our CI crash while `flatten: false` resolves the problem.