ct-Open-Source / ct-Open-Source/team-container
LDAP issues
- Dominant language
- HTML
- Stars
- 116
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
I successfully installed team-container/Jitsi Meet, then tried to switch to LDAP auth. This feature appears to be broken, though.
I had to change _team-container/team-video/templates/deploy_prosody.yaml_ as suggested in issue report #43. Though saslauthd then worked ok (tested from inside the pod using testsaslauthd), the Jitsi Meet web client simply ignored it (anyone could still open a room). After some searching, i discovered that, for some reason, the jicofo sip properties are missing an entry
org.jitsi.jicofo.auth.URL=XMPP:meet.example.org
Once changed inside the pod and jicofo restarted, LDAP auth works as expected with the Jitsi Meet web client.
How would i configure this in the YAML configuration to get it right in the first place?
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with team-video/templates/deploy_prosody.yaml and the Jicofo SIP properties generated by the deployment. Trace how the YAML configures saslauthd and Jicofo, then verify the resulting pod configuration against the required auth URL. Done means LDAP authentication works through the Jitsi Meet web client without manual pod changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, yaml
- Domain
- authentication, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100