Thomas Ottenhus

@mcnaugha we established the missing forwarding as headers to be a problem here. The attached build allows you to use a forward proxy. Add something like this to your appsettings.json:...

I shouldn't have done it tired yesterday .... During the current rebuilding of the server, I added more identifiers that are supported and forgot to allow hardware-module and persistent-identifier to...

I think the Forwarded headers take "allowed hosts" from the generic config section, since the latter one is AFAIR independend of the ForwardedHeaders Module, but I would have to validate...

Ah - we're getting somewhere - it now discarded the order, since it was not able to create all necessary challenges - that's something I cannot create a testcase currently,...

There's the first payload i've been looking for - it contains the response from the apple device :) Thanks a lot so far - I've now to dissect it and...

@mcnaugha I looked into the challenge payload, that the order contained and I have to say it's a little confusing. It contains an attObj, as it should and inside there's...

Good morning, you're probably right - it would be easier to have a machine on my end - at least to collect the data to go forward. But currently I...

I extracted the Certificate and put it in openssl - what I see is the Phone Model and OS Version, but the attestation itself is missing. ``` X509v3 extensions: X509v3...

I've not tested it with win-acme, yet. But, I'll can do next Werk. Could be interesting to see the logs of the acme server, though - could you provide them?

I was able to take a look into the issue with WACS. Assume your ACME-Server name be "acme.th11s.corp". If you put that into the WACS settings (e.g. https://acme.th11s.corp), it'll try...