Skip to content
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

Add support of several accouts for GoDaddy provider #610

Open
hubaksis opened this issue Jul 26, 2023 · 3 comments
Open

Add support of several accouts for GoDaddy provider #610

hubaksis opened this issue Jul 26, 2023 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@hubaksis
Copy link

Feature request.
I need to update several different certificates for my clients. They manage their domains by themselves, but they provided me with their API credentials, so I can issue certificates for them. Right now there is no support for multiple GoDaddy providers with different credentials.

Possible solution:
Add support for multiple DNS providers (for my case - GoDaddy).
Add a new app settings 'GoDaddys', which have json in the format {["ApiKey":"a1", "ApiSecret":"s1"], ["ApiKey":"a2", "ApiSecret":"s2"]}

Possible workarounds (alternatives)
Create multiple instances of the app to be able to support multiple credentials

@hubaksis hubaksis added the enhancement New feature or request label Jul 26, 2023
@webprofusion-chrisc

This comment was marked as off-topic.

@hubaksis
Copy link
Author

I presume you just need to manage multiple certs across different domains/dns providers and push them all to keyvault? The reason I ask it it seems more practical to perhaps just use a different ACME client with keyvault support.

Multiple domains across different DNS providers is already implemented (as I can see, but I haven't used it), however multiple domains across multiple accounts in one DNS provides is not.
Creating a different ACME client is a possible workaround (as I mentioned in the first message), but it will be tricky in terms of management.

@shibayan
Copy link
Owner

While we recommend deploying Azure Functions on a customer-by-customer basis from the standpoint of separating credentials and privileges, we understand that there are problems with the current DNS Provider setup.

We would like to improve this method to be more scalable in the future.

@shibayan shibayan added this to the Backlog milestone Aug 18, 2023
@shibayan shibayan modified the milestones: Backlog, v5.0.0 Release Apr 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants