Managing tickets for expiring certificates

Status update for tickets

Concert is designed to manage certificates within your application's ecosystem. Ticket status updates are supported for tickets that are created in GitHub, Jira, Salesforce, and ServiceNow. After certificates are renewed, new certificate details are added to Concert. You can bring in new certificate details to Concert by CSV uploads, JSON uploads, or import through ingestion from an environment namespace. Refer to uploading certificate details section for details steps.

Concert can identify the renewed certificates by comparing end points. Concert replaces old certificates with new ones and also close any open tickets that are associated to the updated certificates. The status of new certificates is reflected as 'Valid' and expired certificates will be archived.

Status for grouped ticket

You can have automation rules that are created for ticket creation for certificate expiry. In case of multiple certificate expires, instead of creating ticket for each certificate, Concert will group tickets by certificate issuing authority or expiry date, and create one ticket for a group of certificates.

Once you renew or replace expiring certificates, upload a new file to Concert containing updated certificate data. Concert reviews the contents of the updated file and automatically close tickets that are created in your third-party ticketing system if all certificates mentioned in that ticket are updated. If only some of the certificates that are mentioned in the ticket are resolved, Concert adds a comment in the ticket providing details about which certificates no longer require action.

For grouped tickets if all the certificates are updated and the details are loaded into Concert, Concert closes such group tickets.