Learn what to do if your Adobe licenses installed in the Keychain (on macOS) or Certificate Store (on Windows) show as not trusted.
Adobe apps require Signed Application Profiles, and during the process of obtaining these profiles, the necessary certificates for signature validation are installed in the Keychain on macOS and the Certificate Store on Windows.
Adobe licensing uses X.509, standards-compliant, DER certificates for licensing and entitlement. Adobe apps use these certificates to license software. These are part of the certificate trust chain, the root of which is self-signed. A self-signed certificate is an identity certificate signed by the same entity that is being certified.
While installing the certificates, only a portion of the certificates in the certificate trust chain is installed. The Root Certificate isn't installed. So, the certificates in the certificate trust chain show up in the Keychain and Certificate Store with these messages:
- Windows: Windows does not have enough information to verify this certificate
- macOS: Certificate isn’t trusted
This situation isn't a cause for concern, as Adobe apps use the certificates only for licensing purposes. Removing certificates has no adverse effect since they are reinstalled in the Keychain or Certificate Store during periodic iterations to obtain the Signed Application Profiles.
Adobe app doesn't have the required self-signed root certificate
The self-signed root certificate is available as a separate (optional) installable profile from Adobe. If you want, you can install the profile, which prompts for permission to install the self-signed root certificate system-wide and mark it as trusted. Once the self-signed root certificate is installed and marked as trusted, no more error messages are displayed for the certificates installed.
