Bug 1786981

Summary:	cross-forest realm auth doesn't fetch user info from Active Directory automatically in satellite
Product:	Red Hat Satellite	Reporter:	Ram Nayan Singh <ramsingh>
Component:	Authentication	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED WONTFIX	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	low
Version:	6.5.0	CC:	aruzicka, mhulan, tbrisker
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-08-08 10:51:17 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 Ram Nayan Singh 2019-12-30 06:16:20 UTC

cross-forest realm auth doesn't fetch user info from Active Directory automatically in the satellite.

Satellite 6.5

Integrated cross-forest realm to point Satellite server to IDM and IDM to one way trusted to AD

when AD-User tries to login first-time satellite does not fetch First Name, Last Name, and Email Address from AD.

whenever AD-User is logged satellite should fetch the user info (First Name, Last Name, and Email Address) from AD.

Comment 4 Mike McCune 2021-07-13 21:54:48 UTC

Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 6 Adam Ruzicka 2023-08-08 10:51:17 UTC

Closing this bug out since we do not believe it will be fixed in the next multiple releases due to our current available capacity and the amount of external dependencies looking into this would require. If this is a large impact on you, please feel free to re-open it and provide additional information to help us better prioritize it.