-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Conversation
✅ Deploy Preview for novu-stg-vite-dashboard-poc ready!
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(); | ||
|
There was a problem hiding this comment.
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
libs/application-generic/src/usecases/execute-bridge-request/execute-bridge-request.usecase.ts
Outdated
Show resolved
Hide resolved
There was a problem hiding this 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.
6ea4c79
to
060dac7
Compare
…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.
060dac7
to
74cf782
Compare
* 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, |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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.
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