Re: Sending HTTP 401 Unauthorized header response

Michael J Rubinsky <[email protected]> Fri, 04 Jan 2019 20:44:42 +0000

Newsgroups	gmane.comp.horde.user
Message-ID	<20190104204442.Horde.KJs_6OlSPeN9De_wB9fDO2c@tarn.theupstairsroom.com>

Quoting Arjen de Korte <[email protected]>:

> Citeren Arjen de Korte <[email protected]>:
>
>> Possibly more log spam:
>>
>> 2019-01-04T13:23:44+01:00 ERR: horde Sending HTTP 401 Unauthorized  
>> header response. [pid 1949 on line 126 of  
>> "/usr/share/php7/PEAR/Horde/Rpc/ActiveSync.php"]
>>
>> Dumping $serverVars just a few lines before this line, it looks  
>> like the client attempts to authenticate with type "Bearer" but  
>> there is no token. I also see requests where the same client is  
>> using Basic authentication with a base64 encoded username and  
>> password, which works fine. The client in question is the built-in  
>> Windows 10 Mail and synchronizes as usual.
>>
>> I've removed the account and recreated it, but the problem remains.
>
> It occurs with multiple accounts, all using the Windows 10 Mail  
> client. When logging the $serverVars['HTTP_AUTHORIZATION'] variable,  
> they seem to come in pairs:
>
>     2019-01-04T19:24:10+01:00 DEBUG: Variable information:
>     string(50) "Basic XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX=="
>
>     Backtrace:
>     1. Horde_Rpc_ActiveSync->getResponse() /srv/www/htdocs/horde/rpc.php:160
>     2. Horde::debug() /usr/share/php7/PEAR/Horde/Rpc/ActiveSync.php:120
>
>     2019-01-04T19:24:26+01:00 DEBUG: Variable information:
>     string(6) "Bearer"
>
>     Backtrace:
>     1. Horde_Rpc_ActiveSync->getResponse() /srv/www/htdocs/horde/rpc.php:160
>     2. Horde::debug() /usr/share/php7/PEAR/Horde/Rpc/ActiveSync.php:120
>
> Could it somehow be that no token is sent from the server to the  
> client? Can I somehow log the token?

I sent a response to your first report that I'm guessing got lost  
somewhere along the way. Essentially:

We don't support Bearer token authentication, so this is normal  
behavior. The server rejects the authentication and the client falls  
back to username/password. We can probably lower the log entry to a  
DEBUG level.

Thanks for the report, though.



>
> -- 
> Horde mailing list
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: [email protected]



-- 
mike
The Horde Project
http://www.horde.org
https://www.facebook.com/hordeproject
https://www.twitter.com/hordeproject

-- 
Horde mailing list
Frequently Asked Questions: http://horde.org/faq/
To unsubscribe, mail: [email protected]

(unnamed) (application/pgp-keys, 9.1 KB) - not displayed

signature.asc (application/pgp-signature, 821 B)