Thanks, Patrick! I installed the app now again and see the “Custom Discourse” option. It’s not yet explained in the documentation which is why I thought nothing had changed. Also on the https://apps.nextcloud.com/apps/sociallogin page there is a link to a broken link on the nextcloud support forum, so I am struggling to figure out where to talk about this app with the developers.
I have it working now, but the biggest problem I am having is that I cannot figure out how to enable this to be the only method for logging in for all existing users by default.
Second biggest problem is that the user details are not carrying over correctly from discourse to nextcloud. 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. The name is carried over, but other profile details have to be fileld in again in nextcloud. Avatar is also not carried over.
I am also kind of wondering how the user will set up their username and password for the desktop or mobile client, when this is the only login method for the nextcloud web app. I guess they will have to know to go into their account prefs in the nextcloud web app to setup nextcloud login credentials.
Some other things I noticed:
- app settings are not reached via the
appssection but via the administration settings sidebar. took me a minute to find.
- there are three sections in the admin settings for the app, and the top and bottom sections have save buttons but the middle one (for custom providers) does not. It’s not clear which one to use to save custom discourse settings. Answer: they both work the same way.
- there are many app settings. these appear to work best for my setup:
disable auto create new users= allows new users to be created in nextcloud if they exist in discoursecreate users with disabled account= do not disable newly created usersallow users to connect social logins with their account= lets existing users opt in to logging in via discourse (
not able to figure out how to default to allowing users to log in via discourse)update user profile every login= syncs discourse groups with nextcloud groups each time they log in. (
does not correctly sync username, name, bio and other profile info)do not prune not available user groups on login(
I don’t know what this does but enabled by default. I suspect it prevents removing the user from existing nextcloud groups if they are not mapped from discourse?)automatically create groups if they do not exist= disabled because creates some fugly group names that replicate groups you do want (see below)restrict login for users without mapped groups= disabledrestict login for users without assigned groups= disableddisable notify admins about new users= disabled because helpful for me to see when new nextcloud users are createdhide default login= encourages users to login via discourse though still possible to log in directly with the nextcloud username/email and password.
- I lost admin access immediately the first time I tried it, before creating group mappings. To get it back, I had to go to the command line and run
occ group:adduser admin USERNAME - group mapping works super well! Most important was to add the mapping of
admins→ nextcloudadminso that admins in my forum have admin privs in nextcloud. I also was able to add mappings for groups used for secure categories, to also give access to secure folders in nextcloud related to those secure categories.
Inching ever closer!
