Skip to content

Commit f3a3444

Browse files
navaneethsnair1navaneethsnair1
committed
update beta and GA blogs
1 parent 90e4294 commit f3a3444

3 files changed

Lines changed: 74 additions & 33 deletions

File tree

‎blog_tags.json‎

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,8 @@
22
"blog_tags": [
33
{
44
"name": "announcements",
5-
"posts": ["26.0.0.5-beta", "26.0.0.4", "26.0.0.4-beta",
5+
"posts": ["26.0.0.5", "26.0.0.5-beta",
6+
"26.0.0.4", "26.0.0.4-beta",
67
"26.0.0.3", "26.0.0.3-beta",
78
"26.0.0.2", "26.0.0.2-beta",
89
"26.0.0.1", "26.0.0.1-beta",
@@ -199,7 +200,8 @@
199200
},
200201
{
201202
"name": "release",
202-
"posts": ["26.0.0.5-beta", "26.0.0.4", "26.0.0.4-beta",
203+
"posts": ["26.0.0.5", "26.0.0.5-beta",
204+
"26.0.0.4", "26.0.0.4-beta",
203205
"26.0.0.3", "26.0.0.3-beta",
204206
"26.0.0.2", "26.0.0.2-beta",
205207
"26.0.0.1", "26.0.0.1-beta",
@@ -336,7 +338,7 @@
336338
},
337339
{
338340
"name": "security",
339-
"posts": ["26.0.0.5-beta", "26.0.0.4",
341+
"posts": ["26.0.0.5", "26.0.0.5-beta", "26.0.0.4",
340342
"26.0.0.4-beta", "26.0.0.3",
341343
"25.0.0.12", "25.0.0.12-beta",
342344
"25.0.0.9", "25.0.0.9-beta",
@@ -374,7 +376,7 @@
374376
},
375377
{
376378
"name": "spring",
377-
"posts": ["25.0.0.12-beta", "24.0.0.6", "spring-boot-3",
379+
"posts": ["26.0.0.5", "25.0.0.12-beta", "24.0.0.6", "spring-boot-3",
378380
"23.0.0.12", "23.0.0.10-beta",
379381
"23.0.0.9", "23.0.0.9-beta",
380382
"23.0.0.8-beta", "running-spring-boot-3",
@@ -433,7 +435,7 @@
433435
},
434436
{
435437
"name": "jakarta-ee",
436-
"posts": ["26.0.0.4-beta", "26.0.0.3", "25.0.0.12-beta",
438+
"posts": ["26.0.0.5", "26.0.0.4-beta", "26.0.0.3", "25.0.0.12-beta",
437439
"24.0.0.12-beta", "rethinking-microservices",
438440
"24.0.0.8", "liberty-developer-essentials-badge",
439441
"24.0.0.8-beta", "24.0.0.7-beta",

‎posts/2026-05-05-26.0.0.5-beta.adoc‎

Lines changed: 12 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -1,24 +1,24 @@
11
---
22
layout: post
3-
title: "Updates to MCP Server and TLS/SSL Cipher Support in 26.0.0.5 Beta"
3+
title: "Updates to MCP Server and TLS/SSL Cipher Support in 26.0.0.5-beta"
44
# Do NOT change the categories section
55
categories: blog
66
author_picture: https://avatars3.githubusercontent.com/navaneethsnair1
77
author_github: https://github.com/navaneethsnair1
8-
seo-title: "Updates to MCP Server and TLS/SSL Cipher Support in 26.0.0.5 Beta- OpenLiberty.io"
9-
seo-description: This beta release updates the `mcpServer-1.0` feature and simplifies SSL cipher configuration by using the effective JDK cipher list by default and flexible `enabledCiphers` syntax.
10-
blog_description: This beta release updates the `mcpServer-1.0` feature and simplifies SSL cipher configuration by using the effective JDK cipher list by default and flexible `enabledCiphers` syntax.
8+
seo-title: "Updates to MCP Server and TLS/SSL Cipher Support in 26.0.0.5-beta - OpenLiberty.io"
9+
seo-description: This beta release updates the mcpServer-1.0 feature and simplifies SSL cipher configuration by using the effective JDK cipher list by default and flexible enabledCiphers syntax.
10+
blog_description: This beta release updates the mcpServer-1.0 feature and simplifies SSL cipher configuration by using the effective JDK cipher list by default and flexible enabledCiphers syntax.
1111
open-graph-image: https://openliberty.io/img/twitter_card.jpg
1212
open-graph-image-alt: Open Liberty Logo
1313
---
14-
= Updates to MCP Server and TLS/SSL Cipher Support in 26.0.0.5 Beta
14+
= Updates to MCP Server and TLS/SSL Cipher Support in 26.0.0.5-beta
1515
Navaneeth S Nair <https://github.com/navaneethsnair1>
1616
:imagesdir: /
1717
:url-prefix:
1818
:url-about: /
1919
//Blank line here is necessary before starting the body of the post.
2020

21-
This beta release updates the `mcpServer-1.0` feature and simplifies SSL cipher configuration by using the effective JDK cipher list by default and flexible `enabledCiphers` syntax.
21+
This beta release updates the mcpServer-1.0 feature and simplifies SSL cipher configuration by using the effective JDK cipher list by default and flexible enabledCiphers syntax.
2222

2323
// // // // // // // //
2424
// Change the RELEASE_SUMMARY to an introductory paragraph. This sentence is really
@@ -55,7 +55,7 @@ The link:https://modelcontextprotocol.io/docs/getting-started/intro[Model Contex
5555
This beta release of Liberty includes important updates to the `mcpServer-1.0` feature, including configurable endpoint paths and notable bug fixes.
5656

5757
=== Prerequisites
58-
To use the `mcpServer-1.0` feature, it is required to have `Java 17` or later installed on your system.
58+
To use the `mcpServer-1.0` feature, it is required to have Java 17 or later installed on your system.
5959

6060
=== Configure custom MCP endpoint paths
6161
Previously, the MCP endpoint was hard-coded to `/mcp` under the web application context root. You can now configure custom endpoint paths to better suit your application architecture and naming conventions.
@@ -78,8 +78,6 @@ For a single application, configure the endpoint path directly in the `<mcpServe
7878
<mcpServer path="/custom-mcp"/>
7979
</application>
8080
81-
<include location="../fatTestPorts.xml" />
82-
8381
</server>
8482
----
8583

@@ -153,36 +151,34 @@ This has been fixed to ensure proper isolation of encoder beans per application,
153151
[#ssl]
154152
== Update to TLS/SSL Cipher support
155153

156-
Liberty uses the effective JDK cipher list from the JDK. The `securityLevel` attribute in the SSL configuration is not used anymore. In addition, the `enabledCiphers` attribute in the SSL config is updated to customize the SSL ciphers in a more flexible way.
157-
158-
This change modifies the existing attribute `enabledCiphers` in the `ssl` config.
154+
Liberty now uses the effective cipher list from the JDK for SSL configuration. The `securityLevel` attribute in the SSL configuration is not used anymore. In addition, the `enabledCiphers` attribute in the SSL config is updated to customize the SSL ciphers in a more flexible way.
159155

160156
Liberty's `securityLevel` based cipher categories no longer provide meaningful value. The `MEDIUM` and `LOW` categories contain no remaining ciphers.
161157

162158
The `enabledCiphers` attribute now has two mutually exclusive modes: (1) Specify a custom list of ciphers separated by spaces, or (2) Specify filter criteria to add (+) or remove (-) cipher suites from the effective JDK cipher list. If the value set in `enabledCiphers` contains a static entry and a +/- entry, an error is logged, and the server ignores the `enabledCiphers` value by returning the effective JDK cipher list.
163159

164-
*Existing Usage - A user sets `securityLevel` as `HIGH`*
160+
*Existing Usage:* A user sets `securityLevel` as `HIGH`
165161

166162
[source,xml]
167163
----
168164
<ssl id="defaultSSL" securityLevel=HIGH/>
169165
----
170166

171-
*Example with new syntax - `securityLevel` is not required and is ignored if provided*
167+
The `securityLevel` attribute is now ignored, so the previous `<ssl>` configuration is treated equivalently to the configuration shown here where there is no `securityLevel` attribute configured.
172168

173169
[source,xml]
174170
----
175171
<ssl id="defaultSSL"/>
176172
----
177173

178-
*Existing Usage - A user specifies all ciphers from the effective jdk list excluding all TLS_RSA ciphers except for one (TLS_RSA_WITH_AES_128_GCM_SHA256)*
174+
*Existing Usage:* A user specifies all ciphers from the effective JDK list, excluding all TLS_RSA ciphers except for one (TLS_RSA_WITH_AES_128_GCM_SHA256)
179175

180176
[source,xml]
181177
----
182178
<ssl id="defaultSSL" securityLevel="CUSTOM" enabledCiphers="TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 TLS_DHE_DSS_WITH_AES_256_GCM_SHA384 TLS_DHE_DSS_WITH_AES_128_GCM_SHA256 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 TLS_DHE_DSS_WITH_AES_256_CBC_SHA256 TLS_DHE_DSS_WITH_AES_128_CBC_SHA256 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA TLS_DHE_DSS_WITH_AES_256_CBC_SHA TLS_DHE_DSS_WITH_AES_128_CBC_SHA TLS_RSA_WITH_AES_128_GCM_SHA256">
183179
----
184180

185-
*Example with new syntax - Use wildcards to achieve the same logic*
181+
*Example with new syntax:* Use wildcards to achieve the same logic
186182
[source,xml]
187183
----
188184
<ssl id="defaultSSL" enabledCiphers="-TLS_RSA* +TLS_RSA_WITH_AES_128_GCM_SHA256"/>

‎posts/2026-05-19-26.0.0.5.adoc‎

Lines changed: 55 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,17 @@
11
---
22
layout: post
3-
title: "Jakarta EE 11, SpringBoot 4.0, and more in 26.0.0.5"
3+
title: "Jakarta EE 11, Spring Boot 4.0, and more in 26.0.0.5"
44
# Do NOT change the categories section
55
categories: blog
66
author_picture: https://avatars3.githubusercontent.com/navaneethsnair1
77
author_github: https://github.com/navaneethsnair1
8-
seo-title: Jakarta EE 11, SpringBoot 4.0, and more in 26.0.0.5- OpenLiberty.io
9-
seo-description: This release adds support for Jakarta EE 11 and SpringBoot 4.0, including MicroProfile 7 compatibility with Jakarta EE 11 and support for deploying SpringBoot 4.x applications in both JAR and WAR formats.
10-
blog_description: This release adds support for Jakarta EE 11 and SpringBoot 4.0, including MicroProfile 7 compatibility with Jakarta EE 11 and support for deploying SpringBoot 4.x applications in both JAR and WAR formats.
8+
seo-title: Jakarta EE 11, Spring Boot 4.0, and more in 26.0.0.5- OpenLiberty.io
9+
seo-description: This release introduces official support for Jakarta EE 11, Spring Boot 4.0 applications, and updated TLS/SSL cipher handling in Open Liberty, including enhanced Spring Boot deployment support and simplified SSL cipher configuration.
10+
blog_description: This release introduces official support for Jakarta EE 11, Spring Boot 4.0 applications, and updated TLS/SSL cipher handling in Open Liberty, including enhanced Spring Boot deployment support and simplified SSL cipher configuration.
1111
open-graph-image: https://openliberty.io/img/twitter_card.jpg
1212
open-graph-image-alt: Open Liberty Logo
1313
---
14-
= Jakarta EE 11, SpringBoot 4.0, and more in 26.0.0.5
14+
= Jakarta EE 11, Spring Boot 4.0, and more in 26.0.0.5
1515
Navaneeth S Nair <https://github.com/navaneethsnair1>
1616
:imagesdir: /
1717
:url-prefix:
@@ -49,7 +49,7 @@ Navaneeth S Nair <https://github.com/navaneethsnair1>
4949
// change the "IMAGE CAPTION" to a couple words of what the image is
5050
// // // // // // // //
5151

52-
This release adds support for Jakarta EE 11 and SpringBoot 4.0, including MicroProfile 7 compatibility with Jakarta EE 11 and support for deploying SpringBoot 4.x applications in both JAR and WAR formats.
52+
This release introduces official support for Jakarta EE 11, Spring Boot 4.0 applications, and updated TLS/SSL cipher handling in Open Liberty, including enhanced Spring Boot deployment support and simplified SSL cipher configuration.
5353

5454
// // // // // // // //
5555
// In the preceding section:
@@ -67,7 +67,8 @@ This release adds support for Jakarta EE 11 and SpringBoot 4.0, including MicroP
6767
In link:{url-about}[Open Liberty] 26.0.0.5:
6868

6969
* <<jakarta_ee, Jakarta EE 11 Core Profile, Web Profile, and Platform>>
70-
* <<springboot, SpringBoot 4.0>>
70+
* <<springboot, Spring Boot 4.0>>
71+
* <<ssl, Update to TLS/SSL Cipher support>>
7172
* <<CVEs, Security Vulnerability (CVE) Fixes>>
7273
* <<bugs, Notable bug fixes>>
7374

@@ -280,10 +281,10 @@ To run Jakarta EE 11 features on the Application Client Container, add the follo
280281
// Contact/Reviewer: anjumfatima90
281282
// // // // // // // //
282283
[#springboot]
283-
== SpringBoot 4.0
284-
Open Liberty currently supports running SpringBoot 1.5, 2.x, and 3.x applications. With the introduction of the new `springBoot-4.0` feature, users can now deploy SpringBoot 4.x applications. While Liberty has consistently supported SpringBoot applications packaged as `WAR` files, this enhancement extends support to both `JAR` and `WAR` formats for SpringBoot 4.x applications.
284+
== Spring Boot 4.0
285+
Open Liberty currently supports running Spring Boot 1.5, 2.x, and 3.x applications. With the introduction of the new `springBoot-4.0` feature, users can now deploy Spring Boot 4.x applications. While Liberty has consistently supported Spring Boot applications packaged as `WAR` files, this enhancement extends support to both `JAR` and `WAR` formats for Spring Boot 4.x applications.
285286

286-
The `springBoot-4.0` feature provides complete support for running a SpringBoot 4.x application on Open Liberty, as well as the ability to thin the application when building containerized applications.
287+
The `springBoot-4.0` feature provides complete support for running a Spring Boot 4.x application on Open Liberty, as well as the ability to thin the application when building containerized applications.
287288

288289
To use this feature, users must be running `Java 17` or later with EE11 features enabled. If the application uses servlets, it must be configured to use `Servlet 6.1`. Include the following features in your `server.xml` file to configure the server.
289290

@@ -295,17 +296,59 @@ To use this feature, users must be running `Java 17` or later with EE11 features
295296
</features>
296297
----
297298

298-
The `server.xml` configuration for deploying a SpringBoot application follows the same approach used in earlier Liberty SpringBoot versions.
299+
The `server.xml` configuration for deploying a Spring Boot application follows the same approach used in earlier Liberty Spring Boot versions.
299300

300301
[source, xml]
301302
----
302303
<springBootApplication id="spring-boot-app" location="spring-boot-app-0.1.0.jar" name="spring-boot-app" />
303304
----
304305

305-
As in earlier versions, the SpringBoot application JAR can be deployed by placing it in the `/dropins/spring` folder. The `springBootApplication` configuration in the `server.xml` file can be omitted when this deployment method is used.
306+
As in earlier versions, the Spring Boot application JAR can be deployed by placing it in the `/dropins/spring` folder. The `springBootApplication` configuration in the `server.xml` file can be omitted when this deployment method is used.
306307

307308
// DO NOT MODIFY THIS LINE. </GHA-BLOG-TOPIC>
308309

310+
// // // // DO NOT MODIFY THIS COMMENT BLOCK <GHA-BLOG-TOPIC> // // // //
311+
// Blog issue: https://github.com/OpenLiberty/open-liberty/issues/34374
312+
// Contact/Reviewer: rangaran
313+
// // // // // // // //
314+
[#ssl]
315+
== Update to TLS/SSL Cipher support
316+
Liberty now uses the effective cipher list from the JDK for SSL configuration. The `securityLevel` attribute in the SSL configuration is not used anymore. In addition, the `enabledCiphers` attribute in the SSL config is updated to customize the SSL ciphers in a more flexible way.
317+
318+
Liberty's `securityLevel` based cipher categories no longer provide meaningful value. The `MEDIUM` and `LOW` categories contain no remaining ciphers.
319+
320+
The `enabledCiphers` attribute now has two mutually exclusive modes: (1) Specify a custom list of ciphers separated by spaces, or (2) Specify filter criteria to add (+) or remove (-) cipher suites from the effective JDK cipher list. If the value set in `enabledCiphers` contains a static entry and a +/- entry, an error is logged, and the server ignores the `enabledCiphers` value by returning the effective JDK cipher list.
321+
322+
*Existing Usage:* A user sets `securityLevel` as `HIGH`
323+
324+
[source,xml]
325+
----
326+
<ssl id="defaultSSL" securityLevel=HIGH/>
327+
----
328+
329+
The `securityLevel` attribute is now ignored, so the previous `<ssl>` configuration is treated equivalently to the configuration shown here where there is no `securityLevel` attribute configured.
330+
331+
[source,xml]
332+
----
333+
<ssl id="defaultSSL"/>
334+
----
335+
336+
*Existing Usage:* A user specifies all ciphers from the effective JDK list, excluding all TLS_RSA ciphers except for one (TLS_RSA_WITH_AES_128_GCM_SHA256)
337+
338+
[source,xml]
339+
----
340+
<ssl id="defaultSSL" securityLevel="CUSTOM" enabledCiphers="TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 TLS_DHE_DSS_WITH_AES_256_GCM_SHA384 TLS_DHE_DSS_WITH_AES_128_GCM_SHA256 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 TLS_DHE_DSS_WITH_AES_256_CBC_SHA256 TLS_DHE_DSS_WITH_AES_128_CBC_SHA256 TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA TLS_DHE_DSS_WITH_AES_256_CBC_SHA TLS_DHE_DSS_WITH_AES_128_CBC_SHA TLS_RSA_WITH_AES_128_GCM_SHA256">
341+
----
342+
343+
*Example with new syntax:* Use wildcards to achieve the same logic
344+
[source,xml]
345+
----
346+
<ssl id="defaultSSL" enabledCiphers="-TLS_RSA* +TLS_RSA_WITH_AES_128_GCM_SHA256"/>
347+
----
348+
349+
To learn more about Transport Security, see link:https://openliberty.io/docs/modules/reference/23.0.0.6/com.ibm.websphere.appserver.api.ssl_1.5-javadoc/com/ibm/websphere/ssl/Constants.html[SSL Constants Javadoc], link:https://openliberty.io/docs/modules/reference/23.0.0.6/com.ibm.websphere.appserver.api.ssl_1.5-javadoc/com/ibm/websphere/ssl/JSSEProvider.html[JSSEProvider Javadoc], and link:https://openliberty.io/docs/latest/reference/config/ssl.html[SSL Configuration Reference].
350+
351+
// DO NOT MODIFY THIS LINE. </GHA-BLOG-TOPIC>
309352

310353
[#CVEs]
311354
== Security vulnerability (CVE) fixes in this release

0 commit comments

Comments
 (0)