Support Let's Encrypt Profile in New Order

[campersau]

Let's Encrypt added a new "profile" parameter to the "new-order" endpoint. It would be great if this could be added here as well.
E.g. "profile": "tlsserver"

Full example:

POST /acme/new-order HTTP/1.1
Host: example.com
Content-Type: application/jose+json

{
    "protected": base64url(...),
    "payload": base64url({
        "profile": "tlsserver",
        "identifiers": [
            { "type": "dns", "value": "www.example.org" },
            { "type": "dns", "value": "example.org" }
        ],
    }),
    "signature": "H6ZXtGjTZyUnPeKn...wEA4TklBdh3e454g"
}

See https://letsencrypt.org/2025/01/09/acme-profiles/

[pablopioli]

It appears this project is abandoned. I have been maintaining my own fork adding changes in https://github.com/pablopioli/certes
This should be feasible, would you like to help test it?

[pablopioli]

Found trivial to add support, I added the value as optional in
pablopioli@678678a

It is not compiled in the nuget package for now

[webprofusion-chrisc]

See also https://github.com/webprofusion/anvil as used by Certify The Web, it includes some experimental/draft ACME extensions etc (ARI, profile support etc). It's not really supported as a community fork etc but it's maintained for the purposes of our own app and feature experiments. Technically these things are not yet part of ACME.

[pablopioli]

I see the changes are essentially the same
webprofusion/anvil@6718681#diff-bbdaa9e4bcc3bba1a9e5460f27cd55c0dec6b36223eac976fe115e7c34232a23

As using Anvil: until some big change happens I will update my fork, as my use case is basically similar to "primarily used by https://certifytheweb.com/ and is subject to changes required by that application."