Hi Slaughter,
I’m trying to catch up on the latest approach for “CA assisted DNS Validation”. As I understand it, an applicant can create a DNS TXT record that perpetually permits the CA to keep that domain validation up to date and there is no longer a need for a random value challenge to be used each time.
So, here is an example:
If a customer wants a CA (specificCA.com) to keep the domain example.com updated all the time, then they can create a DNS TXT record:
Record location: _validation-persist.example.com
Contents: TXT "specificCA.com; accounturi=https://example.com/acct/123"
Where 123 is the account value supplied by the CA to this applicant and it’s unique per applicant.
It’s up to the CA as to when this is checked – can be done at time of issuance, or within X days, where X is the current domain re-use period.
Do I have that right?
Thanks!
Doug
--
You received this message because you are subscribed to the Google Groups "Validation Subcommittee (CA/B Forum)" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
validation+...@groups.cabforum.org.
To view this discussion visit
https://groups.google.com/a/groups.cabforum.org/d/msgid/validation/d5f1bc0e-1799-4f10-9fa9-1ac00ece9a49n%40groups.cabforum.org.
Hi Doug,
The content of the TXT would be in the form of:
" specificCA.com; accounturi=https://specificCA.com/account/123"
Where specificCA.com is the CA and the accounturi: “https://specificCA.com/account/123” represents a unique applicant for specificCA.com.
> It’s up to the CA as to when this is checked – can be done at time of issuance, or within X days, where X is the current domain re-use period.
Like all other DCV methods, this method must be performed prior to certificate issuance to verify control of the domain by the Applicant.
The re-use period of that successful DCV for subsequent certificate issuances however is limited to the TTL of the TXT record or 8 hours (whichever is greater). This re-use period also SHALL not exceed the validation reuse period specified in section 4.2.1.
Hope that helps,
Slaughter