New User and default Library access

jdaviescoates

It sounds to me like this ought to be configurable and that the standard Jellyin default is indeed that all users ought to have access to all libraries, see https://jellyfin.org/docs/general/server/users/adding-managing-users/

girish

We use Jellyfin LDAP plugin - https://github.com/jellyfin/jellyfin-plugin-ldapauth

Not a csharp dev, but it seems the default value in the plugin is false which doesn't match the upstream defaults - https://github.com/jellyfin/jellyfin-plugin-ldapauth/blob/a866c85e7c34cb5848c287586987fbe4761dd250/LDAP-Auth/Config/PluginConfiguration.cs#L40

girish

OK, https://github.com/jellyfin/jellyfin-plugin-ldapauth/blob/a866c85e7c34cb5848c287586987fbe4761dd250/LDAP-Auth/Config/configPage.html#L268C80-L268C96

@cylon Can you try this:

Edit /app/data/jellyfin/data/plugins/configurations/LDAP-Auth.xml using File manager
Add <EnableAllFolders>true</EnableAllFolders>
Restart the app

cylon

I tried adding the line <EnableAllFolders>true</EnableAllFolders> but when I restart the app the config is restored to the original version without the line.

I saved the file, I can see the line is there when I close / open the file, but after restarting the app the LDAP-Auth.xml is somehow restored

cylon

also, I tried creating a new user without restarting Jellyfin (when the EnableAllFolders config is still there) and it works, new user have access to all librairies
The issue is now only that at restart this config got removed from the config file

cylon

additional question:

When I delete a user from Cloudron User management, the user is not delete from Jellyfin and still have access

( but maybe I should open a new topic for this one?)

nebulon

Indeed https://git.cloudron.io/cloudron/jellyfin-app/-/blob/master/start.sh?ref_type=heads#L24 does overwrite that file on every restart. We have to make the package smarter to only selectively update fields. I have created a task for this, but may take some time to get to this with holidays coming up.

The user syncing for deleted users is very app dependent and the general rule is that log into the app will fail (since user is gone so credentials can't be checked) but usually apps do not purge such users and the data. Those things would have to get fixed upstream, so feel free to create an issue for this at the upstream project.