bug#44195: EXCORPORATE: android/termux/emacs - "error in process filter: wrong authorization "

[Jeffrey Haug]

Thomas - thank you for all of your help, ideas, and support to diagnose the problem.

Current workaround:

https://debbugs.gnu.org/cgi/bugreport.cgi?bug=44439

After changing from "error" to "message" - I can authenticate to exchange successfully!

Issue root cause explanation:

https://debbugs.gnu.org/cgi/bugreport.cgi?bug=43566

Thanks,

Jeff

On Tue, 27 Oct 2020, 5:01 am Thomas Fitzsimmons, <fitzsim@fitzsim.org> wrote:

Hi Jeffrey,

Thanks for reporting.

Jeffrey Haug <jthaug@gmail.com> writes:

> Setup
>
> termux-info
> Packages CPU architecture:
> aarch64
> Subscribed repositories:
> # sources.list
> deb https://termux.mentality.rip/termux-packages-24/ stable main
> # game-repo (sources.list.d/game.list)
> deb https://dl.bintray.com/grimler/game-packages-24 games stable
> # science-repo (sources.list.d/science.list)
> deb https://dl.bintray.com/grimler/science-packages-24 science stable
> Updatable packages:
> All packages up to date
> Android version:
> 10
> Kernel build information:
> Linux localhost 4.14.113-19542039 #1 SMP PREEMPT Fri Aug 28 18:36:13 KST 2020 aarch64 Android
> Device manufacturer:
> samsung
> Device model:
> SM-N975F
>
> emacs 27.1
> excorporate-0.9.1
> fsm-0.2.1
> soap-client-3.2.0
> url-http-ntlm-2.0.4
>
> Issue
>
> autodiscover works great
> after entering username & password
> I get the following error:
>
> error in process filter: Wrong authorization used for https:// *url remove*
>
> I have verified my username & password several times. I can follow the
> exact steps on my other windows 10 emacs setup and connect
> successfully.
>
> Can you help me debug?

Sure.  On the aarch64 machine can you try the steps in the
Troubleshooting section of the Excorporate manual?

C-h i d m exco RET 5

You can compare the results of doing the same steps on your working
setup.  See if you can see any differences in how the authentication is
working, like what authentication types the server is offering via
WWW-Authenticate headers and which one Emacs is choosing in
Authorization headers.

Thanks,
Thomas