Change default solver method for wildcard domains about acmephp HOT 9 CLOSED

I don't think resolver should be DNS by default when wildcard identifier occur.
It is a mechanism of letsencrypt, doesn't mean it's an ACME mechanism.

from acmephp.

Thanks for the feedback!

If you are interested by doing a PR on this, don't hesitate to ping me here or on the Symfony Slack: I'd be glad to help :) .

from acmephp.

How do you validate wildcard domains using run command command?

In my case all the sub-domains lead to same document root so http-file would also work, but instead I also get same This ACME server does not expose supported challenge. error.

from acmephp.

You have to use a DNS solver.
For now only AWS Route53 is implented

from acmephp.

Theoretically \AcmePhp\Core\Challenge\Dns\SimpleDnsSolver (activated via solver: dns config file line) should also work, but I'm not sure if it will actually wait during run command execution for me to change DNS?

Will it?

from acmephp.

I'm using Gandi.Net. It has API (see http://doc.livedns.gandi.net/) were you can:

1. create new zone file version based on existing zone file
2. add needed entries for validation to it
3. switch to new zone file version
4. after validation is done switch back to old zone file version
5. drop new zone file version created for validation only

from acmephp.

Sounds 5. Could you please submit a Pull Request?

from acmephp.

I probably could, but I wonder how do I test that. In the test suite I haven't found examples of DNS solver test classes.

Also maybe you can point me to the correct test case where I can see how challenge fixtures are used. Generating certificates right on Let's Encrypt just to test how it works sounds like a terrible idea.

from acmephp.

@jderusse , PR created: #162

from acmephp.