Alan King

So... I have a rough proof of concept for how this could be implemented. Writing it here for posterity. Here's the rule (NREP) for checking whether the resource is archive...

I think that the situation would occur any time the pre-PEP for the "unregistered" resource plugin operation returns an error. I'm not sure that any resource plugin has implemented any...

This issue was inspired by a need for a test wherein `irepl -a` updates a replica which is in a cache resource in a compound resource hierarchy and testing to...

I don't think this is a refactor as a behavioral change is being proposed... Seems more like a bug to me as the expected behavior does not match the observed...

The rename operation does not currently exist for hierarchy resolution. This will need to be added before the keyword for the context string of a weighted passthru resource.

Also... rename does not resolve a hierarchy because it is a logical operation and so just renames all the replicas regardless.

I could see the argument for both updating pam_password and not updating pam_password in favor of implementing this with pam_interactive. Hmm...

Recursive actions in `ichmod` (as well as many others) are handled on the server side of the API call, which is why the API PEP only fires once. In order...

Oh, missed that bit about the database PEP. Got it

If Metalnx or Jargon have some way of passing a value for the Time To Live (TTL) for the PAM authentication calls, that would be the preferred approach, I think....