Skip to main content
User guide

ID views

When an ID view is the right tool, which attributes an override can change, how a view is applied to hosts, and why Default Trust View must not be deleted.

This page covers the ID views page under Identity. An ID view gives a subset of hosts a different set of user and group attributes: uid, gid, home, shell, GECOS, SSH keys. The global directory is untouched; only hosts the view is applied to see the overrides.

ID views

UseNotes
Migrationzhangwei was uid 1500 on the legacy system and IPA allocated 60005. Until the old file server is re-chowned, the affected hosts keep seeing 1500
Per-host differencesA different shell or home on certain hosts, such as a bastion that only grants rbash
POSIX attributes for AD usersUsers from an AD trust have no uid or shell of their own; they come from overrides in Default Trust View or from the ID range algorithm

Overrides

User overrides

One override per user or group per view. Only the fields to change are filled in; empty fields keep the global value. The target of a user override can be an IPA user or an AD user (user@ad.example.com).

AttributeUserGroup
Login or group nameOverridableOverridable
UID or GIDOverridableOverridable
Home, shell, GECOSOverridableNone
SSH keys, certificatesOverridableNone

Applied to

Applied to

A view is applied to hosts or host groups. A host has at most one view at a time; applying another replaces it. IPA servers cannot have a view. The client's sssd cache must be cleared (sss_cache -E) or expire before overrides become visible.

Default Trust View is created when the AD trust is set up and applies to every host without an explicit view; overrides for AD users live there by default. Deleting it drops every Linux-side attribute override for AD users.

Boundaries

TopicNotes
File ownershipOverriding a uid does not change ownership on disk. After migration, either chown or keep the view permanently
Access evaluationOverrides play no part in HBAC and sudo evaluation, which looks at global objects and group membership
Client requirementViews work only on IPA clients running sssd 1.12 or later. Legacy systems talking plain LDAP to IPA do not see them

On this page