Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-8260429

Internal LDAP channel binding property should be public

XMLWordPrintable

    • Icon: CSR CSR
    • Resolution: Withdrawn
    • Icon: P4 P4
    • 17
    • security-libs
    • None
    • source
    • low
    • Low compatibility risk. No code changes instead of renaming internal undocumented property.
    • Other
    • JDK

      Summary

      Make internal LDAP channel binding property public.

      Problem

      The fix for https://bugs.openjdk.java.net/browse/JDK-8245527 introduced an internal property "jdk.internal.sasl.tlschannelbinding" which is used to pass the TLS channel binding data to the SASL client. "jdk.internal.sasl.tlschannelbinding" property is not documented, so custom SASL Client providers can not rely on the name of this property.

      Solution

      1. Rename internal property to the "com.sun.sasl.tls.cbdata"
      2. Document property in the src/java.security.sasl/share/classes/module-info.java file

      Specification

      Add the following section into src/java.security.sasl/share/classes/module-info.java

      * @implNote
      * The following implementation specific property is supported by the
      * default SASL implementation in the JDK:
      * <ul>
      *     <li>{@code com.sun.sasl.tls.cbdata}:
      *         <br>The value of this property is the byte array representing the
      *         TLS Channel Binding data as defined in RFC-5929 and RFC-5056.
      *         LDAP Client generates TLS Channel Binding data on the base of
      *         TLS handshake and provides it to the SASL Client for authentication.
      *         "com.sun.sasl.tls.cbdata" property should not be specified
      *         explicitly. It is used internally to pass Channel Binding data from
      *         LDAP to SASL client.
      *     </li>
      * </ul>

            abakhtin Alexey Bakhtin
            revans Richard Evans
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: