Skip to content

Enforce TLS 1.2 as the minimum protocol version in MaplyURLSessionManager to ensure secure network communication#1626

Open
AmineNac wants to merge 1 commit into
mousebird-consulting-inc:mainfrom
AmineNac:patch-1
Open

Enforce TLS 1.2 as the minimum protocol version in MaplyURLSessionManager to ensure secure network communication#1626
AmineNac wants to merge 1 commit into
mousebird-consulting-inc:mainfrom
AmineNac:patch-1

Conversation

@AmineNac
Copy link
Copy Markdown

Modified MaplyURLSessionManager to enforce a minimum TLS version of 1.2 for URLSession connections. This change disables outdated and insecure protocols such as SSLv2, SSLv3, TLSv1.0, and TLSv1.1. Enforcing TLS 1.2+ helps ensure secure data transmission and complies with security standards recommended by code scanning tools like Fortify and SonarQube.

…ager to ensure secure network communication

Modified MaplyURLSessionManager to enforce a minimum TLS version of 1.2 for URLSession connections. This change disables outdated and insecure protocols such as SSLv2, SSLv3, TLSv1.0, and TLSv1.1. Enforcing TLS 1.2+ helps ensure secure data transmission and complies with security standards recommended by code scanning tools like Fortify and SonarQube.
@AmineNac
Copy link
Copy Markdown
Author

AmineNac commented Nov 3, 2025

@TimSylvester any updates on this ?

@TimSylvester
Copy link
Copy Markdown
Collaborator

Seems reasonable. It can be overridden, right?

@sjg-wdw ?

@sjg-wdw
Copy link
Copy Markdown
Collaborator

sjg-wdw commented Nov 3, 2025

Given the sort of data usually displayed in the toolkit I'm not sure it matter too much, but I could be wrong. Did you have a use case for this in your app?

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.

3 participants