Christian Meyer
Christian Meyer
duplicate of #790
this might fix among others, issues #689 , #662 , #645 , #624 , #573 , ...
As it might be a bit hard to follow the thought process behind the refactoring, I've reiterated the changes and created a separate branch to illustrate the way of this...
> I tried your v2.34.0-patch.1. I no longer receive the error I was getting but now receive: invalid character 'h' looking for beginning of value @theemethod would you be able...
> @christianmeyer Sure. I'm using Windows 10. You can ignore the cache errors. I was trying to figure out how to get the raw output that is failing. Not sure...
> Thanks for the update. Unfortunately, the error output seems to be the same. This is a new testing tenant so there are no CA policies and MFA is disabled....
Given the exceptions introduced as part of this discussions, I've refactored the code again, to isolate them in the thought to be somehow linear authentication flow. The AzureAD authentication flow...
Just out of curiosity, is that issue also persisting with the version out of #795 ? In that case I would adopt the referenced fix.
@jiragrid check the patched version #795, if that works better for you. We used to hand in tenant id with other adoptions, but could leave it out with this version,...
@jczerepak can you check the fix from #795 ?