From 5e129393085ba01c598c33f6585ff0ebc5cb36d5 Mon Sep 17 00:00:00 2001 From: Tim Perry Date: Thu, 27 Aug 2026 18:42:22 +0100 Subject: [PATCH] doc: remove outdated TLS authorized warning Signed-off-by: Tim Perry --- doc/api/tls.md | 17 ++++++++--------- 1 file changed, 8 insertions(+), 9 deletions(-) diff --git a/doc/api/tls.md b/doc/api/tls.md index 34f8c3b99e93..c8e12eaacf62 100644 --- a/doc/api/tls.md +++ b/doc/api/tls.md @@ -1094,6 +1094,11 @@ property is set only when `tlsSocket.authorized === false`. * Type: {boolean} @@ -1103,15 +1108,10 @@ specified when creating the `tls.TLSSocket` instance, otherwise `false`. The peer certificate is only verified during a full TLS handshake. When a connection is established by resuming a previous session (see -[Session Resumption][]), verification is not repeated. If the client -presented a certificate in the original handshake, `authorized` and +[Session Resumption][]), verification is not repeated: `authorized` and `authorizationError` carry the result stored with the session, including -any verification error. On TLS 1.3, a client that sent no certificate at -all can resume a session and report `authorized` as `true`, while -[`tls.TLSSocket.getPeerCertificate()`][] returns an empty object. Servers -that authorize clients manually with `rejectUnauthorized: false` should -therefore also check [`tls.TLSSocket.isSessionReused()`][] and that a peer -certificate is present. +any verification error and the case where the client presented no +certificate at all. ### `tlsSocket.disableRenegotiation()` @@ -2625,7 +2625,6 @@ added: v0.11.3 [`tls.TLSSocket.getProtocol()`]: #tlssocketgetprotocol [`tls.TLSSocket.getSession()`]: #tlssocketgetsession [`tls.TLSSocket.getTLSTicket()`]: #tlssocketgettlsticket -[`tls.TLSSocket.isSessionReused()`]: #tlssocketissessionreused [`tls.TLSSocket.servername`]: #tlssocketservername [`tls.TLSSocket`]: #class-tlstlssocket [`tls.connect()`]: #tlsconnectoptions-callback