Bug 1302328

Summary:	cannot configure username and password for connection to LDAP
Product:	[Red Hat Storage] Red Hat Storage Console	Reporter:	Martin Kudlej <mkudlej>
Component:	core	Assignee:	Timothy Asir <tjeyasin>
core sub component:	authentication	QA Contact:	sds-qe-bugs
Status:	CLOSED ERRATA	Docs Contact:
Severity:	high
Priority:	high	CC:	japplewh, nthomas, sankarshan
Version:	2
Target Milestone:	---
Target Release:	2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-08-23 19:46:15 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:

Description Martin Kudlej 2016-01-27 13:54:54 UTC

Description of problem:
LDAP server can require authentication for connection. It is not possible to configure it now in configuration for LDAP authentication.

Version-Release number of selected component (if applicable):
rhscon-core-0.0.7-0.1.alpha1.el7.x86_64
rhscon-ui-0.0.6-0.1.alpha1.el7.noarch
rhscon-ceph-0.0.5-0.1.alpha1.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Configure AD server which requires authentication for connection

Actual results:
It is not possible to configure LDAP authentication in configuration.

Expected results:
It is possible to configure LDAP authentication in configuration and LDAP user can authenticate in USM.

Comment 1 Timothy Asir 2016-02-01 05:13:44 UTC

Patch sent to upstream for review: https://review.gerrithub.io/261751

Comment 3 Timothy Asir 2016-03-02 12:20:29 UTC

fixed in version rhscon-core-0.0.8-10.el7.x86_64

Comment 4 Jeff Applewhite 2016-03-18 18:41:37 UTC

still valid?

Comment 5 Martin Kudlej 2016-07-01 15:14:45 UTC

Tested with 
rhscon-core-0.0.29-1.el7scon.x86_64
rhscon-ui-0.0.43-1.el7scon.noarch
and it works. --> Verified

Comment 8 errata-xmlrpc 2016-08-23 19:46:15 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2016:1754