[JAVA-3386] Add Java driver example of forcing TLS 1.2 Created: 16/Aug/19  Updated: 28/Oct/23  Resolved: 13/Nov/19

Status: Closed
Project: Java Driver
Component/s: Documentation
Affects Version/s: None
Fix Version/s: 3.12.0

Type: Improvement Priority: Minor - P4
Reporter: Nic Cottrell Assignee: John Stewart (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on JAVA-2244 Allow TLS 1.2 SSL connections with Mo... Closed
Backwards Compatibility: Minor Change

 Description   

Description

https://mongodb.github.io/mongo-java-driver/3.7/driver/tutorials/ssl/#jvm-support-for-tls-v1-1-and-newer explains which  Java versions support which TLS versions  and which are default. 

Customers interested in compliance, may want to force only TLS 1.2 from their app,  such as in  the example in JAVA-2486.

I propose a new section at the bottom headed "Forcing TLS 1.2" with the code snippet and caveats about Java updates from the previous section. 

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Githook User [ 13/Nov/19 ]

Author:

{'username': 'jstewart-mongo', 'email': 'john.stewart@mongodb.com', 'name': 'John Stewart'}

Message: Add Java driver example of forcing TLS 1.2

JAVA-3386
Branch: master
https://github.com/mongodb/mongo-java-driver/commit/af974b28439fa17422a58ba53b56250eb0c2a8b4

Comment by John Stewart (Inactive) [ 08/Nov/19 ]

PR: https://github.com/jstewart-mongo/mongo-java-driver/pull/65

Comment by Ravind Kumar (Inactive) [ 16/Aug/19 ]

Sadly, at this time our bandwidth is limited, but perhaps in a more golden future

 

For now I'll move this over.

Comment by Jeffrey Yemin [ 16/Aug/19 ]

Yes, though we welcome pull requests from docs engineers!

Comment by Ravind Kumar (Inactive) [ 16/Aug/19 ]

jeff.yemin am I right in thinking we should move this to the JAVA project for visibility?

Generated at Thu Feb 08 08:59:29 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.