Skip to content

Commit

Permalink
deploy: a40aed3
Browse files Browse the repository at this point in the history
  • Loading branch information
@asteflova
asteflova committed Dec 12, 2024
1 parent 14ae458 commit ed55bba
Show file tree
Hide file tree
Showing 28 changed files with 2,066 additions and 899 deletions.
49 changes: 45 additions & 4 deletions nightly/Administering_Project/index-foreman-deb.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -1171,10 +1171,51 @@ <h4 id="Removing_a_User_Group_admin"><a class="anchor" href="#Removing_a_User_Gr
<div class="sect2">
<h3 id="Creating_and_Managing_Roles_admin"><a class="anchor" href="#Creating_and_Managing_Roles_admin"></a>3.5. Creating and managing roles</h3>
<div class="paragraph">
<p>Foreman provides a set of predefined roles with permissions sufficient for standard tasks, as listed in <a href="#Predefined_Roles_Available_in_foreman_admin">Predefined roles available in Foreman</a>.
It is also possible to configure custom roles, and assign one or more permission filters to them.
Permission filters define the actions allowed for a certain resource type.
Certain Foreman plugins create roles automatically.</p>
<p>Users in Foreman can have one or more roles assigned.
These roles are associated with permissions that enable users to perform specified administrative actions in Foreman.
Permission filters define the actions allowed for a certain resource type.</p>
</div>
<div class="paragraph">
<p>Foreman provides a set of predefined roles with permissions sufficient for standard tasks.
For a list of these roles, see <a href="#Predefined_Roles_Available_in_foreman_admin">Predefined roles available in Foreman</a>.
You can also configure custom roles.</p>
</div>
<div class="admonitionblock note">
<table>
<tr>
<td class="icon">
<div class="title">Note</div>
</td>
<td class="content">
<div class="paragraph">
<p>One of the predefined roles is the <strong>Default role</strong>.
Foreman assigns the <strong>Default role</strong> to every user in the system.
By default, the <strong>Default role</strong> grants only a limited set of permissions.
Be aware that if you add a permission to the <strong>Default role</strong>, every Foreman users will gain that permission.
Assigning a different role to a user does not remove the <strong>Default role</strong> from the user.</p>
</div>
</td>
</tr>
</table>
</div>
<div class="paragraph">
<p>The following types of roles are commonly defined within various Foreman deployments:</p>
</div>
<div class="dlist">
<dl>
<dt class="hdlist1">Roles related to applications or parts of infrastructure</dt>
<dd>
<p>For example, roles for owners of Enterprise Linux as the operating system as opposed to roles for owners of application servers and database servers.</p>
</dd>
<dt class="hdlist1">Roles related to a particular stage of the software lifecycle</dt>
<dd>
<p>For example, roles divided among the development, testing, and production phases, where each phase has one or more owners.</p>
</dd>
<dt class="hdlist1">Roles related to specific tasks</dt>
<dd>
<p>For example, you can create a role for security managers and a role for license managers, depending on the specific tasks users need to be able to perform within your organization.</p>
</dd>
</dl>
</div>
<div class="sect3">
<h4 id="Creating_a_Role_admin"><a class="anchor" href="#Creating_a_Role_admin"></a>3.5.1. Creating a role</h4>
Expand Down
49 changes: 45 additions & 4 deletions nightly/Administering_Project/index-foreman-el.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -1174,10 +1174,51 @@ <h4 id="Removing_a_User_Group_admin"><a class="anchor" href="#Removing_a_User_Gr
<div class="sect2">
<h3 id="Creating_and_Managing_Roles_admin"><a class="anchor" href="#Creating_and_Managing_Roles_admin"></a>3.5. Creating and managing roles</h3>
<div class="paragraph">
<p>Foreman provides a set of predefined roles with permissions sufficient for standard tasks, as listed in <a href="#Predefined_Roles_Available_in_foreman_admin">Predefined roles available in Foreman</a>.
It is also possible to configure custom roles, and assign one or more permission filters to them.
Permission filters define the actions allowed for a certain resource type.
Certain Foreman plugins create roles automatically.</p>
<p>Users in Foreman can have one or more roles assigned.
These roles are associated with permissions that enable users to perform specified administrative actions in Foreman.
Permission filters define the actions allowed for a certain resource type.</p>
</div>
<div class="paragraph">
<p>Foreman provides a set of predefined roles with permissions sufficient for standard tasks.
For a list of these roles, see <a href="#Predefined_Roles_Available_in_foreman_admin">Predefined roles available in Foreman</a>.
You can also configure custom roles.</p>
</div>
<div class="admonitionblock note">
<table>
<tr>
<td class="icon">
<div class="title">Note</div>
</td>
<td class="content">
<div class="paragraph">
<p>One of the predefined roles is the <strong>Default role</strong>.
Foreman assigns the <strong>Default role</strong> to every user in the system.
By default, the <strong>Default role</strong> grants only a limited set of permissions.
Be aware that if you add a permission to the <strong>Default role</strong>, every Foreman users will gain that permission.
Assigning a different role to a user does not remove the <strong>Default role</strong> from the user.</p>
</div>
</td>
</tr>
</table>
</div>
<div class="paragraph">
<p>The following types of roles are commonly defined within various Foreman deployments:</p>
</div>
<div class="dlist">
<dl>
<dt class="hdlist1">Roles related to applications or parts of infrastructure</dt>
<dd>
<p>For example, roles for owners of Enterprise Linux as the operating system as opposed to roles for owners of application servers and database servers.</p>
</dd>
<dt class="hdlist1">Roles related to a particular stage of the software lifecycle</dt>
<dd>
<p>For example, roles divided among the development, testing, and production phases, where each phase has one or more owners.</p>
</dd>
<dt class="hdlist1">Roles related to specific tasks</dt>
<dd>
<p>For example, you can create a role for security managers and a role for license managers, depending on the specific tasks users need to be able to perform within your organization.</p>
</dd>
</dl>
</div>
<div class="sect3">
<h4 id="Creating_a_Role_admin"><a class="anchor" href="#Creating_a_Role_admin"></a>3.5.1. Creating a role</h4>
Expand Down
49 changes: 45 additions & 4 deletions nightly/Administering_Project/index-katello.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -1699,10 +1699,51 @@ <h4 id="Removing_a_User_Group_admin"><a class="anchor" href="#Removing_a_User_Gr
<div class="sect2">
<h3 id="Creating_and_Managing_Roles_admin"><a class="anchor" href="#Creating_and_Managing_Roles_admin"></a>5.5. Creating and managing roles</h3>
<div class="paragraph">
<p>Foreman provides a set of predefined roles with permissions sufficient for standard tasks, as listed in <a href="#Predefined_Roles_Available_in_foreman_admin">Predefined roles available in Foreman</a>.
It is also possible to configure custom roles, and assign one or more permission filters to them.
Permission filters define the actions allowed for a certain resource type.
Certain Foreman plugins create roles automatically.</p>
<p>Users in Foreman can have one or more roles assigned.
These roles are associated with permissions that enable users to perform specified administrative actions in Foreman.
Permission filters define the actions allowed for a certain resource type.</p>
</div>
<div class="paragraph">
<p>Foreman provides a set of predefined roles with permissions sufficient for standard tasks.
For a list of these roles, see <a href="#Predefined_Roles_Available_in_foreman_admin">Predefined roles available in Foreman</a>.
You can also configure custom roles.</p>
</div>
<div class="admonitionblock note">
<table>
<tr>
<td class="icon">
<div class="title">Note</div>
</td>
<td class="content">
<div class="paragraph">
<p>One of the predefined roles is the <strong>Default role</strong>.
Foreman assigns the <strong>Default role</strong> to every user in the system.
By default, the <strong>Default role</strong> grants only a limited set of permissions.
Be aware that if you add a permission to the <strong>Default role</strong>, every Foreman users will gain that permission.
Assigning a different role to a user does not remove the <strong>Default role</strong> from the user.</p>
</div>
</td>
</tr>
</table>
</div>
<div class="paragraph">
<p>The following types of roles are commonly defined within various Foreman deployments:</p>
</div>
<div class="dlist">
<dl>
<dt class="hdlist1">Roles related to applications or parts of infrastructure</dt>
<dd>
<p>For example, roles for owners of Enterprise Linux as the operating system as opposed to roles for owners of application servers and database servers.</p>
</dd>
<dt class="hdlist1">Roles related to a particular stage of the software lifecycle</dt>
<dd>
<p>For example, roles divided among the development, testing, and production phases, where each phase has one or more owners.</p>
</dd>
<dt class="hdlist1">Roles related to specific tasks</dt>
<dd>
<p>For example, you can create a role for security managers and a role for license managers, depending on the specific tasks users need to be able to perform within your organization.</p>
</dd>
</dl>
</div>
<div class="sect3">
<h4 id="Creating_a_Role_admin"><a class="anchor" href="#Creating_a_Role_admin"></a>5.5.1. Creating a role</h4>
Expand Down
49 changes: 45 additions & 4 deletions nightly/Administering_Project/index-orcharhino.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -1660,10 +1660,51 @@ <h4 id="Removing_a_User_Group_admin"><a class="anchor" href="#Removing_a_User_Gr
<div class="sect2">
<h3 id="Creating_and_Managing_Roles_admin"><a class="anchor" href="#Creating_and_Managing_Roles_admin"></a>5.5. Creating and managing roles</h3>
<div class="paragraph">
<p>orcharhino provides a set of predefined roles with permissions sufficient for standard tasks, as listed in <a href="#Predefined_Roles_Available_in_orcharhino_admin">Predefined roles available in orcharhino</a>.
It is also possible to configure custom roles, and assign one or more permission filters to them.
Permission filters define the actions allowed for a certain resource type.
Certain orcharhino plugins create roles automatically.</p>
<p>Users in orcharhino can have one or more roles assigned.
These roles are associated with permissions that enable users to perform specified administrative actions in orcharhino.
Permission filters define the actions allowed for a certain resource type.</p>
</div>
<div class="paragraph">
<p>orcharhino provides a set of predefined roles with permissions sufficient for standard tasks.
For a list of these roles, see <a href="#Predefined_Roles_Available_in_orcharhino_admin">Predefined roles available in orcharhino</a>.
You can also configure custom roles.</p>
</div>
<div class="admonitionblock note">
<table>
<tr>
<td class="icon">
<div class="title">Note</div>
</td>
<td class="content">
<div class="paragraph">
<p>One of the predefined roles is the <strong>Default role</strong>.
orcharhino assigns the <strong>Default role</strong> to every user in the system.
By default, the <strong>Default role</strong> grants only a limited set of permissions.
Be aware that if you add a permission to the <strong>Default role</strong>, every orcharhino users will gain that permission.
Assigning a different role to a user does not remove the <strong>Default role</strong> from the user.</p>
</div>
</td>
</tr>
</table>
</div>
<div class="paragraph">
<p>The following types of roles are commonly defined within various orcharhino deployments:</p>
</div>
<div class="dlist">
<dl>
<dt class="hdlist1">Roles related to applications or parts of infrastructure</dt>
<dd>
<p>For example, roles for owners of Enterprise Linux as the operating system as opposed to roles for owners of application servers and database servers.</p>
</dd>
<dt class="hdlist1">Roles related to a particular stage of the software lifecycle</dt>
<dd>
<p>For example, roles divided among the development, testing, and production phases, where each phase has one or more owners.</p>
</dd>
<dt class="hdlist1">Roles related to specific tasks</dt>
<dd>
<p>For example, you can create a role for security managers and a role for license managers, depending on the specific tasks users need to be able to perform within your organization.</p>
</dd>
</dl>
</div>
<div class="sect3">
<h4 id="Creating_a_Role_admin"><a class="anchor" href="#Creating_a_Role_admin"></a>5.5.1. Creating a role</h4>
Expand Down
53 changes: 49 additions & 4 deletions nightly/Administering_Project/index-satellite.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -1777,6 +1777,10 @@ <h2 id="Managing_Locations_admin"><a class="anchor" href="#Managing_Locations_ad
</li>
</ul>
</div>
<div class="paragraph">
<p>You can structure locations hierarchically by providing a parent location.
Unless otherwise specified, locations inherit the settings from their parent location.</p>
</div>
<div class="sect2">
<h3 id="Creating_a_Location_admin"><a class="anchor" href="#Creating_a_Location_admin"></a>7.1. Creating a location</h3>
<div class="paragraph">
Expand Down Expand Up @@ -2557,10 +2561,51 @@ <h4 id="Removing_a_User_Group_admin"><a class="anchor" href="#Removing_a_User_Gr
<div class="sect2">
<h3 id="Creating_and_Managing_Roles_admin"><a class="anchor" href="#Creating_and_Managing_Roles_admin"></a>8.5. Creating and managing roles</h3>
<div class="paragraph">
<p>Satellite provides a set of predefined roles with permissions sufficient for standard tasks, as listed in <a href="#Predefined_Roles_Available_in_satellite_admin">Predefined roles available in Satellite</a>.
It is also possible to configure custom roles, and assign one or more permission filters to them.
Permission filters define the actions allowed for a certain resource type.
Certain Satellite plugins create roles automatically.</p>
<p>Users in Satellite can have one or more roles assigned.
These roles are associated with permissions that enable users to perform specified administrative actions in Satellite.
Permission filters define the actions allowed for a certain resource type.</p>
</div>
<div class="paragraph">
<p>Satellite provides a set of predefined roles with permissions sufficient for standard tasks.
For a list of these roles, see <a href="#Predefined_Roles_Available_in_satellite_admin">Predefined roles available in Satellite</a>.
You can also configure custom roles.</p>
</div>
<div class="admonitionblock note">
<table>
<tr>
<td class="icon">
<div class="title">Note</div>
</td>
<td class="content">
<div class="paragraph">
<p>One of the predefined roles is the <strong>Default role</strong>.
Satellite assigns the <strong>Default role</strong> to every user in the system.
By default, the <strong>Default role</strong> grants only a limited set of permissions.
Be aware that if you add a permission to the <strong>Default role</strong>, every Satellite users will gain that permission.
Assigning a different role to a user does not remove the <strong>Default role</strong> from the user.</p>
</div>
</td>
</tr>
</table>
</div>
<div class="paragraph">
<p>The following types of roles are commonly defined within various Satellite deployments:</p>
</div>
<div class="dlist">
<dl>
<dt class="hdlist1">Roles related to applications or parts of infrastructure</dt>
<dd>
<p>For example, roles for owners of Red&#160;Hat Enterprise Linux as the operating system as opposed to roles for owners of application servers and database servers.</p>
</dd>
<dt class="hdlist1">Roles related to a particular stage of the software lifecycle</dt>
<dd>
<p>For example, roles divided among the development, testing, and production phases, where each phase has one or more owners.</p>
</dd>
<dt class="hdlist1">Roles related to specific tasks</dt>
<dd>
<p>For example, you can create a role for security managers and a role for license managers, depending on the specific tasks users need to be able to perform within your organization.</p>
</dd>
</dl>
</div>
<div class="sect3">
<h4 id="Creating_a_Role_admin"><a class="anchor" href="#Creating_a_Role_admin"></a>8.5.1. Creating a role</h4>
Expand Down
4 changes: 2 additions & 2 deletions nightly/Configuring_User_Authentication/index-foreman-deb.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -217,7 +217,7 @@ <h1>Configuring authentication for Foreman users</h1>
<div id="toc" class="toc2">
<div id="toctitle">Table of Contents</div>
<ul class="sectlevel1">
<li><a href="#overview-of-authentication-methods-in-project_authentication">1. Overview of authentication methods in Foreman</a></li>
<li><a href="#overview-of-authentication-methods-in-foreman_authentication">1. Overview of authentication methods in Foreman</a></li>
<li><a href="#Accessing_Server_authentication">2. Accessing Foreman</a>
<ul class="sectlevel2">
<li><a href="#logging-in-to-the-foreman_web_UI_authentication">2.1. Logging in to the Foreman web UI</a></li>
Expand Down Expand Up @@ -285,7 +285,7 @@ <h1>Configuring authentication for Foreman users</h1>
</div>
<div id="content">
<div class="sect1">
<h2 id="overview-of-authentication-methods-in-project_authentication"><a class="anchor" href="#overview-of-authentication-methods-in-project_authentication"></a>1. Overview of authentication methods in Foreman</h2>
<h2 id="overview-of-authentication-methods-in-foreman_authentication"><a class="anchor" href="#overview-of-authentication-methods-in-foreman_authentication"></a>1. Overview of authentication methods in Foreman</h2>
<div class="sectionbody">
<div class="paragraph">
<p>Foreman includes native support for authentication with a username and password.
Expand Down
4 changes: 2 additions & 2 deletions nightly/Configuring_User_Authentication/index-foreman-el.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -217,7 +217,7 @@ <h1>Configuring authentication for Foreman users</h1>
<div id="toc" class="toc2">
<div id="toctitle">Table of Contents</div>
<ul class="sectlevel1">
<li><a href="#overview-of-authentication-methods-in-project_authentication">1. Overview of authentication methods in Foreman</a></li>
<li><a href="#overview-of-authentication-methods-in-foreman_authentication">1. Overview of authentication methods in Foreman</a></li>
<li><a href="#Accessing_Server_authentication">2. Accessing Foreman</a>
<ul class="sectlevel2">
<li><a href="#logging-in-to-the-foreman_web_UI_authentication">2.1. Logging in to the Foreman web UI</a></li>
Expand Down Expand Up @@ -285,7 +285,7 @@ <h1>Configuring authentication for Foreman users</h1>
</div>
<div id="content">
<div class="sect1">
<h2 id="overview-of-authentication-methods-in-project_authentication"><a class="anchor" href="#overview-of-authentication-methods-in-project_authentication"></a>1. Overview of authentication methods in Foreman</h2>
<h2 id="overview-of-authentication-methods-in-foreman_authentication"><a class="anchor" href="#overview-of-authentication-methods-in-foreman_authentication"></a>1. Overview of authentication methods in Foreman</h2>
<div class="sectionbody">
<div class="paragraph">
<p>Foreman includes native support for authentication with a username and password.
Expand Down
4 changes: 2 additions & 2 deletions nightly/Configuring_User_Authentication/index-katello.html
View file
Original file line number Diff line number Diff line change
Expand Up @@ -217,7 +217,7 @@ <h1>Configuring authentication for Foreman users</h1>
<div id="toc" class="toc2">
<div id="toctitle">Table of Contents</div>
<ul class="sectlevel1">
<li><a href="#overview-of-authentication-methods-in-project_authentication">1. Overview of authentication methods in Foreman</a></li>
<li><a href="#overview-of-authentication-methods-in-foreman_authentication">1. Overview of authentication methods in Foreman</a></li>
<li><a href="#Accessing_Server_authentication">2. Accessing Foreman</a>
<ul class="sectlevel2">
<li><a href="#logging-in-to-the-foreman_web_UI_authentication">2.1. Logging in to the Foreman web UI</a></li>
Expand Down Expand Up @@ -286,7 +286,7 @@ <h1>Configuring authentication for Foreman users</h1>
</div>
<div id="content">
<div class="sect1">
<h2 id="overview-of-authentication-methods-in-project_authentication"><a class="anchor" href="#overview-of-authentication-methods-in-project_authentication"></a>1. Overview of authentication methods in Foreman</h2>
<h2 id="overview-of-authentication-methods-in-foreman_authentication"><a class="anchor" href="#overview-of-authentication-methods-in-foreman_authentication"></a>1. Overview of authentication methods in Foreman</h2>
<div class="sectionbody">
<div class="paragraph">
<p>Foreman includes native support for authentication with a username and password.
Expand Down
Loading

0 comments on commit ed55bba

Please sign in to comment.