Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2233587

Summary: [RFE]: Provide a notification 7/30/60 days prior to manifest certificate expiration
Product: Red Hat Satellite Reporter: Taft Sanders <tasander>
Component: Subscription ManagementAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.14.0CC: jlenz, rlavi
Target Milestone: UnspecifiedKeywords: FutureFeature
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-08-28 18:49:29 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Taft Sanders 2023-08-22 16:01:47 UTC
Description of problem:
As a customer, I would like to be notified via email or notifications drawer on the Satellite when the manifest (not the subscriptions attached to the manifest) is expiring on 7, 30, and 60 days prior.

Version-Release number of selected component (if applicable):
satellite-6.14

How reproducible:
n/a

Steps to Reproduce:
1. n/a
2.
3.

Actual results:
No notification currently exists

Expected results:
- Pull the expiration date of the manifest upstream consumer certificate expiration date via API

and/or

- Receive email alerts 7,30, and 60 days prior to the manifest upstream consumer certificate prior to expiring.

and/or

- See notifications in the notification drawer 7,30, and 60 days prior to the manifest upstream consumer certificate prior to expiring.

Additional info:
The certificate in question is located in the manifest download bundle:
↪ cat export/upstream_consumer/1406625066595009049.json | jq
{
  "created": "2023-06-07T02:53:59.000+00:00",
  "updated": "2023-06-07T02:53:59.000+00:00",
  "id": "2c94bf3688732944018893c67f943593",
  "key": "-----BEGIN PRIVATE KEY-----\nMIIJQgIBADANBgkqhkiG9w0BAQEFAASCCSwwggkoAgEAAoICAQC4zRjvJHdh4nC3\nO4z27enykUcdgFgez6
                     --snip--
aVwhJRyj08w==\n-----END PRIVATE KEY-----\n",
  "serial": {
    "created": "2023-06-07T02:53:58.000+00:00",
    "updated": "2023-06-07T02:53:58.000+00:00",
    "id": 1406625066595009049,
    "serial": 1406625066595009049,
    "expiration": "2024-06-07T02:53:58.000+00:00", #<<<<<<<<<<<<<<<<<<<<<<<<<THIS EXPIRATION HERE
    "revoked": false,
    "collected": false
  },
  "cert": "-----BEGIN CERTIFICATE-----\nMIIGVDCCBDygAwIBAgIIE4VWC6KOQhkwDQYJKoZIhvcNAQELBQAwgaQxCzAJBgNV\nBAYTAlVTMRcwFQYDVQ
                    --snip--
LSMJnQ==\n-----END CERTIFICATE-----\n"
}

Comment 1 Jeremy Lenz 2023-08-28 18:49:29 UTC

*** This bug has been marked as a duplicate of bug 2075163 ***