Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Document URL: 
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.13/html/installing_satellite_server_in_a_connected_network_environment/configuring_external_authentication_satellite#Kerberos_Configuration_in_Web_Browsers_satellite

Section Number and Name: 
5.3.4. Kerberos Configuration in Web Browsers

Describe the issue:
There is a note about GPO-PAM mapping.
I think this shouldn't be a note.
I think this should be in the section 5.3.3. Configuring Direct AD Integration with GSS-Proxy.
Because this setting is required (I wasn't able to get AD auth working without it) and it needs to be done on the Satellite, not on the client (running the web browser).

Related:
https://bugzilla.redhat.com/show_bug.cgi?id=2117523 but it was closed because there is already this KBA: https://access.redhat.com/solutions/6982443 ... however, 1) KBA isn't a proper documentation and 2) this is actually in docs but in a wrong place and incorrectly marked.

Missing that causes this error on login in WebUI or with ticket:

PAM authentication failed for user foobar: User not known to the underlying authentication module, referer: <FQDN>

Hello!
Currently in progress of making the PR with requested changes.
Link to draft PR here: https://github.com/theforeman/foreman-documentation/pull/2307

The documentation has been updated:
6.13: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.13/html-single/installing_satellite_server_in_a_connected_network_environment/index#Configuring_Direct_AD_Integration_with_GSS_Proxy_satellite
6.12: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.12/html-single/installing_satellite_server_in_a_connected_network_environment/index#Configuring_Direct_AD_Integration_with_GSS_Proxy_satellite
6.11: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.11/html-single/administering_red_hat_satellite/index#Configuring_Direct_AD_Integration_with_GSS_Proxy_admin