Update of baikal overwrites auth setting

What app is this about, and its version

baikal 0.12.1~ynh2

What YunoHost version are you running

12.1.40.1

What type of hardware are you using

VPS bought online

Describe your issue

Just to let you know about this slight issue which can be triggered by updating the baikal app. Authentication of external apps like DAVx didn’t work after update. The update may overwrite your personal auth setting, changing

dav_auth_type: 'Basic'
back to the default
dav_auth_type: 'LDAP-UserBind'

in /var/www/baikal/config/baikal.yaml

However the update logs notify you somehow

Share relevant logs or error messages

File /var/www/baikal/config/baikal.yaml has been manually modified since the installation or last upgrade. So it has been duplicated in /var/cache/yunohost/appconfbackup//var/www/baikal/config/baikal.yaml.backup.20260822.151312

The same happened to me, I was able to find it out and change it, but it took me some time not knowing the cause. I guess those configs shouldn’t be refreshed after an update.

You can ask to reopen this issue : Restore Baikal settings after upgrade · Issue #51 · YunoHost-Apps/baikal_ynh · GitHub

Could this help ?

You can try it with

yunohost app upgrade baikal -u https://github.com/YunoHost-Apps/baikal_ynh/tree/test_backup_vars  --force

A config panel would be interesting here

Indeed, that was my first thought and it was more straightforward but I think that if a user makes a change via baikal UI, it won’t be mirrored in settings.yml and there will be an inconsistency between the baikal.yaml (and its values displayed in the config panel) and the settings.yml.

I only considered a ‘basic’ config panel with bind ="foo>max:__INSTALL_DIR__/conf.json"

I guess a config script mirroring the values between settings.yml and baikal.yml could also do the trick.

I don’t know if this has anything to do with my problem:

With the android Davx5 and PC thunderbird applications, I can no longer log in with a baikal user account.

I tested a connection to baikal in a private window: This redirects me to the SSO of yunohost… However, Baikal is configured to accept “visitor” accounts.

In the baikal settings, “WebDAV authentication type” is set to LDAP-UserBind. I don’t know how it was set up before, but I think I need to switch it to Basic What do you think?

If you manually created users through the baikal admin UI, yes, switch to Basic.
If you use your yunohost users, it should work with LDAP-UserBind.

By default, only admins can reach the /admin page.

Try with “Basic” or with “Digest” if Basic doesn’t work

Well, thanks, that’s work with Basic.

I have test the ldap with an yunohost user, and that’s work to.

I think i don’t use yunohost in a good way…

If I’m not mistaken to use the LDAP function, you must create a baikal user with the same username as a yunohost user, I’m not sure but I’ve read that somewhere.

With WebDAV authentication type : LDAPUserBind you just need, for example, to create a calendar in thunderbird with one of your yunohost users’ credentials and that user will be added to the baikal users list.