Bug 1584455

Summary: Issue displaying the photo pic on the main screen *instead customer see a long id*
Product: Red Hat Satellite Reporter: Waldirio M Pinheiro <wpinheir>
Component: WebUIAssignee: satellite6-bugs <satellite6-bugs>
WebUI sub component: Foreman QA Contact: Katello QA List <katello-qa-list>
Status: CLOSED DUPLICATE Docs Contact:
Severity: high    
Priority: unspecified CC: mhulan, sgraessl, tbrisker
Version: 6.3.1   
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-31 02:00:10 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 Waldirio M Pinheiro 2018-05-31 00:24:35 UTC 
Description of problem:
When Configuring the ldap authentication, we can use the attribute to request the picture from AD, on Sat6.2 we can't see the image/picture *tested locally / reproducer* but via foreman-rake console we can see the thumbnailphoto string *image coded* and no issues on the Satellite webUI.

The same configuration on Sat6.3, same result from foreman-rake console BUT on the webUI we can see the long number. The same when we access Administer / Users, on the Username column we can see the long number string instead the picture + username.

Version-Release number of selected component (if applicable):
6.3.1

How reproducible:
100%

Steps to Reproduce:
1. Configure ldap auth source pointing to the AD
2. Login with external user


Actual results:
Via user page we can see on the top right corn the long numeral string or when accessing Administer / Users / Username column.

Expected results:
See the picture on the customer page or see the picture + username when accessing Administer / Users / Username column.

Additional info:
Comment 1 Waldirio M Pinheiro 2018-05-31 02:00:10 UTC 

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