Skip to content

Commit a8bb0a4

Browse files
author
Rand McKinney
committed
Fix incorrect info re certs
1 parent fbeec1c commit a8bb0a4

File tree

2 files changed

+2
-14
lines changed

2 files changed

+2
-14
lines changed

docs/getting-started.mdx

Lines changed: 0 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -108,13 +108,6 @@ The above list is for reference only; inclusion does not imply endorsement by CA
108108

109109
When you purchase a certificate, you must select at least one of the extended key usage (EKU) fields that specify what the certificate can be used for: **email protection** and **document signing**. Applications that use the CAI SDK won't accept the certificate unless it has one of these EKUs.
110110

111-
Certificate authorities offer many levels of validation. For Content Credentials, one of these types is highly recommended (though not required):
112-
113-
- **Organization Validated (OV).** The CA validates the organization's identity by checking its credentials against extensive databases, including those held by local governments.
114-
- **Extended Validation (EV).** A fully authenticated certificate, needed to offer secure web locations, email, and financial transactions.
115-
116-
If you don't get an OV certificate, then the Content Credentials that use the certificate won't display your organization name, as shown in the examples on [verify.contentauthenticity.org](https://verify.contentauthenticity.org/).
117-
118111
### Extracting the certificate
119112

120113
To work with the certificate, you need to extract it. When the CAI SDK adds Content Credentials to an asset, it incorporates the certificate (including the associated public key) into the manifest.

docs/prod-cert.mdx

Lines changed: 2 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -34,14 +34,9 @@ CAs offer a variety of different kinds of certificates (links below are to [Digi
3434
- The simplest and least expensive option is an [S/MIME email certificate](https://www.digicert.com/tls-ssl/compare-secure-email-smime-certificates).
3535
- Other options, such as [document signing certificate](https://www.digicert.com/signing/compare-document-signing-certificates) require more rigor (like proving your identity) and cost more.
3636

37-
### CA validation
37+
### Organization name
3838

39-
CAs offer many levels of validation. For Content Credentials, one of these types is highly recommended (though not required):
40-
41-
- **Organization Validated (OV).** The CA validates the organization's identity by checking its credentials against extensive databases, including those held by local governments.
42-
- **Extended Validation (EV).** A fully authenticated certificate, needed to offer secure web locations, email, and financial transactions.
43-
44-
If you don't get an OV certificate, then the C2PA [Verify tool](https://verify.contentauthenticity.org/) won't display your organization name in the Content Credentials.
39+
If you want the C2PA [Verify tool](https://verify.contentauthenticity.org/) to display your organization name in the Content Credentials, your certificate must include the "O" or [Organization Name attribute OID value: 2.5.4.10](https://www.alvestrand.no/objectid/2.5.4.10.html) in the Distinguished Name information. The CA may require some validation steps to prove you are part of that organization (details vary by CA).
4540

4641
## The C2PA Python example
4742

0 commit comments

Comments
 (0)