UI: Display names for related identity groups and entities

[sgabenov]

Issues

Fixes #31494.
Related to #15740 and #31495.

Description

Display readable names instead of raw IDs for identity relationships in the Vault UI:

• groups associated with an entity, including inherited groups;
• group and entity members of a group;
• parent groups.

The identity read endpoints expose only relationship IDs. The UI now resolves those IDs from the existing identity list endpoints, whose key_info contains both IDs and names. IDs remain available as native tooltips.

This approach makes at most one additional list request per related identity type, and only when the active tab has relationships to display. It avoids issuing a separate read request for every row. If a list request fails, for example because the token lacks list permission, the page continues to render and falls back to the original IDs.

This is an updated alternative to #31495, adapted to the current API-service-based identity routes.

User impact

Operators can identify related groups and entities without copying UUIDs into separate lookups. The fallback preserves the existing behavior for restricted policies.

Testing

• ember-template-lint for the changed identity templates
• eslint for the changed route and acceptance tests
• git diff --check
• identity acceptance module: 9 tests passed

PCI review checklist

• I have documented a clear reason for, and description of, the change I am making.
• If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
• If applicable, I've documented the impact of any changes to security controls. Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.

[vercel]

Deployment failed for project vault-ui with the following error:

The `vercel.json` schema validation failed with the following message: should NOT have additional property `public`

Learn More: https://vercel.com/docs/concepts/projects/project-configuration

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
vault-ui	Error		Aug 12, 2026 7:34am

[hashicorp-cla-app]

All committers have signed the CLA.

[hashicorp-cla-app]

Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement

Learn more about why HashiCorp requires a CLA and what the CLA includes

---

gabenov.s seems not to be a GitHub user.
You need a GitHub account to be able to sign the CLA.
If you have already a GitHub account, please add the email address used for this commit to your account.

_{Have you signed the CLA already but the status is still pending? Recheck it.}

[vercel]

Deployment failed for project vault-ui with the following error:

The `vercel.json` schema validation failed with the following message: should NOT have additional property `public`

Learn More: https://vercel.com/docs/concepts/projects/project-configuration

[vercel]

Deployment failed for project vault-ui with the following error:

The `vercel.json` schema validation failed with the following message: should NOT have additional property `public`

Learn More: https://vercel.com/docs/concepts/projects/project-configuration