use case for this feature
Michael.Paoli:
testing, notably to (re)test/(re)validate and create authorizations. E.g. withcertbot certonly --manual --manual-auth-hook authprog --manual-cleanup-hook cleanup prog
enhanced security - deactivating the authorization (moderately, at least) enhances security, by disallowing reuse of the existing authorization - thus requiring the authorization steps to need to be completed (again) before (re)issuing certificate, etc. - it's potentially an additional safeguard/control. Without being able to deactivate authorization, account authentication alone is sufficient to get cert(s) (re)issued for same domain(s).
not familiair with these "many" requests
I found quite a bit in related suggestions/requests/discussion, etc. earlier - didn't save all the links and such. But searching bit again (alas, not quite the search I had earlier, and not quite same results), even just on community.letsencryt.org it does come up semi-regularly, e.g.:Deactivate authorization Flush of authorization cache DNS-01, TTL and deactivating authorizations Authorization deactivation - #3 by serverco
Certbot isn't developed by Let's Encrypt, but by the EFF. Please see the Certbot Github repo
Okay, thanks, I'll have another look around there. When I was looking earlier didn't easily spot an particular pointers for "feature requests" or the like, but I'll have another look.