Eugene Bekker

Hmm, the second registration should not have clobbered the first (in theory) -- there are checks in place to prevent that, will need to check on that... Fortunately, it sounds...

Ah, I see the issue. You need to take a look at the most recent few comments in #165. You may also find the [Reference Sheet](https://github.com/ebekker/ACMESharp/wiki/Let%27s-Encrypt-Reference-Sheet) useful.

Yes, you are correct, you need to re-authorize Identifiers on a recurring basis.

The only reason to "reuse" a vault is if you want to keep all the related entities (Registration, Identifiers, Authorizations, Certificates) under one umbrella, but if you don't care about...

Right now the one I'm working on is backed by Firebase. The next one will be backed by EF Core, so you can host that one by using any supported...

I agree -- SQL Server backend would be overkill, but by writing to EF Core, you can target any supported relational DB provider ([SQLite](https://docs.microsoft.com/en-us/ef/core/providers/sqlite/)) or even NoSQL DB in the...

This is not an error, this is by design, please see the last question in the [FAQ](https://github.com/ebekker/ACMESharp/wiki/FAQ).

Duplicate of #185.

The current release requires you to create a new alias for each new cert request. The upcoming release, 0.8.2 has added support for renaming/deleting aliases so you could reuse a...

Are you saying you got the unresolved DNS name error when you specified an invalid "Identifier Alias"?