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

Understanding the acme.sh data model wrt account email address #2970

Closed
pini-gh opened this issue May 30, 2020 · 3 comments
Closed

Understanding the acme.sh data model wrt account email address #2970

pini-gh opened this issue May 30, 2020 · 3 comments

Comments

@pini-gh
Copy link

pini-gh commented May 30, 2020

Hi,

This is not a bug report but a question to @Neilpang.

I'm trying to follow up on the initial work by @buchdag to use acme.sh instead of simp_le for letsencrypt-nginx-proxy-companion.
As I undertand it:

  • An acme.sh configuration directory is tied to one and only one email address
  • An acme.sh configuration directory can hold several accounts for different ACME service providers. These accounts are configured under <acme.sh_conf_dir>/ca/<service_provider_fqdn>.
    Then, say I want to update the email address for a given acme.sh configuration directory, I'd need to issue an acme.sh --update-account command for each configured ACME service provider. This command would look like:
acme.sh --update-account --server <service_provider_directory_url> --accountemail <new_email>

Is that correct? In this case it would be convenient to have the service provider directory url stored somewhere into the account configuration,to be able to script the above command. Would you mind me submitting a PR to this end?

In case my understanding stated above is not correct, please tell me.

Thanks in advance,

_g.

@auto-comment
Copy link

auto-comment bot commented May 30, 2020

If this is a bug report, please upgrade to the latest code and try again:
如果有 bug, 请先更新到最新版试试:
acme.sh --upgrade
please also provide the log with --debug 2.
同时请提供调试输出 --debug 2
see: https://github.com/acmesh-official/acme.sh/wiki/How-to-debug-acme.sh
Without --debug 2 log, your issue will NEVER get replied.
没有调试输出, 你的 issue 不会得到任何解答.

@Neilpang
Copy link
Member

Yes, correct.
But I won't accept the PR for just the case that you want to enumerate all the CA to update email.

@pini-gh
Copy link
Author

pini-gh commented May 31, 2020

Ack. Closing this issue as the question was answered.

@pini-gh pini-gh closed this as completed May 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants