-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update API keys for GC Notify in DUP by march 6th #347
Comments
I have updated the API keys to the new format in DEV and TEST. After confirmation from Manuji I will recreate in PROD |
Tested on TEST: Passed
|
Awesome getting this through! Hope we can have these changes made either today or early next week to meet that marhc 6th deadline. |
@JLWade we have already done it on PROD as well. I am waiting to verify it on PROD tomorrow (as the passes are only required for the weekend). |
amazing! |
I reserved a pass for Saturday and I got the confirmation email successfully. We can move this ticket along and I will open if something goas wrong with the reminder SMS and email. |
moving to done |
GC Notify is requiring an update to the api keys they are using to process email and sms notifications used in all applications, including DUP. This ticket is to make that update.
AC:
notes:
From GC Notify: To enhance security, starting March 6, 2024, we’ll require the entire API key for every API call. If you send only 36 characters or a partial key, you’ll get a 403 error message and your job will fail.
A full key starts with “gcntfy”. If you no longer know your full key, you must create a new one.
Include the entire API key in the HTTP header when calling the API. For more information, read our API documentation.
The text was updated successfully, but these errors were encountered: