Galène videoconferencing server discussion list archives
 help / color / mirror / Atom feed
From: "Michael Ströder" <michael@stroeder.com>
To: galene@lists.galene.org
Subject: [Galene] Re: Experimental LDAP integration for Galene
Date: Wed, 3 Aug 2022 12:17:28 +0200	[thread overview]
Message-ID: <f93f8541-1859-bf91-497b-68da4225903a@stroeder.com> (raw)
In-Reply-To: <878ro5bqpf.wl-jch@irif.fr>

On 8/3/22 11:51, Juliusz Chroboczek wrote:
> https://github.com/jech/galene-ldap
> 
> Probably not very useful yet, but a good platform for further
> experimentation.  If you're running LDAP, please try setting it up and
> share your ideas about how it could be made useful.

In general when implementing an LDAP auth client it's very helpful to 
make the LDAP filter for searching the user entry configurable with kind 
of template string.

Especially the hard-coded filter

(&(objectClass=posixAccount)(uid=%s))

won't work in most LDAP deployments which do not use this object class 
for accounts, with MS AD being the most prominent example.

Especially you could define for simple access control:

(&(uid=%s)(memberOf=cn=test-auth,dc=example,dc=org))

Or any other kind of attribute-based login access control.

BTW: While historically I have quite strong LDAP background I'm still 
convinced that an OpenID Connect (OIDC) integration would be more 
helpful for the future. So you could leave LDAP integration, 2FA etc. to 
the usual WebSSO suspects like Keycloak, Authelia, CAS, Authentik etc. 
And admins can choose whatever other authc mech they want.

Ciao, Michael.

  reply	other threads:[~2022-08-03 10:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-03  9:51 [Galene] " Juliusz Chroboczek
2022-08-03 10:17 ` Michael Ströder [this message]
2022-08-03 10:29   ` [Galene] " Juliusz Chroboczek
2022-08-03 11:48     ` Michael Ströder
2022-08-03 12:25       ` Juliusz Chroboczek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.galene.org/postorius/lists/galene.lists.galene.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f93f8541-1859-bf91-497b-68da4225903a@stroeder.com \
    --to=michael@stroeder.com \
    --cc=galene@lists.galene.org \
    --subject='[Galene] Re: Experimental LDAP integration for Galene' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox