omniauth-ldap | LDAP strategy for OmniAuth | Identity Management library
kandi X-RAY | omniauth-ldap Summary
kandi X-RAY | omniauth-ldap Summary
LDAP strategy for OmniAuth
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of omniauth-ldap
omniauth-ldap Key Features
omniauth-ldap Examples and Code Snippets
Community Discussions
Trending Discussions on omniauth-ldap
QUESTION
I'm trying to configure Gitlab 10.0.2 to use LDAP authentication. I cannot use TLS, so I was hoping to use SASL DIGEST-MD5 to provide better security than cleartext. The Gitlab documentation seems to suggest that this is possible (emphasis mine):
You should disable anonymous LDAP authentication and enable simple or SASL authentication.
However, it does not provide any guidance on how to configure a SASL bind. I've tried setting the try_sasl
and sasl_mechanisms
configuration keys mentioned in the omniauth-ldap README, but I've verified with Wireshark that a simple bind is still being used instead of DIGEST-MD5.
The relevant section from my gitlab.rb:
...ANSWER
Answered 2017-Oct-04 at 20:31I got it working, but only by patching the Gitlab install. So, be forewarned: Here there be dragons
Patch /etc/gitlab/gitlab.rbQUESTION
I currently try to configure Discourse to only allow users in a specific ldap group to log in. Discourse has a plugin called discourse-ldap auth ( https://github.com/jonmbake/discourse-ldap-auth ). This plugin uses the omniauth ldap module: https://github.com/omniauth/omniauth-ldap
My discourse plugin configuration (the configuration is actually used by the discourse plugin for the omniauth ldap module):
- ldap enabled: true
- ldap hostname: the hostname of my ldap server
- ldap port: 389
- ldap method: plain
- ldap base: the base of my ldap server
- ldap uid: userPrincipalName
- ldap bind dn: Nothing
- ldap password: Nothing
- ldap filter: (&(userPrincipalName=%{username})(memberOf=cn=[the name of the required group],ou=....,[base]))
When using this configuration, nobody can log in to the forum. When I use the bind dn and password, everybody can log in. I also tried this filter without success (copied from my ldap servers filter):
- (&(&(&(userPrincipalName=%{username})(memberOf=[dn of the group]))))
What do I have to configure, to only allow users in that specific group to log in?
I didn't found any errors or indicators in the log. Please help!
Thanks fou your help and attention!
...ANSWER
Answered 2018-Nov-21 at 19:09You do need the "ldap dn" and "ldap password". Those are the credentials used to authenticate to LDAP so you can lookup people's accounts. Usually, that is a service account only used by your application.
The filter should probably look something like this:
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install omniauth-ldap
On a UNIX-like operating system, using your system’s package manager is easiest. However, the packaged Ruby version may not be the newest one. There is also an installer for Windows. Managers help you to switch between multiple Ruby versions on your system. Installers can be used to install a specific or multiple Ruby versions. Please refer ruby-lang.org for more information.
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page