Skip to content
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

Open
JLWade opened this issue Feb 22, 2024 · 7 comments
Open

Update API keys for GC Notify in DUP by march 6th #347

JLWade opened this issue Feb 22, 2024 · 7 comments
Assignees

Comments

@JLWade
Copy link

JLWade commented Feb 22, 2024

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:

  • api keys for GC notify are updating appropriately and emails for confirmations and reminders are working correctly, and sms messages for reminders are sending correctly
  • smoke test in prod for notifications and no issues

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.

@JLWade JLWade converted this from a draft issue Feb 22, 2024
@JLWade JLWade changed the title Update API keys for GC Notify in DUP Update API keys for GC Notify in DUP by march 6th Feb 22, 2024
@Christopher-walsh22 Christopher-walsh22 self-assigned this Feb 22, 2024
@Christopher-walsh22 Christopher-walsh22 removed their assignment Feb 22, 2024
@Christopher-walsh22
Copy link
Contributor

I have updated the API keys to the new format in DEV and TEST. After confirmation from Manuji I will recreate in PROD

@manuji
Copy link

manuji commented Feb 23, 2024

Tested on TEST: Passed

  • Verified that the emails and SMS were received correctly.
  • Assigning back to Chris to make the changes on the PROD

@JLWade
Copy link
Author

JLWade commented Feb 29, 2024

Awesome getting this through! Hope we can have these changes made either today or early next week to meet that marhc 6th deadline.

@manuji
Copy link

manuji commented Feb 29, 2024

@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).

@JLWade
Copy link
Author

JLWade commented Feb 29, 2024

amazing!

@manuji
Copy link

manuji commented Feb 29, 2024

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.

@JLWade
Copy link
Author

JLWade commented Mar 1, 2024

moving to done

@JLWade JLWade moved this from PO Review to Done in BC Parks Digital Delivery (Team Osprey) Mar 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

3 participants