-
-
Notifications
You must be signed in to change notification settings - Fork 246
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support custom ACME servers #186
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
As far as I'm aware this would still be a good idea |
+1 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Still a thing |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Is there a way we can keep this open without having to comment every month? As far as I'm aware this is still a thing and several people are interested. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Tagged as |
Thank you |
Hi guys! How can we get this merged? |
If #371 is rebased it can be re-reviwed and likely merged. |
Hello! I've recreated PR, could anybody look at it? |
Desired Behavior
Currently SWAG supports ZeroSSL and Let's Encrypt, that covers most of the situations, however there are more organizations starting to use internal ACME providers such as Step CA. SWAG should be able to use at least a basic custom provider url
Example
Current Behavior
Only two predefined ACME providers
Alternatives Considered
Maintaining a custom fork of SWAG
The text was updated successfully, but these errors were encountered: