No 'Authorization: Bearer' header found.

[Krassmus]

Steps to reproduce

1. Have an oauth 2 access token and try to access nextcloud via webdav.
2. create a curl-request with the "Authorization: Bearer xyz" header where xyz is the access token.

Expected behaviour

I should have got access to the web dav objects

Actual behaviour

Nextcloud tells me en error message

<d:error xmlns:d="DAV:" xmlns:s="http://sabredav.org/ns">
<s:exception>Sabre\DAV\Exception\NotAuthenticated</s:exception>
<s:message>No 'Authorization: Basic' header found. Either the client didn't send one, or the server is misconfigured, No 'Authorization: Bearer' header found. Either the client didn't send one, or the server is mis-configured</s:message>
</d:error>

But it's from! I have clearly added the header with bearer token (but not basic auth).

Server configuration

Operating system:
ubuntu
Web server:
apache
Database:
mysql
PHP version:
5.5
Nextcloud version: (see Nextcloud admin page)
12
Updated from an older Nextcloud/ownCloud or fresh install:
fresh
Where did you install Nextcloud from:
manually
Signing status:

Signing status

No errors have been found.

Are you using external storage, if yes which one: local/smb/sftp/...
no
Are you using encryption: yes/no
ssl
Are you using an external user-backend, if yes which one: LDAP/ActiveDirectory/Webdav/...
no

Client configuration

Browser:
php curl
Operating system:
ubuntu

Logs

Web server error log

no log error at that time

I thought this could be related to #5372 but the fix there didn't seem to work for me.

[Krassmus]

Edit: I do get a "Login failed: 'CxiRWaDhH7ffGQLuog7dH5E8oXJyU94VexxxxxxLcSupBDwRDKRi0ey0' (Remote IP: '78.47.9.104')" log entry, when I try to receive a refresh token. Might that be the problem?

[rullzer]

@LukasReschke wasn't this some apache thing?

[Krassmus]

I actually use an apache.

[LukasReschke]

This will only work if you have mod_rewrite and mod_env enabled and available as well as allowed the .htaccess that we ship (AllowOverride All). Apache strips the Authorization: Bearer.

[LukasReschke]

As alternative just use Basic auth and use the token as user password.

[Krassmus]

Alright! That seemed to solve the problem. Maybe the admin-page for the nextcloud oauth app could throw a warning if those mods aren't enabled.

Anyway: Thank you! I wouldn't have guessed that in a million years.

[m1cka]

Hi,
@Krassmus ,
maybe you can paste/show your .htaccess?
@LukasReschke i use apache too. where need to add Header always set? in apache conf or in nextcloud .htaccess?

[havrla]

Heloo,

same problem after install package php-pear-Auth-SASL on system Centos7 with php71w and NC12.0.6

Recovery from snapshot :-), remove package no effect.

Havrla

[karankotz]

@Krassmus Can you please provide more details on how you solved this problem, I have been struggling with this since long time!

[Krassmus]

Hi @karankotz , this comment by Lukas helped me out:

This will only work if you have mod_rewrite and mod_env enabled and available as well as allowed the .htaccess that we ship (AllowOverride All). Apache strips the Authorization: Bearer.

The apache stripped away a header which I was sending. Without this header the error-reporting No 'Authorization: Bearer' header found. makes truly sense. Nextcloud can't receive the token, when it has been flushed by the webserver. So have a look at your apache config. Or do you use nginx or stuff?

[karankotz]

@Krassmus
I have followed the below steps (I am using Ubuntu):

1> Enabled the mod_env and mod_rewrite (following the steps at http://www.iasptk.com/enable-apache-mod_rewrite-ubuntu-14-04-lts)

2> Created the .htaccess at the path /var/www/html/ and added "RewriteEngine on".

Still I have the same error after restarting the apache2 service.

[Krassmus]

Does your apache have the AllowOverride All statement in the directory statement? Maybe your .htaccess file is not evaluated at all by the apache?

[karankotz]

@Krassmus
I have added the AllowOverride All for the directory settings at the path /etc/apache2/apache2.conf.

Can you please share which OAuth token(source) are you using ? How are you getting the token?

I have configured the Nextcloud with Keycloak and using the access token generated from the keycloak server for this nextcloud server which is configured as the client.