NextCloud sync incompatible with SSO

I didn't find this elsewhere, please point me in the right direction if I just searched for the wrong things.

I just downloaded the Joplin iOS app and tried to setup sync with NextCloud. Unfortunately, rather than asking me for my NextCloud's domain and sending me through the oauth flow like other NextCloud integrations, the app wants me to store my NextCloud username and password in it. This is presents a problem as our NextCloud uses single sign on for account management, so using NextCloud's default login method will not work.

Is there any chance of getting a proper NextCloud auth flow in Joplin? It looks like a nifty app and I'd love to use it, but this makes it unusable for me.

I asked about this a while back. See details on loginflow at

Or documentation for loginflow on webui and desktop clients at:

1 Like

Does the method detailed here (Improve security of the Nextcloud link) help you in any way?

That is an interesting read! Haven't seen someone use federation and share links in that way.

Actually you can find your webdav address in the bottom left of the Nextcloud webui when viewing the Files app, under "settings" button. It should work fine.

Thanks, this is what I was looking for. I didn't know the name for it.

Ah yes, this mentions how to get one time passwords, that seems to do it.

Locating the webdav URL was not the issue. Although it would be nice if Joplin made it clear it was going to dump a bunch of files in whatever folder I passed it, and not make it's own folder like most sync-via-nextcloud apps do. I ended up with a bunch of crap in my nextcloud home folder because of this

I feel the documentation was extremely clear on the matter:

In the desktop application or mobile application, go to the Configuration screen and select Nextcloud as the synchronisation target. Then input the WebDAV URL (to get it, click on Settings in the bottom left corner of the page, in Nextcloud), this is normally (make sure to create the "Joplin" directory in Nextcloud), and set the username and password. If it does not work, please see this explanation for more details.

1 Like

i suppose if i had known to check the documentation first I might have found that, but I didn't see any need to do so as I didn't encounter anything that didn't appear to be self-explanatory.