Nextcloud OIDC integration

[firmansi]

@girish I don't really get it, from the first time I set the Nextcloud, user management with Cloudron instead of the app, so when I add new user then it will have access to to Cloudron automatically.

Well, it;s true, What I see when I click Access Control is Dashboard Visibility. Now I set the app visible only to several groups.

[jdaviescoates]

@girish Ah yes, I found it in /settings/admin/user_oidc thanks

[nebulon]

@firmansi I don't think I understand what you are trying to tell us. Is the app installed with or without Cloudron usermanagement? Note that if it is installed without then the access controls become the dashboard visibility settings!

[firmansi]

@nebulon I think it's without Cloudron User Management because What i see now is only Dashboard Visibility Setting, why I seem confused, because I have been using this Nextcloud in Cloudron for the last 1,5 years, and all this time I never create new user in Nextcloud directly, but always with Cloudron Users with LDAP

[nebulon]

Yeah something is inconsistent then. You can just verify the LDAP extension settings as an admin within Nextcloud to see what is happening.

[firmansi]

@nebulon What do you mean to verify the LADP extension to see what is happening? Everything works just fine with the LDAP so far

[nebulon]

I meant to check if your Nextcloud is actually using Cloudron usermanagement or not, since your statements are contradicting between LDAP and dashboard visibility. You can also run env | grep LDAP in the webterminal into that nextcloud app instance. If you see LDAP related environment variables, it means you are using Cloudron usermanagement.

[firmansi]

@nebulon i've checked with ENV | grep LDAP, and no Cloudron User Management. How can i possible switch to Nextcloud with User Management?

[nebulon]

This is only an installation choice, so if you have installed it without, you would have to install a fresh Nextcloud and import the data for each user. You can also try importing the current app's backup into a new installation with the import app backup feature (in the Backups view).

[firmansi]

@nebulon thanks for the advice

[firmansi]

Just for input, there might be some like me using Nextcloud in cloudron who don't use Cloudron User Management from the beginning, I think for the next update, still give space to those like mine because last time I did the latest update, I can't login with user credential set up in User Directory Cloudron, only with admin credential

[firmansi]

@nebulon By the way I have tried with new fresh installation, but always said Could not update the provider: The discovery endpoint is not reachable.
in Nextcloud. My current cofiguration for User Directory is with LDAP Server activated already

[nebulon]

If the app is installed without Cloudron usermanagement, and update will not touch upon the authentication settings, so there is no change for those, the package code simply does not change anything related to users in such a case. So I can't imagine how this has affected your instance.

Also I can't quite make out what you mean with LDAP Server activated already in this context. On Cloudron the LDAP server is always active for apps, but not every app will be setup to use it.

[joseph]

@firmansi said in Nextcloud OIDC integration:

My current cofiguration for User Directory is with LDAP Server activated already

Note: This LDAP server is for apps external to Cloudron. This is not needed to be enabled for apps installed in Cloudron itself.

[firmansi]

@nebulon Thanks for the info, but I also set up in the same Cloudron server, fresh Nexcloud Installation, but I experience error connecting to openID with message "Could not update the provider: The discovery endpoint is not reachable.
in Nextcloud" , please let me know what i need to check in the Cloudron regarding to that error message

[jdaviescoates]

@firmansi @andreasdueren has also hit that issue, see https://forum.cloudron.io/post/100656

Works fine for me. Are you using Cloudflare, or on a home network or something?

[firmansi]

@jdaviescoates No,I use AWS, and I am aware about proxy thing, as I point out that I already use this Cloudron as central user directory LDAP server for other servers outside my Cloudron

I take a look the discussion, and it seems it does not resolve

[jdaviescoates]

PS it would've been nice if when adding this you'd also updated the manifest to use the branding on the button too

Like e.g. you've already done on e.g. PeerTube:

[joseph]

@firmansi Wanted to extend my invitation in the other thread to you too. If you can reach out to support@cloudron.io and we can debug your install as to why we get this error, it will be great.

[girish]

@jdaviescoates the plugin doesn't support setting the button name unfortunately. we have to raise issues for these upstream. For example, in the OIDC settings dialog which you posted earlier, you can see that the name comes from the provider type and there is no explicit label configuration. If you open a bug report upstream, please link here.