1 Answer
- Newest
- Most votes
- Most comments
0
The answer turned out to be my use of outdated jars. When I updated to more modern libraries, it started using proper TLSv1.2
answered 3 years ago
Relevant content
- asked 2 years ago
- asked 7 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago