The automountkey-find currently doesn't have a --pkey-only option which is necessary to provide paging functionality. The primary key consists of 2 attributes: automountkey and automountinformation, both should be returned by this option.
In the LDAP server the entries are stored using the description attribute (which contains the key and info) as the RDN. For example:
dn: description=/- auto.direct,...
A better solution would be to use a composite RDN:
dn: automountinformation=auto.direct+automountkey=/-,...
This way the description attribute can be used more properly to store a note describing this particular entry.
From UI perspective either of these solutions would be fine:
Return the key and info in separate attributes:
{ "automountinformation": [ "auto.direct" ], "automountkey": [ "/-" ], "dn": "description=/- auto.direct,...", }
Return the key and info concatenated into a single value, provided the delimiter (i.e. the space) in both key and info is escaped properly to avoid parsing problem.
{ "description": [ "/- auto.direct" ], "dn": "description=/- auto.direct,...", }
This will be fixed in the UI. Adding --pkey-only option wouldn't provide much benefits because there isn't much info in automount key other than the primary keys themselves. The UI will use a regular automountkey-find command to get the entire data (including primary keys) and use it to calculate the page.
master: - 7c0c395 ipa-2-2: - c92309f
Metadata Update from @edewata: - Issue assigned to edewata - Issue set to the milestone: FreeIPA 2.2 Core Effort - 2012/01
Login to comment on this ticket.