devise_ldap_authenticatable | Devise Module for LDAP | Identity Management library

by cschiewek Ruby Version: Current License: MIT

X-Ray Key Features Code Snippets Community Discussions(3)Vulnerabilities Install Support

kandi X-RAY | devise_ldap_authenticatable Summary

devise_ldap_authenticatable is a Ruby library typically used in Security, Identity Management, Ruby On Rails applications. devise_ldap_authenticatable has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub.

[Code Climate] Devise LDAP Authenticatable is a LDAP based authentication strategy for the [Devise] authentication framework. If you are building applications for use within your organization which require authentication and you want to use LDAP, this plugin is for you. Devise LDAP Authenticatable works in replacement of Database Authenticatable. This devise plugin has not been tested with DatabaseAuthenticatable enabled at the same time. This is meant as a drop in replacement for DatabaseAuthenticatable allowing for a semi single sign on approach. For a screencast with an example application, please visit: [

Support

Quality

Security

License

Reuse

Support

devise_ldap_authenticatable has a low active ecosystem.

It has 587 star(s) with 353 fork(s). There are 23 watchers for this library.

It had no major release in the last 6 months.

There are 44 open issues and 114 have been closed. On average issues are closed in 167 days. There are 3 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of devise_ldap_authenticatable is current.

Quality

devise_ldap_authenticatable has no bugs reported.

Security

devise_ldap_authenticatable has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

devise_ldap_authenticatable is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

devise_ldap_authenticatable releases are not available. You will need to build from source code and install.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of devise_ldap_authenticatable

Get all kandi verified functions for this library.

devise_ldap_authenticatable Key Features

No Key Features are available at this moment for devise_ldap_authenticatable.

devise_ldap_authenticatable Examples and Code Snippets

No Code Snippets are available at this moment for devise_ldap_authenticatable.

Community Discussions

Trending Discussions on devise_ldap_authenticatable

rails devsie_ldp how to ignore certificate verification?

Infinite redirects with Devise and devise_cas_authenticatable

rake aborted! cannot load such file -- ap

QUESTION

rails devsie_ldp how to ignore certificate verification?

Asked 2018-Nov-28 at 21:19

I am using devise, devise_ldap_authenticatable module to do simple ldap authentication. But if I try to authenticate on ssl (689 port), I have this error:

...

ANSWER

Answered 2018-Nov-28 at 21:19

Per the devise_ldap_authenticatable documentation

If you're using a test LDAP server running a self-signed SSL certificate, make sure the appropriate root certificate is installed on your system. Alternately, you may temporarily disable certificate checking for SSL by modifying your system LDAP configuration (e.g., /etc/openldap/ldap.conf or /etc/ldap/ldap.conf) to read TLS_REQCERT never.

Source https://stackoverflow.com/questions/53515612

QUESTION

Infinite redirects with Devise and devise_cas_authenticatable

Asked 2018-Mar-07 at 11:57

I have a Rails 5.2 app that uses Devise 4.4.1 and devise_ldap_authenticatable for auth. I'm trying to switch that out for devise_cas_authenticatable and now get into a redirect loop after entering my credentials on the CAS login page.

The app, the CAS server (rubycas-server), LDAP and the database are all running as Docker containers through Docker Compose. The CAS server is configured to use HTTP for development.

From what I can tell, my app isn't setting a session when CAS returns after logging in, but I have no idea why. Even some pointers for debugging would be gratefully received.

Here is the section of the log that repeats with each redirect:

...

ANSWER

Answered 2018-Mar-07 at 11:57

The problem occurred when devise_ldap_authenticatable called resource.save. Validations run before the before_create callback, and these validation errors were silently preventing the user from being created and thus authenticated. The uniqueness validation on the email field is why the log shows a SELECT by email.

The solution was to change

Source https://stackoverflow.com/questions/49110126

QUESTION

rake aborted! cannot load such file -- ap

Asked 2018-Jan-31 at 09:49

I have build my new rails application and when I am trying to deploy to Apache server while executing bundle exec rake secret I am getting rake aborted! cannot load such file -- ap.This is the URL I have referred to deploy Deploying a Ruby app on a Linux/Unix production server.

Please look into my Gemfile

...

ANSWER

Answered 2018-Jan-31 at 09:48

This line in the Gemfile seems strange to me

Source https://stackoverflow.com/questions/48538938

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install devise_ldap_authenticatable

Run the rails generators for devise (please check the [devise](http://github.com/plataformatec/devise) documents for further instructions). Run the rails generator for devise_ldap_authenticatable.

Support

Using a "username" instead of an "email": The field that is used for logins is the first key that’s configured in the config/initializers/devise.rb file under config.authentication_keys, which by default is email. For help changing this, please see the [Railscast](http://railscasts.com/episodes/210-customizing-devise) that goes through how to customize Devise. Also, this [documentation](https://github.com/plataformatec/devise/wiki/How-To%3a-Allow-users-to-sign-in-using-their-username-or-email-address) from Devise can be very helpful. SSL certificate invalid: If you’re using a test LDAP server running a self-signed SSL certificate, make sure the appropriate root certificate is installed on your system. Alternately, you may temporarily disable certificate checking for SSL by modifying your system LDAP configuration (e.g., /etc/openldap/ldap.conf or /etc/ldap/ldap.conf) to read TLS_REQCERT never. Devise LDAP Authenticatable uses a running OpenLDAP server to do automated acceptance tests. You’ll need the executables slapd, ldapadd, and ldapmodify. On OS X, this is available out of the box. On Ubuntu, you can install OpenLDAP with sudo apt-get install slapd ldap-utils. If slapd runs under AppArmor, add an exception like this to /etc/apparmor.d/local/usr.sbin.slapd to let slapd read our configs (reload using sudo service apparmor reload afterwards).

Find more information at: