docs: Updated Connection URI doc to clearify certs order
What the developer wrote
Authored by ShahanaFarooqui
docs: Updated Connection URI doc to clearify certs order
Changelog-None.
What changed, and why it matters
This commit only rewords a documentation sentence to make clearer the order in which three certificate pieces should be combined. No code, configuration, or security behavior changed.
No security action needed. Treat as a normal documentation improvement.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies three identical descriptions in doc/developers-guide/app-development.md for the certs query parameter used by commando, clnrest, and clngrpc connection URIs. The old text said ‘Base64-encoded concatenation of client key, client cert, and CA cert’; the new text says ‘A Base64-encoded sequence created by concatenating the client key, client certificate, and CA certificate, in that order.’ The semantic content (key, then client cert, then CA cert) is unchanged; only clarity is improved.
Changed components
doc/developers-guide/app-development.mdInspect captured patch +3 / −3
diff --git a/doc/developers-guide/app-development.md b/doc/developers-guide/app-development.md
index 14645d44..57276ed5 100644
--- a/doc/developers-guide/app-development.md
+++ b/doc/developers-guide/app-development.md
@@ -32,7 +32,7 @@ commando+<protocol>://<cln-host>:<ws-port>?pubkey=<pubkey>&rune=<rune>&invoiceRu
- pubkey: Node's public key (hex encoded)
- rune: Authentication rune for general commands
- invoiceRune: Specific rune for invoice creation (optional)
-- certs: Base64-encoded concatenation of client key, client cert, and CA cert
+- certs: A Base64-encoded sequence created by concatenating the client key, client certificate, and CA certificate, in that order.
#### Example:
@@ -50,7 +50,7 @@ clnrest+<protocol>://<rest-host>:<rest-port>?rune=<rune>&certs=<combined-base64-
- rest-host: Hostname or IP address of the REST interface
- rest-port: REST API port (typically 3010)
- rune: Authentication rune for REST API access
-- certs: Base64-encoded concatenation of client key, client cert, and CA cert
+- certs: A Base64-encoded sequence created by concatenating the client key, client certificate, and CA certificate, in that order.
#### Example:
@@ -69,7 +69,7 @@ clngrpc://<grpc-host>:<grpc-port>?pubkey=<pubkey>&protoPath=<path-to-proto>&cert
- grpc-port: gRPC port (typically 9736)
- pubkey: Node's public key (hex encoded)
- protoPath: Path to protocol buffer definition file (typically https://github.com/ElementsProject/lightning/tree/master/cln-grpc/proto)
-- certs: Base64-encoded concatenation of client key, client cert, and CA cert
+- certs: A Base64-encoded sequence created by concatenating the client key, client certificate, and CA certificate, in that order.
#### Example:
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.