Bug 2223695 - Security and Hardening Guide provide advises how to tune API policies, but the outcome of this process is not supported
Summary: Security and Hardening Guide provide advises how to tune API policies, but th...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 16.2 (Train)
Hardware: All
OS: All
unspecified
high
Target Milestone: ---
: ---
Assignee: RHOS Documentation Team
QA Contact: RHOS Documentation Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-07-18 14:18 UTC by Alex Stupnikov
Modified: 2023-07-25 12:42 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-07-25 12:42:39 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-26701 0 None None None 2023-07-18 14:24:59 UTC

Description Alex Stupnikov 2023-07-18 14:18:12 UTC
Description of problem:

RHOSP 16.2 "Security and Hardening Guide" has section "5.7. Modifying policies with heat" that explains how to use *Policies THT parameters to tune default API policies. No additional requirements or warnings are provided there, while according to engineering this process is not supported. I will provide references privately.

Comment 5 Roger Heslop 2023-07-24 20:33:49 UTC
I've re-published the guide with the same admonition that currently exists at the top of Chapter 5, to be shown with all modules that deal directly with the modification of policies.

* The change is complete for both 16.2 and 17.0 versions of the documentation
* This same change will persist for the next release, 17.1 GA.
* This change will _not_ be visible in 17.1-Beta documentation

Alex, could you let me know if this fulfills the request of the BZ?

Thanks,

Comment 6 Alex Stupnikov 2023-07-25 09:55:16 UTC
Current version of RHOSP 16.2 document looks perfect to me. Thank you very much for the changes you have introduced.


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