Bug 1309118 - In the 'AD integration with GSS proxy' procedure, add the package 'gssproxy' to the list of prerequisites
Summary: In the 'AD integration with GSS proxy' procedure, add the package 'gssproxy' ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Docs User Guide
Version: 6.1.2
Hardware: Unspecified
OS: Unspecified
medium
high vote
Target Milestone: Unspecified
Assignee: Brandi Munilla
QA Contact: Allison Heslin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-02-16 22:36 UTC by Russell Dickenson
Modified: 2019-10-10 11:13 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-27 23:43:03 UTC
Target Upstream Version:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1343567 0 high CLOSED Ad Integration Install packages step requires installing 'gssproxy' package 2021-02-22 00:41:40 UTC

Internal Links: 1343567

Description Russell Dickenson 2016-02-16 22:36:02 UTC
Document URL: https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.1/html-single/User_Guide/index.html#sect-Red_Hat_Satellite-User_Guide-AD_direct

Section Number and Name: 20.4. USING ACTIVE DIRECTORY DIRECTLY

Describe the issue: The procedure does not mention the package 'gssproxy' in the list of prerequisites, which results in failure of the desired configuration.

Suggestions for improvement: Add the package 'gssproxy' to the list of prerequisites.

Additional information: This ticket was raised in response to the following Customer Portal discussion: https://access.redhat.com/discussions/2148371

Comment 1 Andrew Dahms 2016-02-19 05:41:26 UTC
Assigning to Brandi for review.

Brandi - looks like we need to add the name of the package mentioned above to the list in Step 1. of Procedure 20.4.

Comment 4 Andrew Dahms 2016-04-27 23:43:03 UTC
This content is now live on the Customer Portal.

Closing.


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