we are a very large university (ethz.ch) with all the de-centralized system-administration that comes with such an environment. At the moment we are constantly hitting the issue rate-limit (50+ up to 180+ new requests per week). After looking at the rate-limit adjustment documentation I still have some questions.
The rate-limit adjustments are linked to an account ID. That ID has an account-secret (key). This means we can't publish that info it inside our organization (10k employees and 40k students, published info is not a secret anymore). What happens if a certbot is asking for an ethz.ch certificate without the account ID that has the increased rate-limit approval? Will the request be denied? Will the request go on with the default rate-limits?
What strategy would you guys recommend for such an organization? How can we increase the rate-limit without being bound to an un-shareable secret?
Thank you and best regards,