Date: Fri, 29 Mar 2024 15:05:35 +0000 (UTC) Message-ID: <1882847361.8141.1711724735154@ip-10-10-7-29.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_8140_1853612901.1711724735153" ------=_Part_8140_1853612901.1711724735153 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Once your campus has subscribed to the Certificate Service = and appointed Registration Authority Officer(s) (RAO), InCommon must valida= te each domain =E2=80=94 that is, domain control must be demonstrated =E2= =80=94 before issuing certificates. This is called Domain Control Validatio= n =E2=80=94 please read the DCV = documentation.
This process determines whether there is a reasonable ownership connecti= on between the organization listed in WhoIs and the organization requesting= the domain for certificate issuance. Because the Certificate Service is av= ailable only to U.S. higher education institutions, an insufficient connect= ion will result in rejected domains. This determination is made at the sole= discretion of InCommon. Here is a guide that InCommon uses for permit= ted non-Fully Qualified Domain Name (FQDN) entries.
Note about how to submit your base dom= ains
IMPORTANT: You should be sure to not only submit your b= ase domain (e.g. campus.edu), but you should also submit the wildcard of yo= ur base domain (e.g. *.campus.edu). This will enable you to do DCV once and= have all of your sub-domains covered (sports.campus.edu, business.campus.e= du, etc), rather than having to complete DCV separately for each sub-domain= .