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 1559484 - Move IdM FIPS compliance information to separate section
Summary: Move IdM FIPS compliance information to separate section
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: doc-Linux_Domain_Identity_Management_Guide
Version: 7.4
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: ---
Assignee: Marc Muehlfeld
QA Contact: ipa-qe
URL:
Whiteboard:
Depends On: 1571754
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-03-22 16:04 UTC by Martin Kosek
Modified: 2019-04-09 10:31 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-04-09 10:31:35 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Martin Kosek 2018-03-22 16:04:36 UTC
Document URL: 
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/linux_domain_identity_authentication_and_policy_guide/installing-ipa#prerequisites

Section Number and Name: 
2.1.2. System Requirements

Describe the issue: 
This is a follow up to Bug 1510313. We recently hit questions and what can or cannot be done in FIPS mode when investigating Bug 1544679 and the person asking was not able to find the FIPS chapter we have now in the book.

FIPS requirements and expectations are now described within
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/linux_domain_identity_authentication_and_policy_guide/installing-ipa#prerequisites

Right now, when I search "FIPS" in
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/linux_domain_identity_authentication_and_policy_guide/index
, I get no results and I can only find it by displaying single HTML page. This makes the whole FIPS section less discoverable,

Suggestions for improvement: 
Based on the mentioned experience, I think we should have a separate section on FIPS, stating what does or does not work in FIPS mode (i.e. information from Prerequisites section), so that people can easily find that information out. If this is a separate section, another benefit would be that it appears in the guide Content Highlights.

Comment 2 Martin Kosek 2018-03-22 16:06:25 UTC
Assigning to Lucie initially as I discussed the idea with her and she has the context (feel free to re-assign of course).

Comment 3 Standa Laznicka 2018-04-18 08:02:31 UTC
Was there an update to this BZ?

Comment 5 Martin Kosek 2019-02-25 13:02:11 UTC
This makes sense. I think I would only consider to move 2.1.2.1 at one level up (i.e. 2.1.3), to avoid nesting too much.

Comment 8 Marc Muehlfeld 2019-04-09 10:31:35 UTC
The update is now available on the Customer Portal.


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