| /openbmc/bmcweb/http/ |
| H A D | utility.hpp | 238 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 D | test_inband_bmc_auth_reset.robot | 26 @{credentials}= Create List ${OPENBMC_USERNAME} ${OPENBMC_PASSWORD}
27 ${data}= create dictionary data=@{credentials}
|
| /openbmc/openbmc-tools/reboot-ping-pong/ |
| H A D | rpp | 88 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 D | meson.build | 5 'bootstrap-credentials-oem-cmds.cpp',
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-extended/pam/ |
| H A D | pam-plugin-ccreds_11.bb | 1 SUMMARY = "PAM cached credentials module"
|
| /openbmc/openbmc-test-automation/extended/ |
| H A D | test_bmc_stress_buster.robot | 64 @{credentials}= Create List ${rest_username} ${rest_password}
65 ${data}= Create Dictionary data=@{credentials}
|
| /openbmc/docs/designs/ |
| H A D | expired-password.md | 26 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 D | certificate-revocation-list.md | 36 Instead, Google has a dedicated daemon for credentials installation, and this
72 to reload newly installed credentials.
|
| H A D | redfish-tls-user-authentication.md | 224 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 D | test_bmc_connections.robot | 150 # 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 D | console.md | 13 port 2200. Use the same login credentials you would for a normal ssh session:
|
| /openbmc/openbmc/meta-openembedded/meta-networking/files/waf-cross-answers/ |
| H A D | cross-answers-aarch64.txt | 30 Checking whether we can use Linux thread-specific credentials: OK
|
| H A D | cross-answers-mips64el.txt | 30 Checking whether we can use Linux thread-specific credentials: OK
|
| H A D | cross-answers-powerpc.txt | 31 Checking whether we can use Linux thread-specific credentials: OK
|
| H A D | cross-answers-aarch64_be.txt | 30 Checking whether we can use Linux thread-specific credentials: OK
|
| H A D | cross-answers-mips.txt | 31 Checking whether we can use Linux thread-specific credentials: OK
|
| H A D | cross-answers-riscv32.txt | 31 Checking whether we can use Linux thread-specific credentials with 32-bit system calls: OK
|
| H A D | cross-answers-powerpc64.txt | 31 Checking whether we can use Linux thread-specific credentials: OK
|
| H A D | cross-answers-powerpc64le.txt | 31 Checking whether we can use Linux thread-specific credentials: OK
|
| H A D | cross-answers-armeb.txt | 31 Checking whether we can use Linux thread-specific credentials with 32-bit system calls: OK
|
| H A D | cross-answers-x86_64.txt | 30 Checking whether we can use Linux thread-specific credentials: OK
|
| H A D | cross-answers-mipsel.txt | 31 Checking whether we can use Linux thread-specific credentials: OK
|
| H A D | cross-answers-i686.txt | 31 Checking whether we can use Linux thread-specific credentials with 32-bit system calls: OK
|
| H A D | cross-answers-mips64.txt | 30 Checking whether we can use Linux thread-specific credentials: OK
|
| H A D | cross-answers-riscv64.txt | 30 Checking whether we can use Linux thread-specific credentials: OK
|