Bug #7003: Unable to connect to AD through ldap login module - Foreman

Custom queries

3.10.0 release DONE
3.10.0 release TODO
3.11.0 release DONE
3.11.0 release TODO
3.8.1 release DONE
3.8.1 release TODO
3.9.2 release DONE
3.9.2 release TODO
All bugs by votes
All issues closed in the last 3 weeks
Easy and Trivial Issues
Easy Issues (only)
Foreman - new open issues in last 10 days
Good first issues - Foreman core
high prio open bugs
Host registration [open]
Mine
My issues closed in the last 3 weeks
old bugs
Open with target version set (aka blockers)
registration
taken-none
Team Atlas untriaged bugs
templates
Trivial Issues
Untriaged and opened in the past two weeks

Actions

Copy link

Bug #7003

closed

Unable to connect to AD through ldap login module

Added by Leah Fisher over 9 years ago. Updated almost 6 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Daniel Lobato Garcia

Category:

Authentication

Target version:

1.6.0

Difficulty:

Triaged:

Bugzilla link:

Pull request:

https://github.com/theforeman/foreman/pull/1673

Fixed in Releases:

Found in Releases:

Nightly

Red Hat JIRA:

Description

Using settings that worked with the 1.5.2, I am unable to connect to AD for logins in the nightly release. I see the following in the logs:

LDAP-Auth with User lrf
Error during authentication: LdapError: no start_tls result
invalid user

I am trying to connect to the ldap server over ldaps.

Related issues 6 (2 open — 4 closed)

Related to Foreman - Feature #813: Support AD group membership for authorization and authentication	Closed	Daniel Lobato Garcia	03/31/2011	Actions
Related to Foreman - Bug #5414: LDAP + TLS is not LDAP + TLS but LDAP + SSL	Closed	Ori Rabin	04/23/2014	Actions
Related to Foreman - Bug #7016: Make Foreman support StartTLS	Closed			Actions
Related to Foreman - Bug #7066: Unable to bind with DOMAIN\$login any longer	Closed	Dominic Cleal	08/13/2014	Actions
Related to Foreman - Bug #7065: LDAP not able to authenticate user when password has a space in it	New		08/13/2014	Actions
Related to Foreman - Feature #36026: Make Foreman support StartTLS on LDAP connections	New			Actions

Issue # Delay: days Cancel

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Jason Berry over 9 years ago

Git log of file app/models/auth_sources/auth_source_ldap.rb shows commit 6421fa1ca91743085dd5460a82db37388d520638 changed the tls method from "simple_tls" to "start_tls".

Actions

Copy link

Updated by Dominic Cleal over 9 years ago

Related to Feature #813: Support AD group membership for authorization and authentication added

Actions

Copy link

Updated by Dominic Cleal over 9 years ago

Related to Bug #5414: LDAP + TLS is not LDAP + TLS but LDAP + SSL added

Actions

Copy link

Updated by Dominic Cleal over 9 years ago

Category set to Authentication
translation missing: en.field_release set to 10

Yeah, we seem to be muddled about this. The UI label used to say "TLS" although it was SSL-on-connect (LDAPS), we just fixed that and then changed the implementation to TLS (which I hadn't realised during review, good find Jason) while implementing group support and ldap_fluff.

Does AD provide TLS/STARTTLS style, or only LDAPS? If not, we should do both I think.

Actions

Copy link

Updated by The Foreman Bot over 9 years ago

Status changed from New to Ready For Testing
Target version set to 1.7.5
Pull request https://github.com/theforeman/foreman/pull/1673 added
Pull request deleted ()

Actions

Copy link

Updated by Daniel Lobato Garcia over 9 years ago

Thanks Leah and Jason, I've reverted the change in the attached PR. I also opened http://projects.theforeman.org/issues/7016 to track support of StartTLS.

Actions

Copy link