Onedrive Integration - Client secret getting truncated

[sachvgosavi-source]

How to use GitHub

• Please use the 👍 reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

---

When configuring the OneDrive integration in Nextcloud (running as an official app on TrueNAS SCALE), the Client Secret entered in the admin settings gets truncated or lost after saving.
As a result, OAuth authentication fails with:

OneDrive OAuth error : Client error: POST https://login.live.com/oauth20_token.srf resulted in a 400 Bad Request response:
{"error":"invalid_client","error_description":"The provided value for the 'client_secret' parameter is not valid."}

Steps to reproduce

    1.	Install official Nextcloud app on TrueNAS SCALE (24.10 or later).
2.	Go to Settings → Administration → Connected accounts → OneDrive.
3.	Enter valid values for:
       •	Client ID
       •	Client Secret (from Azure App Registration)
       •	Redirect URI correctly set to
                     https://<your-domain>/apps/integration_onedrive/oauth-redirect
4.	Click Save.
5.	Try connecting a user account or re-open the settings.

Expected behaviour

The full Client Secret value should be saved and used for OAuth token exchange.

Actual behaviour

The Client Secret gets truncated or lost after saving, leading to invalid_client OAuth errors.
In some cases, checking the config.php shows the value is partially saved or replaced by an empty string.

Server configuration

Operating system: TrueNAS SCALE 25.0.4.3 (Fangtooth)
Web server: Embedded nginx (TrueNAS Nextcloud App)
Database: PostgreSQL
PHP version: 8.2
Nextcloud version: 32.0.0.13
App version: integration_onedrive 1.0.x
Installation method: Official TrueNAS SCALE App
Reverse proxy: Cloudflare Tunnel

List of activated apps
Default apps
External Storage
Onedrive integration

If you have access to your command line run e.g.:
sudo -u www-data php occ app:list
from within your Nextcloud installation folder

Yes

Nextcloud configuration

'overwrite.cli.url' => 'https://nextcloud.gosavifamily.net', 'trusted_domains' => [ 0 => '127.0.0.1', 1 => '192.168.50.xxx', 2 => 'localhost', 3 => 'nextcloud', 4 => 'nextcloud.gosavifamily.net', ], 'dbtype' => 'pgsql', 'version' => '32.0.0.13', 'config_preset' => 2, 'preview_imaginary_url' => 'http://imaginary:9000', ``` If you have access to your command line run e.g.: sudo -u www-data php occ config:list system from within your Nextcloud installation folder ``` Yes

[oleksandr-nc]

Thank you for submitting this issue. We will investigate it as soon as our schedule allows. We welcome community contributions, and if you or anyone else would like to work on a fix, we would be happy to review a pull request.

[darkoutcast]

I'm adding this here on the off chance that this resolves the issue if the other user is still following this issue. I don't believe it is actually a bug, but instead user error, as I ran down the same issue. I don't normally use Azure and so just like others had been grabbing the wrong client id for the application id in a different issue, I believe this is a matter of grabbing the wrong field. In the attached image, the correct key for this field is the one highlighted in red, not the one to the right of it in black. I made that mistake and it yielded the same error, as clearly, the "Secret_ID" is not the "Secret" that is actually needed for OAuth. Easy mistake for hobbyists unfamiliar with Azure platform formatting to make. I certainly did.