Bug 803821
Summary: | Tech Preview: SELinux User Mapping | |||
---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Rob Crittenden <rcritten> | |
Component: | ipa | Assignee: | Rob Crittenden <rcritten> | |
Status: | CLOSED WONTFIX | QA Contact: | IDM QE LIST <seceng-idm-qe-list> | |
Severity: | unspecified | Docs Contact: | ||
Priority: | high | |||
Version: | 6.2 | CC: | dpal, jgalipea, mkosek | |
Target Milestone: | rc | |||
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | ipa-2.2.0-8.el6 | Doc Type: | Bug Fix | |
Doc Text: |
SELinux user mapping
Red Hat Enterprise Linux 6.3 introduces the ability to control the SELinux context of a user on a remote system. SELinux user map rules can be defined and, optionally, associated with HBAC rules. These maps define the context a user receives depending on the host they are logging into and the group membership. When a user logs into a remote host which is configured to use SSSD with the Identity Management backend, the user's SELinux context is automatically set according to mapping rules defined for that user. For more information, refer to http://freeipa.org/page/SELinux_user_mapping. This feature is considered a Technology Preview.
|
Story Points: | --- | |
Clone Of: | ||||
: | 816741 (view as bug list) | Environment: | ||
Last Closed: | 2012-06-14 19:16:24 UTC | Type: | --- | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 816741 |
Description
Rob Crittenden
2012-03-15 17:24:08 UTC
Fixed upstream: master: 55512dc938eb4a9a6655e473beab587e340af55c ipa-2-2: a4796575717dceb8ca22d61e24766ede93f49690 Rob, can you please add a short tech note about this feature in a CCCR format? Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Cause: Desire to be able to control the SELinux context a user would have on a remote system. Consequence: The user's SELinux context was not controllable. Change: SELinux user map rules can be defined and optionally associated with HBAC rules. These maps define the context a user will receive depending on the host they are logging into and group membership. Result: When a user logs into a remote host which is configured to use sssd with the ipa backend then their SELinux context will be set if there are any mapping rules defined for them. Feature is in and in tech preview Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1,7 +1,3 @@ -Cause: Desire to be able to control the SELinux context a user would have on a remote system. +SELinux user mapping -Consequence: The user's SELinux context was not controllable. +Red Hat Enterprise Linux 6.3 introduces the ability to control the SELinux context of a user on a remote system. SELinux user map rules can be defined and, optionally, associated with HBAC rules. These maps define the context a user receives depending on the host they are logging into and the group membership. When a user logs into a remote host which is configured to use SSSD with the Identity Management backend, the user's SELinux context is automatically set according to mapping rules defined for that user. For more information, refer to http://freeipa.org/page/SELinux_user_mapping. This feature is considered a Technology Preview.- -Change: SELinux user map rules can be defined and optionally associated with HBAC rules. These maps define the context a user will receive depending on the host they are logging into and group membership. - -Result: When a user logs into a remote host which is configured to use sssd with the ipa backend then their SELinux context will be set if there are any mapping rules defined for them. |