Google Drive and One Drive auth tokens
Seems there are issues with accessing files on Google Drive and Microsoft One Drive, see
for the details. The solution seems to be both a technical and an administrative one.
We likely need accounts with both of the services and then file some paperwork.
Cloph, can you let us know where we have official accounts?
I think only at Google (the info@tdf one?), but I am not sure.
Xisco, with the account information at hand, can you chase what we have to do, prepare the technical bits and hand back to me for the paperwork?
Updated by Christian Lohmaier 4 months ago
For microsoft onedrive the reason is not bad auth-tokens, but using obsolete (and now disabled, non-fuctional) API.
Migration seems straightforward enough that I can handle, but requires changes to both libcmis (that deals with the filebrowsing aspect) as well as LibreOffice (that defines the ouath enpoints/scopes to use)
Only "issue" with the API-keys uses is that it's called "LibreOfficeDev" in the dialog to confirm the requested access to onedrive files, so changed the name and at the same time added the magic to have the domain verified using https://www.documentfoundation.org/.well-known/microsoft-identity-association.json
Also with the "open the link in the browser and copy the result back to the connect-to-server window" there really is no need to ask the user for the username/password for the onedrive account, LO cannot make use of it to login anymore.
Updated by Christian Lohmaier about 1 month ago
- File onedrive_wip.png onedrive_wip.png added
- Status changed from New to In Progress
- % Done changed from 0 to 40
wip - unfortunately not as strightforward/minimal changes as hoped, nevertheless basic functionality working again for onedrive. Opening/Saving files should be ready in time for rc1.