# Collabora sends both access\_token and Authorization header to wopi backend for CheckFileInfo **URL:** \ **Category:** Uncategorized\ **Created:** [September 4, 2024, 1:19pm UTC](https://forum.collaboraonline.com/t/collabora-sends-both-access-token-and-authorization-header-to-wopi-backend-for-checkfileinfo/2944 "2024-09-04T13:19:39Z")\ **Posts on this page:** 1\ **Showing post:** 1
**Author:** ![ddscentral](https://avatars.discourse-cdn.com/v4/letter/d/d2c977/32.png) [@ddscentral](https://forum.collaboraonline.com/u/ddscentral)\ **Post date:** [September 4, 2024, 1:19pm UTC](https://forum.collaboraonline.com/t/collabora-sends-both-access-token-and-authorization-header-to-wopi-backend-for-checkfileinfo/2944/1 "2024-09-04T13:19:39Z")
Hello, During our integration of Collabora Online into our app, we have encountered a strange issue. After submitting the form with WOPISrc URL and access\_token (WOPISrc in URL, access\_token through form, just like in sample applications) to the editor URL retrieved from discovery XML, the editor fails to load, complaining it can’t read the file. From the logs, we found out that when trying to retrieve CheckFileInfo URL, Collabora sends both access\_token parameter and Authorzation: Bearer header with the same value as the access\_token to the backend server. This confuses the Spring application running in the backend since it treats both the header and the access\_token parameter as authentication tokens. Is this behavior normal ? Is there any way to disable it ? We could adapt our backend application to ignore the Authorization header (or the access\_token) but I wanted to know whether it is possible to fix without altering the code. Collabora version is 23.05.10.1 (git baa6eef) Spring application with custom WOPI backend. --- _[View the full topic](https://forum.collaboraonline.com/t/collabora-sends-both-access-token-and-authorization-header-to-wopi-backend-for-checkfileinfo/2944)._