Closed Bug 1111318 Opened 10 years ago Closed 10 years ago

update Kount certificate

Categories

(Webmaker Graveyard :: DevOps, defect, P1)

x86
macOS
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: davida, Assigned: johns)

Details

Geoffrey emails:


---------- Forwarded message ----------
From: Kount Support <custserv@kount.com>
Date: Sat, Dec 13, 2014 at 10:00 AM
Subject: Kount RIS Certificate - Expiration Notice, Immediate Action
Required: Merchant ID #132500
To: Geoffrey MacDougall <geoffrey@mozillafoundation.org>, Aaron
Chesley <ajc@kount.com>, Seth Reznik <seth@bluestatedigital.com>
Cc: Kount Support <custserv@kount.com>


Dear Kount User:

On 2014-12-20 11:50:12, the RIS Certificate, mozilla_prod, #12236885d0
for your merchant ID #132500 will expire.  To update your certificate,
simply request a new certificate by accessing the Admin tab of the
Kount AWC and select RIS Certificates.

If a new RIS Certificate is not in place on the expiration date, Kount
will not be able to receive your data transmission, which could cause
an outage of your fraud coverage.

If you have already created and exported a new certificate, be advised
you will continue to receive these notifications regarding the
certificate referenced above, until the listed expiration date or
until the certificate has been revoked.

If you have any questions, please contact us by emailing
custserv@kount.com or by calling 888-880-2585.

Thank you,
Kount
Priority: -- → P1
We've verified with BSD that this is already complete, and we received the message due to the old cert not yet having been revoked.

------
Seth Reznik
9:01 AM (1 hour ago)

to Aaron, JP, Geoffrey 
I spoke to my team here and this is in reference to the old cert, so it can be ignored. The new cert (which is in place) has a new ID etc. and is good to go.

-----------
Aaron J Chesley
9:42 AM (23 minutes ago)

to Seth, JP, Geoffrey 
Seth is correct.
 
I have revoked the old certificate so this message will not be sent again.
 
Aaron
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.