Bug 1786981 - cross-forest realm auth doesn't fetch user info from Active Directory automatically in satellite
Summary: cross-forest realm auth doesn't fetch user info from Active Directory automat...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Authentication
Version: 6.5.0
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-12-30 06:16 UTC by Ram Nayan Singh
Modified: 2023-08-08 10:51 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-08 10:51:17 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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.


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