Bug 1182367

Summary:	[RFE] Test LDAP connection button to know when LDAP authentication not working in Red Hat Satellite 6
Product:	Red Hat Satellite	Reporter:	John Gallucci <john.gallucci>
Component:	Infrastructure	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	Katello QA List <katello-qa-list>
Severity:	high	Docs Contact:
Priority:	high
Version:	Unspecified	CC:	bkearney, mmccune, xdmoon
Target Milestone:	Unspecified	Keywords:	FutureFeature
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
URL:	http://projects.theforeman.org/issues/9419
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:	Build Name: 22922, Installation Guide-6.0-1 Build Date: 07-10-2014 15:39:35 Topic ID: 31214-712456 [Latest]
Last Closed:	2015-02-18 12:57:38 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	260381

Description John Gallucci 2015-01-15 00:11:39 UTC

Title: Configuring LDAP Authentication for Red&nbsp;Hat Satellite

Describe the issue:
LDAP settings are configured, but user cannot login.

Suggestions for improvement:
This is more a request than a bug, but there needs to be a "Test LDAP Connection" button with a viewable error message.  Nowadays almost all enterprise products have this feature.  Having to debug user login errors without being able to first confirm your LDAP settings even work creates a hassle when troubleshooting.  The settings in the instructions are very vague as well as to what works and what doesnt.  These details should be expanded out as well.

Additional information:
Using Red Hat Satellite 6 running on RHEL 6.6.

Comment 1 RHEL Program Management 2015-01-15 00:24:03 UTC

Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 3 John Gallucci 2015-01-15 00:30:02 UTC

and password for the LDAP settings ended up being incorrect.  The log /var/log/foreman/production.log was the only location I could find that had information on there even being an error in the first place.  I was left to troubleshoot all settings for 20 minutes until I figured out what was wrong.

Please provide the correct log and log settings that show the details on the LDAP authentication.

Comment 4 John Gallucci 2015-01-15 00:31:13 UTC

I should add that the issue ended up being the fact that the account username and password for the LDAP settings ended up being incorrect.  The log /var/log/foreman/production.log was the only location I could find that had information on there even being an error in the first place.  I was left to troubleshoot all settings for 20 minutes until I figured out what was wrong.

Please provide the correct log and log settings that show the details on the LDAP authentication.

Comment 6 Athene Chan 2015-02-09 06:02:58 UTC

Hello John,

Sorry for the late reply to this ticket. I've escalated this to the developers to see if this sort of feature can be accommodated or if one exists. If one exists, then we'll schedule it into the documentation at a later date. If this does not exist, I will change the component from documentation to something else so that the developers can  keep track if this possible feature request.

Cheers,
Athene

Comment 9 Bryan Kearney 2015-02-17 18:38:33 UTC

Created redmine issue http://projects.theforeman.org/issues/9419 from this bug

Comment 10 Bryan Kearney 2015-02-18 12:57:38 UTC

Missed that it is a dupe. Closing this one and keeping the earlier one.

*** This bug has been marked as a duplicate of bug 1144232 ***