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

[management] SMTP TLS negotiation error #6101

Closed
gcusnieux opened this issue Sep 6, 2021 · 4 comments
Closed

[management] SMTP TLS negotiation error #6101

gcusnieux opened this issue Sep 6, 2021 · 4 comments

Comments

@gcusnieux
Copy link
Member

OpenJDK 11.0.11 disable TLS 1.0 and 1.1 for security reasons.

We have an error when APIM try to use smtp connection to send an email

How to reproduce:

  • Configure your env wih OpenJDK 11.0.11
  • Configure email with fake-smtp-server or gmail
  • Try to register as a new user to portal
@erickbeloti
Copy link

Hi, in version 3.11.1 the error still occurs

gcusnieux added a commit to gravitee-io/old-gravitee-api-management that referenced this issue Sep 28, 2021
gcusnieux added a commit to gravitee-io/old-gravitee-api-management that referenced this issue Sep 28, 2021
This was referenced Sep 28, 2021
@gcusnieux
Copy link
Member Author

gcusnieux commented Sep 28, 2021

Hello @erickbeloti, this will be fixed in versions 3.12 (to be released in the next few days), 3.10.4 and 3.5.19

@phiz71 phiz71 modified the milestones: APIM - 3.12.0, APIM - 3.5.19 Sep 29, 2021
@phiz71
Copy link
Member

phiz71 commented Sep 29, 2021

Sorry, but the fix is not good. So we will not include it in the 3.12.0, which will be released today or tomorrow I think.
This ticket is our next priority.

phiz71 added a commit to gravitee-io/old-gravitee-api-management that referenced this issue Oct 2, 2021
phiz71 added a commit to gravitee-io/old-gravitee-api-management that referenced this issue Oct 2, 2021
ytvnr pushed a commit to gravitee-io/old-gravitee-api-management that referenced this issue Oct 4, 2021
@erickbeloti
Copy link

Hi,

Just to comment that in version 3.12.1 this bug is completely fixed.

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

No branches or pull requests

6 participants