Skip to content

eDirectory Identity Manager Roles

  • Users

    Keep the assignments maintained on user entries.

  • Roles and groups

    Expose membership views for browsing and counts.

The IDM profile exposes role and group memberships for client queries.

You can add the membership profile to your configured user, role and group entry types.

You decide: Use this profile when eDirectory Identity Manager owns your role assignments.

Next: Attribute modeling

Use this profile when eDirectory Identity Manager owns role assignments on user entries and clients need to browse roles, groups, and membership counts through IdentityScribe.

Start from your normal production config, define the user, role, and group transcribes, then include the profile after those transcribes:

include required("production.conf")

# Configure database, ldap, auth, and the
# user/role/group transcribes here.

include required("edirectory-idm.conf")

The profile is additive. It appends IDM attributes and index coverage to existing transcribes, and it adds virtual attributes for high-fanout reverse views. If your transcribe names differ from user, role, or group, copy the profile and adjust the paths.

Rolealso equivalentToMeUserstored listsGroupnrfMemberOfroleMembersgroupMembershipmember
Rolealso equivalentToMeUserstored listsGroupnrfMemberOfroleMembersgroupMembershipmember
User-side membership powers the virtual role and group member views.

Track role and group membership on the user side:

AttributePurpose
nrfMemberOfEffective role membership. Use this for “users holding this role” searches and counts.
nrfAssignedRolesDirect role assignments. Values include assignment metadata after the role DN.
nrfInheritedRolesRole assignments inherited through hierarchy.
nrfGroupRolesRole assignments inherited through group membership.
nrfContainerRolesRole assignments inherited through containers.
nrfAssociatedRolesImplicit role assignment details where present.
groupMembershipUser-side group membership. This powers the virtual group member view.
nrfAssignedResourcesAssigned resources.
DirXML-EntitlementRefEntitlement references.

Add these attributes to transcribes.user.ldap.attributes and transcribes.user.indices.value-match. The path-style role attributes are matched by their role-DN prefix, so they need query coverage even though the full value contains metadata.

Store role metadata, hierarchy, and status on the role side:

AttributePurpose
nrfLocalizedNames, nrfLocalizedDescrsDisplay labels and descriptions.
nrfRoleCategoryKeyRole category filters.
nrfRoleLevelRole level filters.
nrfStatusRole status filters.
nrfParentRoles, nrfChildRolesRole hierarchy display.
nrfImplicitGroupsGroups connected to the role where eDirectory provides plain DN values.
ownerRole ownership display and filters.

Do not sync the physical equivalentToMe value for large role sets. The profile computes equivalentToMe, and the clearer roleMembers, from user nrfMemberOf, so IdentityHub-style queries still work without a large reverse list on every role.

When users carry groupMembership, prefer that user-side value over syncing very large group member lists. The profile computes group member from it, which supports group membership filters.

If your directory does not provide groupMembership, remove ldap.virtual-attributes.member from the profile and sync the physical group member attribute instead.

Track these group-side attributes for metadata and IDM links:

AttributePurpose
cn, descriptionGroup labels and search.
nrfDynamicMemberDynamic group membership metadata.
nrfAssociatedRolesRoles associated with the group.
nrfAssignedResourcesResources associated with the group.
ownerGroup ownership display and filters.

LDAP clients often treat Simple Paged Results and VLV response sizes as membership counts. For that reason, query.default-count defaults to exact, and the LDAP channel inherits it. A client that does not need a count can send the eDirectory disable-count control.

Keep REST, GraphQL, and MCP at their channel defaults unless callers require exact totals by default:

query.default-count = "exact"
channels.rest.default-count = "estimated"
channels.graphql.default-count = "estimated"
channels.mcp.default-count = "estimated"

Use a channel override when one integration needs different behavior:

channels.ldap.default-count = "estimated"
channels.identity-hub.default-count = "exact"