Home
last modified time | relevance | path

Searched refs:CHAP (Results 1 – 14 of 14) sorted by relevance

/openbmc/bmcweb/redfish-core/include/generated/enums/
H A Dexternal_account_provider.hpp32 CHAP, enumerator
65 {TACACSplusPasswordExchangeProtocol::CHAP, "CHAP"},
H A Dnetwork_device_function.hpp29 CHAP, enumerator
75 {AuthenticationMethod::CHAP, "CHAP"},
H A Daccount_service.hpp52 CHAP, enumerator
119 {TACACSplusPasswordExchangeProtocol::CHAP, "CHAP"},
/openbmc/linux/Documentation/ABI/testing/
H A Dsysfs-ibft15 contain the CHAP name (and password), the reverse CHAP
/openbmc/linux/drivers/target/iscsi/
H A Discsi_target_parameters.h111 #define CHAP "CHAP" macro
116 #define INITIAL_AUTHMETHOD CHAP
H A Discsi_target_parameters.c884 strcmp(value, CHAP) && strcmp(value, NONE)) { in iscsi_check_string_or_list_value()
888 SPKM1, SPKM2, SRP, CHAP, NONE); in iscsi_check_string_or_list_value()
H A Discsi_target_tpg.c325 ret = iscsi_update_param_value(param, CHAP); in iscsit_tpg_enable_portal_group()
H A Discsi_target_configfs.c1318 if (iscsi_update_param_value(param, CHAP) < 0) in iscsi_disc_enforce_discovery_auth_store()
/openbmc/openbmc/poky/meta/recipes-connectivity/ppp/ppp/
H A Dpap2 # authentication via PAP, CHAP and similar protocols.
H A Dprovider1 # example configuration for a dialup connection authenticated with PAP or CHAP
/openbmc/u-boot/doc/
H A DREADME.iscsi27 provides mutual authentication using the CHAP protocol. It typically runs on
52 the mutual authentication using the CHAP protocol. After the authentication iPXE
/openbmc/qemu/docs/system/
H A Ddevice-url-syntax.rst.inc32 Example (CHAP username/password via URL):
38 Example (CHAP username/password via environment variables):
H A Dqemu-block-drivers.rst.inc580 using CHAP authentication for access control.
617 user = "CHAP username"
618 password = "CHAP password"
628 user = "CHAP username"
629 password = "CHAP password"
/openbmc/qemu/qapi/
H A Dblock-core.json4108 # @user: User name to log in with. If omitted, no CHAP authentication