Unfortunately, I received no further replies and, due to limitations, was unable to provide any further screenshots, etc.
I have since discovered under which conditions the login fails. This might be helpful for troubleshooting.
The error does NOT occur when trying to log in to a local Nextcloud account in the app.
The error occurs when trying to log in to the app using a Samba Active Directory (Nextcloud LDAP plugin) account. This is where the problem lies, and the error can only be reproduced via LDAP login.
I’m not a programmer, but I strongly suspect that the app code uses the username entered during login to derive the path of the user attempting to log in. However, LDAP accounts in Nextcloud don’t use login names as folder names, but rather the respective long-digit user ID. Therefore, the login fails.
It would be great if someone could take a look at this or at least access it. Thank you!
It doesn’t seem to be the path alone. As a test, I created a soft link (username) that points to the actual user folder (user ID). This changes the error message on the second login attempt to “Status Token Mismatch.”
I don’t know if this is relevant, but I assume the problem is somehow due to the discrepancy between the login name and user ID – which should be reflected not only in the folder structure but also in the database.
The error occurs when trying to log in to the app using a Samba Active Directory (Nextcloud LDAP plugin) account. This is where the problem lies, and the error can only be reproduced via LDAP login.
How about the Nextcloud mobile app itself? https://apps.apple.com/us/app/nextcloud/id1125420102
Please confirm that you’re able to log in with the same scenario.
Also, I believe we need a test account to your portal to check the situation on the spot, please contact me via PM.
P.S. Please do not create new topics on the same issue.
The answer via PM seems a bit suspect to me, so I’d rather reply here. I don’t want to create multiple Topics, but due to the limited number of replies and content, this was unfortunately unavoidable. How can we exchange ideas and collaborate here if we’re not allowed to communicate?
Logging in AD or LDAP users has worked perfectly so far in all iOS apps* we use - except for the OnlyOffice app.
The problem with the OnlyOffice.app and AD connection seems to be a general issue, as it occurs in completely different environments. These use Nextcloud versions 29 up to the latest version (so that’s not the problem either), only the connected AD or LDAP backends are each SambaADs (different environments).
Unfortunately, I can’t grant access to one of these ADs, I’m sorry.
But perhaps – if one doesn’t already exist – it would be a good opportunity for the developers to consider setting up a corresponding test setup with a connected Samba AD.
Does the OnlyOffice.app work with other Nextcloud installations that include a connected Samba AD?
Dear @Yummiweb
I suggested communication via PM in case you’re sharing account credentials for your Nextcloud portal. We need the test account to be able to check out the situation on the spot.
To sum it up: the issue persists in the mobile app only when using Samba AD on the Nextcloud side. Please confirm that authorization via web-browser is OK.
Also, please reproduce the issue one more time and provide us with app logs files. You can collect them with following steps:
Go to the Settings > About page > quickly tap on our logo several times > wait for the device to emit a characteristic vibration > go back to Settings menu > you will see a new Console option appear > go to Logs tab and check the latest logs.
Thank you for the logs @Yummiweb !
We are checking the situation.
Meanwhile, please clarify if it is possible to create a test account on your Nextcloud portal/Samba AD. This way, we will be able to check the issue on the spot.
Hi Everyone,
I would also like to confirm this bug. We have all of our users with AD/LDAP authentication and the Onlyoffice app will not allow you to sign in using AD credentials, which for an enterprise product, is a huge problem.
I created a Nextcloud local account and repeated the login process and bingo, worked first time as expected.
I’m happy to provide any logs or do any testing to get this fixed ASAP.
Cheers
Hello @AlanH
We need iOS app logs once the situation is reproduced: Go to the Settings > About page > quickly tap on our logo several times > wait for the device to emit a characteristic vibration > go back to Settings menu > you will see a new Console option appear > go to Logs tab and check the latest logs.
Also we need video demonstration of the issue, and a test account as well. This way we will be able to check the issue on the spot.
Additionally, please let us know ONLYOFFICE Documents and Nextcloud versions, and specify the exact AD/LDAP provider.
Please provide more details; perhaps this will help with troubleshooting or further development. I’d especially appreciate the type and version of your AD provider (SAMBA) to clarify that my four (!) installations (all of which have the same issue) are not isolated cases. Perhaps then the developers will take the error message seriously…
Dear @Yummiweb
I do understand your concerns, but we need the requested logs to troubleshoot the situation properly. If you portal has unrestricted access to Internet, we will need a test account as well to be able to reproduce the issue on the spot.
Hi Alexandre,
I have the same issue in my company. I’m going to check if IT can create a test account.
Where can I send the logs, I don’t see the direct message option…
Cheers