Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.

Bug 1484289

Summary: [IPA Documentation] - Clarify shared-secrets can only be used for two-way trusts.
Product: Red Hat Enterprise Linux 7 Reporter: Raul Mahiques <rmahique>
Component: doc-Windows_Integration_GuideAssignee: Filip Hanzelka <fhanzelk>
Status: CLOSED CURRENTRELEASE QA Contact: ipa-qe <ipa-qe>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.4CC: apetrova, arydekul, fhanzelk, mvarun, rhel-docs
Target Milestone: rcKeywords: Documentation
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-12 13:37:28 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 Raul Mahiques 2017-08-23 08:04:33 UTC
Document URL: 
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7-Beta/html-single/Windows_Integration_Guide/index.html#create-trust-shared-secret

Section Number and Name: 
5.2.2.2. Creating a Trust with a Shared Secret

Describe the issue: 
the example talks about one-way:incoming trust, this is not possible at the moment:
https://pagure.io/freeipa/issue/5683

Suggestions for improvement: 
Could you change to reflect that only two-way trust works when using a shared secret?

Additional information: 
Also could you specify the windows AD version? different versions follow different steps.

Thanks!

Comment 2 Alexander Rydekull 2017-11-09 09:53:05 UTC
When will this documentation be fixed?

The product documentation specifically states that it works while it doesn't. Setting wrong expectations and assumptions.

Comment 3 Aneta Šteflová Petrová 2017-11-09 10:41:06 UTC
(In reply to Raul Mahiques from comment #0)
> Document URL: 
> https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7-
> Beta/html-single/Windows_Integration_Guide/index.html#create-trust-shared-
> secret
> 
> Section Number and Name: 
> 5.2.2.2. Creating a Trust with a Shared Secret
> 
> Describe the issue: 
> the example talks about one-way:incoming trust, this is not possible at the
> moment:
> https://pagure.io/freeipa/issue/5683
> 
> Suggestions for improvement: 
> Could you change to reflect that only two-way trust works when using a
> shared secret?

We are working on this part of the issue in BZ#1504235, which is a partial duplicate of this BZ. 

> 
> Additional information: 
> Also could you specify the windows AD version? different versions follow
> different steps.

I'm not sure when we'll get to this part of the issue because the first part is more critical (it's about fixing incorrect information, as Alexander noted in c#2).

> 
> Thanks!

Comment 4 Filip Hanzelka 2017-11-16 14:51:53 UTC
https://bugzilla.redhat.com/show_bug.cgi?id=1504235, which is a partial duplicate of this BZ - see C#3 -, has now been verified.