fabriziosalmi/certmate

Nothing is broken today. CertMate v2.26.0 issues and renews through Azure DNS exactly as it always has. This is about an upgrade we want to make next, and one provider stands in the way of it. React with a thumbs up if you use Azure DNS with CertMate That is the whole ask. A 👍 on this issue is enough — no comment needed. If you want to add one line about your setup (single zone or several, wildcards or not, how many certificates), that helps more, but the count is what we are missing. Why we are asking CertMate pins certbot==2.10.0. That pin is now carrying four cryptography security advisories that cannot be fixed while it holds: every version that fixes them needs a pyOpenSSL that breaks this certbot at import. None of the four is reachable in CertMate's code — we checked each one and wrote the analysis down in SECURITY.md — but carrying advisories forever is not a plan. Moving to a current certbot fixes all four. We measured the whole migration this week (#103): the stack r

This is for a discussion/brainstorming on webhook deployment options I raised on #207 A question was presented about how does this get stored/saved so it can be executed saved. The way I see it is there are really only 2 ways. values in a DB/config that are dynamically generated on execution. Builds a script and saves it. Webhooks have 3 componets: Request Method & URL Request Headers Request Body To make it easy to parse and edit in the URL, and have a common calling function, we could use a JSON config file like so: [ { "name": "Slack Notifications", "endpoint_url": "https://slack.com", "method": "POST", "headers": { "Content-Type": "application/json" }, "payload_template": { "text": "Event {{event}} triggered." } }, { "name": "Customer CRM Sync", "endpoint_url": "https://hubspot.com", "method": "POST", "headers": { "Content-Type": "application/json", "Authorization": "Bearer {{token}}" }, "payload_template": { "conta

Is your feature request related to a problem? No. Describe the solution you'd like I would like to be add an LDAP/AD identity source, handle filter option for groups. The identity provider would make a regular sync and keep the users locally but use authentication against of the LDAP/AD. Describe alternatives you've considered No. Additional context Many other tool has proper settings for it. I don't want to give you full implementation details. BTW I will seperatedly create another feature requst for SSO/OIDC.