Skip to main content
Moderne OnlyThis recipe is proprietary to Moderne and runs on the Moderne platform or CLI — it isn’t part of the open-source catalog. Available with a Moderne subscription.Contact Sales

Enforce a TLS 1.3 floor in YAML files

Recipe IDio.moderne.cryptography.pqc.EnforceTls13Yaml
Artifactio.moderne.recipe:rewrite-cryptography

Rewrites TLS protocol configuration in YAML files to a TLS 1.3 floor, so that JEP 527 hybrid key exchange — which exists for TLS 1.3 only — can negotiate. Covers server.ssl.enabled-protocols, the jdk.tls.client.protocols, jdk.tls.server.protocols and https.protocols keys, server.ssl.protocol under strictAlgorithmName, and any key named in additionalPropertyKeys. Values may be a single scalar, a comma-separated scalar, or a sequence in flow or block style; a sequence is rewritten in place, reusing its existing entries so indentation and comments survive. Configuration a source scan cannot see — config servers, ConfigMap overlays, environment variables — is out of scope, so an unchanged repository is not evidence of an enforced floor.

Single recipeOpenRewriteModerne Proprietary License
Try in PlatformTry this recipe in the Moderne platform. Not a user yet? You’ll get a no-setup demo environment, with nothing to install or configure.

Options

4 parameters
4 optional
ParameterExampleTypeRequired
additionalPropertyKeysmy.service.tls-protocolsListOptional
Configuration keys beyond the built-in ones whose values enumerate TLS protocol versions. Matched with Spring relaxed binding against the dotted path of the mapping entry, so my.tls.enabled-protocols also matches my.tls.enabledProtocols.
minimumProtocolTLSv1.2StringOptional
The protocol floor to enforce globally: TLSv1.3 (the default) strips TLSv1.2 from every enumerated protocol list, TLSv1.2 retains it everywhere. Use retainTls12In instead when only some configuration files need the exception.
retainTls12In**/application-legacy.ymlListOptional
Globs naming the configuration files that keep TLSv1.2 in their rewritten protocol lists, matched against the source path. SSLv2Hello, SSLv3, TLSv1 and TLSv1.1 are still stripped inside a matched file, and TLSv1.3 is still ensured present.
strictAlgorithmNameBooleanOptional
Also rewrite server.ssl.protocol when it names a version-flexible algorithm — TLS or Default — to TLSv1.3. Off by default: Spring Boot passes this value to SSLContext.getInstance, where those names already permit TLS 1.3. A value naming a version below 1.3 is rewritten either way, because such a context can never negotiate TLS 1.3.

Examples

yaml
ParameterValue
minimumProtocolnull
retainTls12Innull
strictAlgorithmNamenull
additionalPropertyKeysnull
Before
server:
ssl:
enabled-protocols:
- TLSv1.1
- TLSv1.2
protocol: TLS
port: 8443
After
server:
ssl:
enabled-protocols:
- TLSv1.3
protocol: TLS
port: 8443

Usage

Run this recipe

This recipe has no required configuration options. Users of Moderne can run it via the Moderne CLI.

You will need to have configured the Moderne CLI on your machine before you can run the following command.

shell
mod run . --recipe EnforceTls13Yaml

If the recipe is not available locally, then you can install it using:

RELEASE resolves to the newest release and LATEST to the newest build of any kind, including snapshots. Either one lets mod config recipes upgrade pull in later versions without editing this command; a pinned version stays where you put it.

mod config recipes jar install io.moderne.recipe:rewrite-cryptography:RELEASE

Data tables

TLS protocol enforcement
io.moderne.cryptography.pqc.table.ProtocolEnforcementTable

Protocol configuration surfaces rewritten to a TLS 1.3 floor, and surfaces flagged as needing manual review because rewriting them would change behaviour in a way a source scan cannot justify. Rows describe declared configuration only: a JVM's java.security file, container -D flags and environment variables are invisible here, so an enforced source does not prove an enforced runtime.

ColumnDescription
Configuration surfaceThe API or configuration key that produced the row, e.g. SSLContext.getInstance, SSLSocket.setEnabledProtocols, SSLServerSocket.setEnabledProtocols, SSLEngine.setEnabledProtocols, SSLParameters.setProtocols, https.protocols, jdk.tls.client.protocols, jdk.tls.server.protocols, jdk.tls.disabledAlgorithms, AbstractTlsPeer.getSupportedVersions, server.ssl.enabled-protocols, server.ssl.protocol. The token vocabulary is shared with the TLS configuration inventory so discovery and enforcement rows can be joined.
ActionRewritten when the recipe changed the source, or Report only when the surface was flagged but deliberately not transformed — a protocol array shared with non-TLS code, or a jdk.tls.disabledAlgorithms assignment that replaces rather than extends the JDK default list.
Protocols beforeComma-joined protocol tokens found before the change, e.g. TLSv1.1,TLSv1.2. BouncyCastle downTo ranges are expanded to their JSSE spelling, e.g. TLSv1.2,TLSv1.1,TLSv1. For a jdk.tls.disabledAlgorithms row this is the raw property value.
Protocols afterComma-joined protocol tokens after the change, e.g. TLSv1.3, or TLSv1.3,TLSv1.2 where an exception retains TLS 1.2. Empty for Report only rows.
Code snippetThe source code of the detected API usage, e.g. Cipher.getInstance("DES").
Library nameThe library providing the configuration surface: JSSE, BouncyCastle or Spring Boot.
Library languageThe language of the source the row was found in: Java, Properties or YAML.
File locationThe path of the source file relative to the repository root.
Start line1-based line of the start of the API usage.
Start column0-based column of the start of the API usage, or -1 when unavailable.
Start offset0-based character offset of the start of the API usage, or -1 when unavailable.
End line1-based line of the end of the API usage.
End column0-based column of the end of the API usage, or -1 when unavailable.
End offset0-based character offset of the end of the API usage, or -1 when unavailable.
Repository nameThe repository name from Git provenance, e.g. payment-service. Empty when unknown.
Scan sourceWhere the source was scanned from, derived from Git provenance, e.g. GitHub, GitLab, Local Repository.
BranchThe branch from Git provenance, e.g. main. Empty when unknown.
Source files that had results
org.openrewrite.table.SourcesFileResults

Source files that were modified by the recipe run.

ColumnDescription
Source path before the runThe source path of the file before the run. null when a source file was created during the run.
Source path after the runA recipe may modify the source path. This is the path after the run. null when a source file was deleted during the run.
Parent of the recipe that made changesIn a hierarchical recipe, the parent of the recipe that made a change. Empty if this is the root of a hierarchy or if the recipe is not hierarchical at all.
Recipe that made changesThe specific recipe that made a change.
Estimated time savingAn estimated effort that a developer to fix manually instead of using this recipe, in unit of seconds.
CycleThe recipe cycle in which the change was made.
Source files that had search results
org.openrewrite.table.SearchResults

Search results that were found during the recipe run.

ColumnDescription
Source path of search result before the runThe source path of the file with the search result markers present.
Source path of search result after run the runA recipe may modify the source path. This is the path after the run. null when a source file was deleted during the run.
ResultThe trimmed printed tree of the LST element that the marker is attached to.
DescriptionThe content of the description of the marker.
Recipe that added the search markerThe specific recipe that added the Search marker.
Source files that errored on a recipe
org.openrewrite.table.SourcesFileErrors

The details of all errors produced by a recipe run.

ColumnDescription
Source pathThe file that failed to parse.
Recipe that made changesThe specific recipe that made a change.
Stack traceThe stack trace of the failure.
Recipe performance
org.openrewrite.table.RecipeRunStats

Statistics used in analyzing the performance of recipes.

ColumnDescription
The recipeThe recipe whose stats are being measured both individually and cumulatively.
Source file countThe number of source files the recipe ran over.
Source file changed countThe number of source files which were changed in the recipe run. Includes files created, deleted, and edited.
Cumulative scanning time (ns)The total time spent across the scanning phase of this recipe.
Max scanning time (ns)The max time scanning any one source file.
Cumulative edit time (ns)The total time spent across the editing phase of this recipe.
Max edit time (ns)The max time editing any one source file.