You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/libnetconf.doc
+9Lines changed: 9 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -391,6 +391,15 @@
391
391
* Another option for authorized clients is to reference another endpoint's clients, however be careful not to create a cyclic reference
392
392
* (see ::nc_server_config_add_ssh_endpoint_client_ref()). An authorized client MUST authenticate to all of it's configured authentication methods.
393
393
*
394
+
* \anchor ln2doc_pubkey
395
+
* The Public Key authentication method is supported. If you wish to use this method, you need to specify the given user's
396
+
* public keys, which will be compared with the key(s) presented by the SSH client when authenticating. One option is to configure
397
+
* the public keys directly in the ietf-netconf-server YANG data (inline-definition). Other option is to configure the keys' data
398
+
* in the ietf-trustore module's YANG data and then reference them (truststore-reference). The final option is to set the global
399
+
* path to file with public keys. This path may contain special tokens, see ::nc_server_ssh_set_authkey_path_format().
400
+
* If the path is set and the use-system-keys container is present in the data for the client wishing to authenticate,
401
+
* then the keys from the file will be used for authentication.
402
+
*
394
403
* \anchor ln2doc_kbdint
395
404
* The Keyboard Interactive authentication method is also supported. It can be done in three ways.
396
405
* If libpam is found, Linux PAM is used to handle the authentication. You need to specify the service name using ::nc_server_ssh_set_pam_conf_filename().
0 commit comments