Has anyone succeeded in using discourse as sso provider for nextcloud? Share recipe?

[paroga (Patrick Gansterer)]

@tobiaseigen

I am struggling to figure out where to talk about this app with the developers.

I’d suggest GitHub.

@tobiaseigen

New users created in nextcloud get an automatically generated username in the form [internal name]-[userid] so in the case of my site e.g. kb2-3797 .

IMHO that’s the best way to implement it, since the id is used primarily internal and not visible in many places to normal users.
Nextcloud has no easy way to rename users, but Discourse has. Renaming a user in Discourse could lead to some strange behavior with Nextcloud if the names don’t match any more.

@tobiaseigen

The name is carried over, but other profile details have to be fileld in again in nextcloud. Avatar is also not carried over.

The avatar_url from DiscourseConnect should get passed to Nextcloud and read there. If you want to pass the bio too, a few lines in in the branch responsible for the profile updates should do the job.

@tobiaseigen

I am also kind of wondering how the user will set up their username and password for the desktop or mobile client

You should use device passwords instead. The Nextcloud password could be different from the Discourse password, which would lead to confusion and skips the SSO.

@tobiaseigen

there are three sections in the admin settings for the app

I think these are general issues with the Nextcloud UI and not app specific.

@tobiaseigen

hide default login = encourages users to login via discourse though still possible to log in directly with the nextcloud username/email and password.

Set the social_login_auto_redirect option to true as described in the config section if you want hide the Nextcloud login completely.