-
Notifications
You must be signed in to change notification settings - Fork 808
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
App token login name does not match
#6783
Comments
Additional debug data from macOS Desktop client - "Settings/Virtual file sync/Advanced/Create debug archive" Not providing enumerator for container with identifier NSFileProviderWorkingSetContainerItemIdentifier yet as account not set up |
Hi @stfast could you also send us the normal debug archive for the desktop client? Thanks! |
Actually they are one post above. Here is archive file. |
Guys, after all VFS PR with HUB 8, this is embarrassing, still not working ... |
Hello @stfast I am sorry I haven't had the time to fix this yet, I am patching the virtual files module as quickly as I can Your log files say your username is Thanks for providing information |
Yes, this is LDAP user ID from LDAP backend as stated on your questionary on the top of this issue, and everything is correct, since normal macOS desktop sync does work, but not VFS one, all latest NC server 29.0.4 and desktop client 3.13.2git (build 24287). |
Anything? Nextcloud 30 approaching and still not fixed. |
App token login name does not match
Can you elaborate a bit on how you're authentication from the VFS version of the client? I have a feeling this is specific to LDAP or an interaction with LDAP and the Login flow or app tokens. Refs:
Though I've no idea at the moment why you'd only encounter it with VFS mode. Is your non-VFS client (that doesn't have this problem) configured exactly the same in terms of authentication? And is it against the same Nextcloud server? |
I have the same error. |
Same here. I also tried with an app password but got identical results. |
Upgraded to Nextcloud 30, now changed error mesaages in debug archive: Sending extension account ID [email protected] |
I ran into the same issue just a couple of days ago. Took me a while to find this issue here. I am using LDAP as user backend and my username is a generated uuid. To fix this issue, I stopped my nextcloud, dumped the database, replaced the UUID with my email address in the dump, imported the dump back to my database, started the nextcloud server again and linked the nextcloud client and everything was working. I only took this approach because this is my personal instance and I have backups of everything. so before anyone takes this road, I cannot stress enough the fact, make backups(!) , test the backups before, and only if everything works, you could think of trying my approach. due to the change of the username, you most probably need to reconnect any DAV related connections. so be very careful!!!! |
Thanks for sharing your knowledge. So since UUID is the default settings for NC internal username you can ask yourself why this issue is unresolved for 1/2 of the year, and could be resolved with these LDAP Expert settings: |
Thanks for pointing this out, I forgot to mention that I changed the Internal Username Attribute before dumping my db and making any changes to my instance. Future usernames will be using the mail attribute from my LDAP as username. |
Great, server side errors for "App token login name does not match" have disappeared, still, VFS macOS desktop sync does work for LDAP users with default LDAP UUID Internal Username, which is default LDAP behavior with only Expert LDAP option to override it for new users. Now we have latest 3.14.3 macOS VFS client and Nextcloud 30.0.1 server. As you see from desktop client debug archive, user is authenticated, but client's server URL (serverUrl) shoud be with UUID (default Internal Username) https://nc.domain.com/remote.php/dav/files/FDD17349-A32D-4411-8E0E-A71BAA44509F and not with username (LDAP userPrincipalName in our case) https://nc.domain.com/remote.php/dav/files/[email protected] I have checked WebDav and it works only with UUID as WebDAV USERNAME and pointed in "Files/Files settings" WebDav URL: This is from attached desktop client debug archive: Not fetching item for identifier: NSFileProviderRootContainerItemIdentifier Actually reexporting database with replaced UUIDs for "usernames" is not an option for lots of users in 23 database tables: $ cd /var/lib/mysql/nextcloud/ |
@stfast thanks for posting this, I realised this a few days ago too (opened claucambra/NextcloudFileProviderKit#24 which fixes this) |
OK, now with Nextcloud Desktop version 3.15.0, LDAP login is working and server and client errors are gone. But how is this supposed to work? On first sync "Virtual file sync" does not get to synced status. When you quit and than start Nextcloud Desktop client again, than suddenly it is "All Synced": Folder with Sync Connection have 5.9 Gb of data even if you quit Nextcloud Desktop client: $ du -sh . and there is none files to evict If we summarize, macOS "Virtual file sync" still not working. |
OK, I dug it deeper and found macOS VFS location on this kind of a path: $ open ~/Library/CloudStorage/Nextcloud-user@[email protected]/ If you quit Nextcloud.app and start it back, Nextcloud folder from Locations in Finder dissapears. You have to be kind of an expert yourself to put this path back to the Finder, since ~/Library/* folder is hidden by default. There should be some configuration for VFS mount path as it is "Folder Sync Connection" for classic sync. |
Bug description
MacOS VFS not working
Steps to reproduce
Expected behavior
MacOS VFS sync should work.
Which files are affected by this bug
All files
Operating system
Mac OS
Which version of the operating system you are running.
macOS Sonoma
Package
Appimage
Nextcloud Server version
29.0.1
Nextcloud Desktop Client version
3.13.0git (build 22493)
Is this bug present after an update or on a fresh install?
Updated from a minor version (ex. 3.4.2 to 3.4.4)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
Are you using an external user-backend?
Nextcloud Server logs
Additional info
The text was updated successfully, but these errors were encountered: