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

fix(application-generic): Allow unauthorized certs for bridge url #6717

Merged
merged 1 commit into from
Oct 19, 2024

Conversation

SokratisVidros
Copy link
Contributor

What changed? Why was the change needed?

Reject self-signed and invalid certificates in Production environments but allow them in Development as it's common for developers to use self-signed certificates in local environments.

Screenshots

Screenshot 2024-10-18 at 00 06 21

Copy link

netlify bot commented Oct 17, 2024

Deploy Preview for novu-stg-vite-dashboard-poc ready!

Name Link
🔨 Latest commit 74cf782
🔍 Latest deploy log https://app.netlify.com/sites/novu-stg-vite-dashboard-poc/deploys/6713b1d9347e0b00081edb94
😎 Deploy Preview https://deploy-preview-6717--novu-stg-vite-dashboard-poc.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

// Test that the update button is enabled again when the form value changes
await senderName.fill('Novu edited');
await expect(updateButton).toBeEnabled();

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this change intended? It seems unrelated to the PR title

Copy link
Contributor

@rifont rifont left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

My only question is: what does the API response look like when attempting to use a self-signed certificate in Prod? We should make sure it's not a 5xx error.

@SokratisVidros SokratisVidros force-pushed the allow_unauthorized_certs_for_bridge_url branch from 6ea4c79 to 060dac7 Compare October 19, 2024 12:42
@SokratisVidros SokratisVidros changed the base branch from next to fix-v2-versioning October 19, 2024 12:43
@SokratisVidros SokratisVidros requested a review from a team as a code owner October 19, 2024 12:43
@SokratisVidros SokratisVidros requested review from scopsy and merrcury and removed request for a team October 19, 2024 12:43
@SokratisVidros SokratisVidros changed the base branch from fix-v2-versioning to next October 19, 2024 12:43
…ment

 Reject self-signed and invalid certificates in Production environments but allow them in Development as it's common for developers to use self-signed certificates in local environments.
@SokratisVidros
Copy link
Contributor Author

Looks good!

My only question is: what does the API response look like when attempting to use a self-signed certificate in Prod? We should make sure it's not a 5xx error.

Screenshot 2024-10-19 at 16 18 38

@SokratisVidros SokratisVidros merged commit 143dfce into next Oct 19, 2024
30 checks passed
@SokratisVidros SokratisVidros deleted the allow_unauthorized_certs_for_bridge_url branch October 19, 2024 13:56
* Reject self-signed and invalid certificates in Production environments but allow them in Development
* as it's common for developers to use self-signed certificates in local environments.
*/
rejectUnauthorized: true,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@SokratisVidros the new error response looks great! One thing though - you forgot to revert the change here to check Environement.name after testing

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

😮‍💨 Fixed on next. Thanks for noticing. That's what happens if you are committing code in between Duplo gaming sessions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants