You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
//Blank line here is necessary before starting the body of the post.
@@ -66,16 +66,10 @@ This release introduces ECDH-ES support in JwtBuilder.
66
66
67
67
In link:{url-about}[Open Liberty] 25.0.0.9:
68
68
69
-
* <<ECDH-ES, Add ECDH-ES support to JwtBuilder>>
69
+
* <<ECDH_ES, Add ECDH-ES support to JwtBuilder>>
70
70
* <<CVEs, Security Vulnerability (CVE) Fixes>>
71
71
* <<bugs, Notable bug fixes>>
72
72
73
-
74
-
// // // // // // // //
75
-
// If there were updates to guides since last release, keep the following, otherwise remove section.
76
-
// // // // // // // //
77
-
Along with the new features and functions added to the runtime, we’ve also made <<guides, updates to our guides>>.
78
-
79
73
// // // // // // // //
80
74
// In the preceding section:
81
75
// Replace the TAG_X with a short label for the feature in lower-case, eg: mp3
@@ -161,30 +155,37 @@ image::img/blog/blog_btn_stack.svg[Ask a question on Stack Overflow, align="cent
161
155
// Blog issue: https://github.com/OpenLiberty/open-liberty/issues/32660
162
156
// Contact/Reviewer: tloodu
163
157
// // // // // // // //
164
-
[#ECDH-ES]
158
+
[#ECDH_ES]
165
159
== Add ECDH-ES support to JwtBuilder
166
160
167
-
Open Liberty has enhanced its JSON Web Token 1.0 (`jwt-1.0`) feature by introducing support for ECDH-ES (Elliptic Curve Diffie-Hellman Ephemeral Static) as a key management algorithm in the JwtBuilder configuration. This update allows application developers to use Elliptic Curve Cryptography for encrypting the Content Encryption Key (CEK) of a JWE, providing a modern alternative to the previously supported RSA-OAEP with enhanced security.To use ECDH-ES, developers must define an Elliptic Curve public key in the keyManagementKeyAlias attribute.The EC public and private key pair can be generated using securityUtility or keytool, for example:
ECDH-ES can be configured under the `keyManagementKeyAlgorithm` attribute in a JwtBuilder element of `JSON Web Token 1.0` (`jwt-1.0`) feature.The EC public key used for encryption must be referenced by its alias in `keyManagementKeyAlias`, and the keystore must be specified using the `trustStoreRef` attribute.
171
-
Sample server.xml configuration:
161
+
Open Liberty has enhanced its JSON Web Token 1.0 (`jwt-1.0`) feature by introducing support for ECDH-ES (Elliptic Curve Diffie-Hellman Ephemeral Static) as a key management algorithm in the JwtBuilder configuration. This update allows application developers to use Elliptic Curve Cryptography for encrypting the Content Encryption Key (CEK) of a JWE, providing a modern alternative to the previously supported RSA-OAEP with enhanced security.
172
162
173
-
[source,xml]
163
+
To use ECDH-ES, developers must define an Elliptic Curve public key in the `keyManagementKeyAlias` attribute. The EC public and private key pair can be generated using securityUtility or keytool, for example:
ECDH-ES can be configured under the `keyManagementKeyAlgorithm` attribute in a JwtBuilder element of `JSON Web Token 1.0` (jwt-1.0) feature. The EC public key used for encryption must be referenced by its alias in `keyManagementKeyAlias`, and the keystore must be specified using the `trustStoreRef` attribute.
174
+
175
+
Sample server.xml configuration:
176
+
+
177
+
[source, xml]
174
178
----
175
179
<jwtBuilder
176
180
keyManagementKeyAlgorithm="ECDH-ES"
177
181
keyManagementKeyAlias="myECPublicKey"
178
182
trustStoreRef="myTrustStore" ... />
179
183
----
180
-
For more details on configuring `JwtBuilder` and using ECDH-ES, refer to the https://openliberty.io/docs/latest/reference/config/jwtBuilder.html[Open Liberty documentation].
184
+
185
+
For more details on configuring `JwtBuilder` and using ECDH-ES, check the link:https://openliberty.io/docs/latest/reference/config/jwtBuilder.html[Open Liberty documentation].
181
186
182
-
183
187
// DO NOT MODIFY THIS LINE. </GHA-BLOG-TOPIC>
184
188
185
-
186
-
For more details, check the LINK[LINK_DESCRIPTION].
187
-
188
189
// // // // // // // //
189
190
// In the preceding section:
190
191
// Replace TAG_X/SUB_TAG_X with the given tag of your secton from the contents list
@@ -210,19 +211,19 @@ For more details, check the LINK[LINK_DESCRIPTION].
210
211
|5.3
211
212
|Denial of service
212
213
|18.0.0.2-25.0.0.8
213
-
|Affects the `feature:servlet-3.1`, `feature:servlet-4.0`, `feature:servlet-5.0` and `feature:servlet-6.0` features
214
+
|Affects the `servlet-3.1`, `servlet-4.0`, `servlet-5.0` and `servlet-6.0` features
|Affects the `feature:wasJmsServer-1.0`, `feature:wasJmsSecurity-1.0`, `feature:wasJmsClient-2.0`, `feature:messagingServer-3.0`, `feature:messagingSecurity-3.0` and `feature:messagingClient-3.0` features
226
+
|Affects the `wasJmsServer-1.0`, `wasJmsSecurity-1.0`, `wasJmsClient-2.0`, `messagingServer-3.0`, `messagingSecurity-3.0` and `messagingClient-3.0` features
226
227
|===
227
228
// // // // // // // //
228
229
// In the preceding section:
@@ -288,22 +289,6 @@ We’ve spent some time fixing bugs. The following sections describe just some o
288
289
// // // // // // // //
289
290
290
291
291
-
// // // // // // // //
292
-
// If there were updates to guides since last release, keep the following, otherwise remove section.
293
-
// Check with Gilbert Kwan, otherwise Michal Broz or YK Chang
294
-
// // // // // // // //
295
-
[#guides]
296
-
== New and updated guides since the previous release
297
-
As Open Liberty features and functionality continue to grow, we continue to add link:https://openliberty.io/guides/?search=new&key=tag[new guides to openliberty.io] on those topics to make their adoption as easy as possible. Existing guides also receive updates to address any reported bugs/issues, keep their content current, and expand what their topic covers.
298
-
299
-
// // // // // // // //
300
-
// In the following section, list any new guides, or changes/updates to existing guides.
301
-
// The following is an example of how the list can be structured (similar to the bugs section):
0 commit comments