{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":29664,"path":"it-operations-management/discovery/gcp-certificate-discovery-pattern.md","title":"GCP Certificate Manager discovery","bundle":null,"doc_type":null,"release":"australia","body":"\n# GCP Certificate Manager discovery\n\nCloud Discovery uses Patterns to discover certificate data that the GCP Certificate Manager manages. Discovering this data requires installing and updating Discovery and Service Mapping Patterns and Certificate Inventory and Management.\n\n## Request apps on the Store\n\nVisit the [ServiceNow Store](https://store.servicenow.com/sn_appstore_store.do#!/store/home) to view all the available apps, and for information about submitting requests to the store. For cumulative release notes information for all released apps, see the [ServiceNow Store version history release notes](https://www.servicenow.com/docs/r/store-release-notes/sn-store-release-notes.html).\n\n## Prerequisites\n\n- **Verify the configuration of an GCP account**\n\n For more information, see [Discovery for cloud environment](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery/cloud-discovery-wizard.md)\n\n- **Verify the installation of the plugins**\n\n Certificate Inventory and Management \\(sn\\_disco\\_certmgmt\\), at least 3.4.0\n\n Discovery and Service Mapping Patterns \\(sn\\_itom\\_pattern\\), at least 1.12.0\n\n- **Verify the configuration of the system property**\n\n When the system property **sn\\_itom\\_pattern.issuer\\_certificate\\_search\\_by\\_idn** is set to **False**, Discovery uses the certificate fingerprints to find issuers and root issuers.\n\n- **Verify the MID Server requirements**\n\n The MID Server must have either **ALL** capability or **GCP** capability.\n\n- **Verify the configuration of Cloud Discovery schedule**\n\n For more information, see [Create a discovery schedule in Cloud Discovery Workspace](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery/cloud-operations-disco-create-schedule.md)\n\n\n## Verify the REST API permissions\n\nDownload the [Cloud Discovery patterns spreadsheet](https://downloads.docs.servicenow.com/resource/enus/api/servicenow-discovery-patterns-api-details.xlsx) so you can grant user permissions required for running the Discovery patterns. In addition to permissions, the spreadsheet also includes useful information such as pattern names, types, CI Classes, and links to vendor documentation. New patterns are available quarterly, so check periodically to be sure you have the latest version of the spreadsheet.\n\n## Data collected by Discovery during horizontal discovery\n\nThe **Google Cloud Platform \\(GCP\\) - Certificate Manager Certificates** pattern and **Google Cloud Platform \\(GCP\\) - Classic Certificates** pattern support the discovery of the following table and fields.\n\n\n
\n\nField\n\n\n\nDescription\n\n
\n\nUnique Certificates \\[cmdb\\_ci\\_certificate\\] ​\n\n
\n\nName\n\n\n\nThe host name/domain associated with the certificate.\n\n For example, *\\*.service-now.com*\n\n
\n\nSerial Number\n\n\n\nThe serial number of the certificate. For example, *70 d8 c9 52 77 1c 2d 54 97 00 0e 21 05 84 dd 76 b5 e8 c1 73*\n\n
\n\nSubject common name\n\n\n\nThe host name/domain associated with the certificate. For example, *\\*.service-now.com*\n\n
\n\nSubject distinguished name\n\n\n\nThe distinguished name of the entity that the certificate is issued to.​\n\n The subject distinguished name consists of the following\n\n- Common name \\(CN\\).\n- Organization \\(O\\)- The organization that owns the domain that the certificate is issued to.\n- organizational unit \\(OU\\)- The organizational unit that owns the domain that the certificate is issued to.\n\n
\n\nIssuer common name\n\n\n\nThe common name of the certificate issuer. For example, Entrust Certification Authority.\n\n
\n\nIssuer distinguished name\n\n\n\nThe distinguished name of the certificate issuer.\n\n The issuer distinguished name consists of the following\n\n- Common Name \\(CN\\)- the authority that issued the certificate. For example, *Entrust Certification Authority*.\n- Organization \\(O\\)- The organization that issued the certificate. For example, *\"Entrust\", Inc*.\n- Organizational Unit \\(OU\\)- The unit that has the legal rights to issue the certificate.\n\n
\n\nRenewal tracking\n\n\n\nIndicates whether to create any priority 1 or priority 3 tasks for the expiring certificates.\n\n Discovery sets **Renewal tracking** to *priority3* when the system property *glide.discovery.certs.enable\\_renewal\\_task\\_creation\\_for\\_discovered\\_certificates* is set to **true**.\n\n
\n\nValid From\n\n\n\nThe certificate is valid from this date \\(UTC\\). For example, *2023-09-25 10:43:03*\n\n
\n\nValid To\n\n\n\nThe expiry date of the certificate \\(UTC\\). For example, 2024-09-24 10:43:03\n\n
\n\nSubject organization\n\n\n\nThe organization \\(O\\) that the certificate is issued to.\n\n
\n\nSubject organizational unit\n\n\n\nThe organizational unit \\(OU\\) that the certificate is issued to.\n\n
\n\nSubject country\n\n\n\nThe country \\(C\\) of the organization that the certificate is issued to. Populated in a two-letter country code.\n\n
\n\nSubject state\n\n\n\nThe region, state \\(ST\\), or province of the organization that the certificate is issued to. Populated with two-letter code.\n\n
\n\nSubject locality\n\n\n\nThe city, location \\(L\\) of the organization that the certificate is issued to.\n\n
\n\nSubject email\n\n\n\nThe email address of the organization that the certificate is issued to.\n\n
\n\nIssuer\n\n\n\nA reference to the entity that signed and issued the certificate. The reference is available if the issued certificate is a part of the same payload.\n\n
\n\nRoot Issuer\n\n\n\nA reference to the root certificate. The reference is available if the issued certificate is a part of the same payload.\n\n
\n\nSubject alternative name\n\n\n\nThe name of the certificate domain record.\n\n
## CI relationships\n\nThe **Google Cloud Platform \\(GCP\\) - Certificate Manager Certificates** pattern and **Google Cloud Platform \\(GCP\\) - Classic Certificates** pattern support the discovery of the following relationships:\n\n|CI|Relationship|CI|\n|---|------------|---|\n|Unique Certificate​ \\[cmdb\\_ci\\_certificate\\]|Hosts::Hosted on|Google Datacenter​ \\[cmdb\\_ci\\_google\\_datacenter\\]​|\n|Unique Certificate ​\\[cmdb\\_ci\\_certificate\\]​|Hosts::Hosted on|Cloud Service Account​ \\[cmdb\\_ci\\_cloud\\_service\\_account\\]​|\n|Key Value​ \\[cmdb\\_key\\_value\\]​|Reference​|Unique Certificate​ \\[cmdb\\_ci\\_certificate\\]​|\n\n**Parent Topic:**[Certificate Inventory and Management patterns](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/discovery/cert-invt-mgmt-patterns.md)\n\n"}}