Skip to content

Commit 76cd44d

Browse files
updates to 25.0.0.9 blog
1 parent c65d563 commit 76cd44d

File tree

1 file changed

+6
-7
lines changed

1 file changed

+6
-7
lines changed

posts/2025-09-09-25.0.0.9.adoc

Lines changed: 6 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -161,19 +161,18 @@ image::img/blog/blog_btn_stack.svg[Ask a question on Stack Overflow, align="cent
161161
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.
162162

163163
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:
164-
+
165-
```
164+
165+
----
166166
./securityUtility createSSLCertificate --sigAlg=SHA256withECDSA --keySize=256 --server=myServer --validity=3650 --password=password
167-
```
168-
+
169-
```
167+
----
168+
169+
----
170170
keytool -genkeypair -alias eccert -keyalg EC -groupname secp256r1 -validity 3650 -storetype pkcs12 -keystore myKeystore.p12 -storepass password
171-
```
171+
----
172172

173173
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.
174174

175175
Sample server.xml configuration:
176-
+
177176
[source, xml]
178177
----
179178
<jwtBuilder

0 commit comments

Comments
 (0)