Home
last modified time | relevance | path

Searched refs:credentials (Results 1 – 25 of 63) sorted by relevance

123

/openbmc/bmcweb/http/
H A Dutility.hpp238 std::string credentials = "Basic "; in createBasicAuthHeader() local
240 enc.encode(username, credentials); in createBasicAuthHeader()
241 enc.encode(":", credentials); in createBasicAuthHeader()
242 enc.encode(password, credentials); in createBasicAuthHeader()
243 enc.finalize(credentials); in createBasicAuthHeader()
244 return credentials; in createBasicAuthHeader()
/openbmc/openbmc-test-automation/openpower/
H A Dtest_inband_bmc_auth_reset.robot26 @{credentials}= Create List ${OPENBMC_USERNAME} ${OPENBMC_PASSWORD}
27 ${data}= create dictionary data=@{credentials}
/openbmc/openbmc-tools/reboot-ping-pong/
H A Drpp88 self.entity.console.credentials.username.encode()
92 self.entity.console.credentials.password.encode()
136 self.entity.console.credentials.username,
143 self.entity.console.credentials.password.encode()
/openbmc/phosphor-host-ipmid/oem/nvidia/
H A Dmeson.build5 'bootstrap-credentials-oem-cmds.cpp',
/openbmc/qemu/docs/system/
H A Dtls.rst240 QEMU has a standard mechanism for loading x509 credentials that will be
243 for the system emulators. Each set of credentials loaded should be given
245 credentials can be used for multiple network backends, so VNC,
246 migration, NBD, character devices can all share the same credentials.
247 Note, however, that credentials for use in a client endpoint must be
258 dynamically generate DH parameters when loading the credentials.
260 The ``endpoint`` parameter indicates whether the credentials will be
274 To load server credentials with client certificate validation enabled
280 while to load client credentials use
287 parameter which expects the ID of the TLS credentials object. For
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/pam/
H A Dpam-plugin-ccreds_11.bb1 SUMMARY = "PAM cached credentials module"
/openbmc/openbmc-test-automation/extended/
H A Dtest_bmc_stress_buster.robot64 @{credentials}= Create List ${rest_username} ${rest_password}
65 ${data}= Create Dictionary data=@{credentials}
/openbmc/docs/designs/
H A Dexpired-password.md26 1. Success, when the access credentials (such as username and password) are
28 2. Failure, when either the access credentials are invalid or the account being
31 3. PasswordChangeRequired, when the access credentials are correct and the
54 credentials, whether or not those credentials have expired and must be
103 credentials are otherwise correct and the reason for the authentication
109 The `/login` URI is enhanced. If it is used with correct credentials (userid
H A Dcertificate-revocation-list.md36 Instead, Google has a dedicated daemon for credentials installation, and this
72 to reload newly installed credentials.
H A Dredfish-tls-user-authentication.md224 credentials according to processing sequence. It is recommended for user to use
225 only one set of credentials/authentication data in a single request to be sure
247 login credentials without password, so verification of user existence cannot be
/openbmc/openbmc-test-automation/security/
H A Dtest_bmc_connections.robot150 # Every 100th iteration Login with correct credentials
231 [Documentation] Make invalid credentials Redfish login attempts continuously and
232 ... verify bmcweb stability by login to Redfish with valid credentials.
360 [Documentation] Continuous invalid credentials login attempts to Redfish and
361 ... login to Redfish with valid credentials at times and get failed login attempts.
371 Log To Console ${iter}th Redfish login with invalid credentials
/openbmc/docs/
H A Dconsole.md13 port 2200. Use the same login credentials you would for a normal ssh session:
/openbmc/qemu/qapi/
H A Dcrypto.json14 # The type of network endpoint that will be using the credentials.
482 # @verify-peer: if true the peer credentials will be verified once the
484 # credentials. (default: true)
489 # credentials will be acting as a client or as a server
535 # credentials (default: true)
/openbmc/openbmc/meta-openembedded/meta-networking/files/waf-cross-answers/
H A Dcross-answers-aarch64.txt30 Checking whether we can use Linux thread-specific credentials: OK
H A Dcross-answers-mips64el.txt30 Checking whether we can use Linux thread-specific credentials: OK
H A Dcross-answers-powerpc.txt31 Checking whether we can use Linux thread-specific credentials: OK
H A Dcross-answers-aarch64_be.txt30 Checking whether we can use Linux thread-specific credentials: OK
H A Dcross-answers-mips.txt31 Checking whether we can use Linux thread-specific credentials: OK
H A Dcross-answers-riscv32.txt31 Checking whether we can use Linux thread-specific credentials with 32-bit system calls: OK
H A Dcross-answers-powerpc64.txt31 Checking whether we can use Linux thread-specific credentials: OK
H A Dcross-answers-powerpc64le.txt31 Checking whether we can use Linux thread-specific credentials: OK
H A Dcross-answers-armeb.txt31 Checking whether we can use Linux thread-specific credentials with 32-bit system calls: OK
H A Dcross-answers-x86_64.txt30 Checking whether we can use Linux thread-specific credentials: OK
H A Dcross-answers-mipsel.txt31 Checking whether we can use Linux thread-specific credentials: OK
H A Dcross-answers-i686.txt31 Checking whether we can use Linux thread-specific credentials with 32-bit system calls: OK

123