It's 2018. Where are mah wildcards bro?


#1

So it’s 2018, and I can’t seem to request a wildcard certificate. I’ve done a sudo apt-get update && sudo apt-get upgrade -y but it seems that there is nothing :frowning:

Maybe it’s because I’m living in the future? It sucks that there isn’t a specific date for the update release - just a mere ‘January 2018’.


#2

There’s some more specific information as of December 7.


#3

Oops. I must be blind.

So I just have to wait until January 4th. I’ll be counting down the days…

By the way, thank you.


#4

Indeed you will have to wait till 27th February.


#5

“a public test API endpoint up by January 4”

Does this not mean that I can start using it by January 4th?


#6

It means there will be a staging server for the ACME v2 protocol.

You will only be able to issue certificates for a staging CA, which is not trusted by browsers.


#7

Aw.

Thanks for clearing that up, though.


#8

interesting title and attitudes


#9

Dun, dun, dunnnnnn.

Whoopidy dooo.


#10

let the testing begin…

well soon :slight_smile:


#11

Yes.

Should be fun. Can’t wait for the official release!


#12

already get staging wildcard cert for:

*.tensorsdata.com
*.testing.tensorsdata.com
tensorsdata.com

deploy on:

https://testing.tensorsdata.com:5443


#13

Looking delicious there.


#14

Hi @fengjiajie,

I can confirm you’re officially the first external user to issue a wildcard certificate from the V2 staging API :tada::lock::tada:

Out of curiosity, which ACME client did you use for this? Did you add your verification TXTs by hand?


#15

So excited to know that.:crazy_face::crazy_face::crazy_face:

I used acme4j which mentioned in Staging endpoint for ACME v2.

It is very very cool, thank you LE team. I refreshed github boulder API V2 project every few hours.


#16

Yes, I add TXTs by hand.


#17

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.