Bug 1573243 – Can't edit users when using LDAP datasource

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1573243 - Can't edit users when using LDAP datasource

Summary:	Can't edit users when using LDAP datasource

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Satellite 6
Classification:	Red Hat
Component:	LDAP (Show other bugs)
Sub Component:
Version:	6.3.0
Hardware:	Unspecified Unspecified

Priority	unspecified Severity high (vote)
Target Milestone:	6.3.3
Target Release:	Unused
Assigned To:	Daniel Lobato Garcia
QA Contact:	Kedar Bidarkar
Docs Contact:

URL:
Whiteboard:
Keywords:	Regression, Triaged

Duplicates:	1584455 (view as bug list)
Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2018-04-30 11:05 EDT by Suraj Patil
Modified:	2018-08-22 16:07 EDT (History)
CC List:	7 users (show)

See Also:
Fixed In Version:	foreman-1.15.6.47-1
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Clones:	1596345 (view as bug list)
Environment:
Last Closed:	2018-08-22 16:07:08 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
screenshot of the issue (88.71 KB, image/png) 2018-04-30 11:05 EDT, Suraj Patil	no flags	Details
1573243_bz.patch (1.79 KB, patch) 2018-06-15 13:19 EDT, Waldirio M Pinheiro	no flags	Details \| Diff
Before and After patch applied (242.93 KB, application/pdf) 2018-06-15 13:23 EDT, Waldirio M Pinheiro	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Foreman Issue Tracker	13749	None	None	None	2018-05-30 21:48 EDT

Groups: None (edit)

Description Suraj Patil 2018-04-30 11:05:13 EDT

Created attachment 1428846 [details]
screenshot of the issue

Description of problem:

When satellite is configured with LDAP (AD server), users photo is not displayed.


How reproducible:

Configure LDAP AD server with satellite. Make sure to put photo attribute = thumbnailPhoto while configuring LDAP.

After configuring LDAP, login to the satellite using AD user.

Actual results:
corrupted image 

Expected results:
User photo should appear in the top right corner and in Administer > Users

Additional info:

Upstream bug - https://projects.theforeman.org/issues/13749

Comment 4 Waldirio M Pinheiro 2018-05-30 22:00:10 EDT

*** Bug 1584455 has been marked as a duplicate of this bug. ***

Comment 7 Daniel Lobato Garcia 2018-05-31 10:23:05 EDT

https://github.com/theforeman/foreman/pull/5630 PR is submitted upstream, waiting on review.

Comment 10 pm-sat@redhat.com 2018-06-07 12:04:40 EDT

Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/13749 has been resolved.

Comment 20 Waldirio M Pinheiro 2018-06-15 13:19 EDT

Created attachment 1452005 [details]
1573243_bz.patch

Comment 21 Waldirio M Pinheiro 2018-06-15 13:23 EDT

Created attachment 1452006 [details]
Before and After patch applied

Comment 24 Kedar Bidarkar 2018-08-01 06:48:57 EDT

Followed the below steps to verify this bug:

Made use of Powershell commands to download and upload photo to user attribute "thumbnailPhoto".

On AD Server:

1) Downloaded photo:
$client = new-object System.Net.WebClient
$client.DownloadFile(“http://example.com/pub/thumbnailphoto.jpg”,“C:\Users\Administrator\Pictures\thumbnailphot.jpg”)


2) Uploaded photo:
$photo = [byte[]](Get-Content C:\Users\Administrator\Pictures\thumbnailphoto.jpg -Encoding byte)
Set-ADUser foobar -Replace @{thumbnailPhoto=$photo}

On Satellite6 Server:

1) On Create LDAP Auth source page of "attribute mappings" Tab do:

Photo attribute: thumbnailPhoto


Verified with Sat6.3.3 snap2

Comment 25 Kedar Bidarkar 2018-08-01 06:50:51 EDT

The photo added to user "foobar" on AD Server appeared automatically in the top right corner of Administer > Users.

Comment 27 errata-xmlrpc 2018-08-22 16:07:08 EDT

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/RHBA-2018:2550

Note You need to log in before you can comment on or make changes to this bug.