Aaron van Meerten

As a nomad admin and dark-mode-liking individual, I'm excited to see this feature progress! +1 from me!

I dug into this issue myself as I suspected that we don't test with JWTs required very often. It seems that this scenario isn't supported out of the box. I...

My (completed untested) PR for the token module changes required are here: https://github.com/jitsi/jitsi-meet/pull/12692

The helm chart in jitsi-contrib/ is definitely just a starting point for a basic jitsi deployment. For the customizations you have in mind it should be fairly simple to fork...

Ah, and for those interface_config.js overrides, you'd want to mount another ConfigMap at /config/custom-interface_config.js

I believe you may need to include certain features in your JWT payload in order to have recording enabled. Check out the documentation for the JaaS token here: https://developer.8x8.com/jaas/docs/api-keys-jwt

This looks more like an LDAP issue than a docker-jitsi-meet issue. Can you try also posting this question on the community forums? https://community.jitsi.org/ has a lot of helpful folks.

> https://github.com/winlibs/cyrus-sasl/blob/d933c030ce12ec0668469d79ab8378e347a1b3ba/saslauthd/LDAP_SASLAUTHD#L144 Yes I concur: we would welcome a PR to address this. Here's the file you'd want to start with: https://github.com/jitsi/docker-jitsi-meet/blob/0298a30ca68b94e8e66731767b716b45e23ffdd5/prosody/rootfs/defaults/saslauthd.conf#L4 In addition, you'll want to add any new...

> I'll see what I can do No pressure, if you end up stuck just reach out and one of us will try to move it along too. We don't...

Is there perhaps a debug mode in your ldap server or the saslauth module where you could see the incoming query format to determine whether your settings of configuration match...