JSR 337 Maintenance Release 3: Java SE 8
Change Summary
Iris Clark
2019/12/11

This document describes additional changes to the specification of JSR 337 which is defined by the Final Release in March 2014, Maintenance Release 1 in March 2015. and Maintenance Release 2 in March 2019. When specification text is provided, insertions are shown on a light green background and deletions are shown struck through on a light red background. Links to pages outside of those explicitly changed by this specification may not be functional.

Send comments to java-se-mr-spec-comments@openjdk.java.net.

Contents
1Version Identification
2TLS ALPN
3RSASSA-PSS
1
Version Identification  

There is no change to the values returned by the system properties java.specification.version and java.vm.specification.version. They continue to report "1.8". If an application needs to identify the release, the system property java.version may be used.

2
TLS ALPN  

The TLS ALPN (Application-Layer Protocol Negotiation) Extension was added to Java SE 9 with JEP 244 (TLS Application-Layer Protocol Negotiation Extension (ALPN)). It allows negotiation of an application-layer protocol value during the TLS handshake which may be used during the selection of other TLS protocol parameters. HTTP/2 and other modern network protocols use ALPN.

The following methods were added to types in package javax.net.ssl to allow TLS clients and servers to use multiple application-layer protocols over the same transport-layer port:

These methods were added to types in package javax.net.ssl to defer the section of an application protocol until after the TLS cipher suite is known:

The Change Specification Request (CSR) associated with this change is 8233417.

3
RSASSA-PSS  
Support for the RSASSA-PSS (RSA Signature Scheme with Appendix -- Probabilistic Signature Scheme) algorithm was added to Java SE 11. It is a cryptographic signature scheme used for secure data transmission which was initially standardized as part of PKCS#1 v2.1 and revised in PKCS#1 v2.2. The following API changes and additions were necessary to enable third-party provider support.

The CSR associated with this change is 8233418.