| /openbmc/openbmc-test-automation/gui/test/access_control/ |
| H A D | test_obmc_gui_local_users.robot | 3 Documentation Test OpenBMC GUI "Local users" sub-menu of "Access control".
14 ${xpath_select_user} //input[contains(@class,"bmc-table__checkbox-input")]
15 ${xpath_edit_user} //button[@aria-label="Edit"]
16 ${xpath_delete_user} //button[@aria-label="Delete"]
18 ${xpath_add_user} //button[text()[contains(.,"Add user")]]
29 Verify Existence Of All Sections In Local User Management Page
30 [Documentation] Verify existence of all sections in local user management page.
36 Verify Existence Of All Buttons In Local User Management Page
37 [Documentation] Verify existence of all buttons in local user management page.
46 Verify Existence Of All Input Boxes In Local User Management Page
[all …]
|
| /openbmc/openbmc/meta-phosphor/classes/ |
| H A D | obmc-phosphor-image.bbclass | 5 # - obmc-bmc-state-mgmt - OpenBMC BMC state management
6 # - obmc-bmcweb - OpenBMC webserver
7 # - obmc-chassis-mgmt - OpenBMC chassis management
8 # - obmc-chassis-state-mgmt - OpenBMC chassis state management
9 # - obmc-console - OpenBMC serial over LAN
10 # - obmc-dbus-monitor - OpenBMC dbus monitoring
11 # - obmc-debug-collector - OpenBMC debug collector
12 # - obmc-devtools - OpenBMC development and debugging tools
13 # - obmc-fan-control - OpenBMC fan management
14 # - obmc-fan-mgmt - Deprecated - use obmc-fan-control instead
[all …]
|
| /openbmc/openbmc-test-automation/gui/gui_test/security_and_access_menu/ |
| H A D | test_user_management_sub_menu.robot | 3 Documentation Test OpenBMC GUI "User management" sub-menu of "Security and access".
16 ${xpath_user_management_heading} //h1[text()="User management"]
17 ${xpath_select_user} //input[contains(@class,"custom-control-input")]
19 ${xpath_add_user} //button[contains(text(),'Add user')]
20 ${xpath_edit_user} //*[@data-test-id='userManagement-tableRowAction-edit-0']
21 ${xpath_delete_user} //*[@data-test-id='userManagement-tableRowAction-delete-1']
22 ${xpath_account_status_enabled_button} //*[@data-test-id='userManagement-radioButton-statusEnable…
23 ${xpath_account_status_disabled_button} //*[@data-test-id='userManagement-radioButton-statusDisabl…
24 ${xpath_username_input_button} //*[@data-test-id='userManagement-input-username']
25 ${xpath_privilege_list_button} //*[@data-test-id='userManagement-select-privilege']
[all …]
|
| /openbmc/qemu/docs/interop/ |
| H A D | vhost-user.json | 1 # -*- Mode: Python -*-
7 # Marc-André Lureau <marcandre.lureau@redhat.com>
10 # later. See the COPYING file in the top-level directory.
14 # vhost user backend discovery & capabilities
21 # List the various vhost user backend types.
34 # @rproc-serial: virtio remoteproc serial link
55 'rproc-serial',
65 # List of vhost user "block" features.
67 # @read-only: The --read-only command line option is supported.
68 # @blk-file: The --blk-file command line option is supported.
[all …]
|
| H A D | index.rst | 1 ------------------------------------------------
2 System Emulation Management and Interoperability
3 ------------------------------------------------
14 dbus-vmstate
15 dbus-display
16 live-block-operations
19 prl-xml
22 pr-helper
23 qmp-spec
24 qemu-ga
[all …]
|
| /openbmc/docs/architecture/ |
| H A D | user-management.md | 1 # User Management - OpenBMC - Design document
6 user-management components. The implementation detail is beyond the scope of
11 1. Use common user-management (e.g. phosphor-user-manager) rather than
12 application-based user-management. Especially, avoid IPMI based
13 user-management.
14 2. For security reasons, avoid transmitting passwords over any D-Bus API.
15 Observe this rule even while creating, modifying or authenticating the user.
16 3. Have applications use the PAM module to authenticate the user instead of
17 relying on a D-Bus API-based approach.
18 4. User creation has to be generic in nature wherever possible.
[all …]
|
| /openbmc/docs/ |
| H A D | features.md | 5 - [BMCWeb][] HTTP/Web server
6 - [WebUI Vue][] web application
7 - REST Management: [BMCWeb Redfish][], [Phosphor REST APIs][] includes [Host
8 management REST APIs][]
9 - [D-Bus interfaces][] describes internal interfaces
10 - [D-Bus Object Mapper][]
11 - [Remote KVM][]
12 - [IPMI in band][] and [IPMI out of band][]
13 - Full IPMI 2.0 Compliance with DCMI
14 - SSH based SOL: [How to use][sol how to use]
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-python/recipes-devtools/python/ |
| H A D | python3-flask-user_0.6.19.bb | 1 SUMMARY = "Customizable user account management for Flask"
2 DESCRIPTION = "Customizable User Account Management for Flask; Register \
5 HOMEPAGE = " https://github.com/lingthio/Flask-User"
6 LICENSE = "BSD-2-Clause"
11 PYPI_PACKAGE = "Flask-User"
17 python3-babel \
18 python3-blinker \
19 python3-flask \
20 python3-flask-login \
21 python3-flask-mail \
[all …]
|
| H A D | python3-flask-login_0.6.3.bb | 1 SUMMARY = "User session management for Flask"
2 DESCRIPTION = "Flask-Login provides user session management for Flask. \
5 HOMEPAGE = " https://github.com/maxcountryman/flask-login"
11 PYPI_PACKAGE = "Flask-Login"
16 RDEPENDS:${PN}:class-target = "python3-flask"
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/User/ |
| H A D | README.md | 1 # User Management
5 User Manager service exposes D-Bus methods for user management operations.
7 ### User Manager Interface
9 User manager interface `xyz.openbmc_project.User.Manager` provides following
12 #### xyz.openbmc_project.User.Manager interface
16 - CreateUser - To create new user to the system.
17 - RenameUser - To rename existing user to new name in the system.
21 - AllGroups - To list all the groups supported in the system.
22 - AllPrivileges - To list all the privileges supported in the system.
26 - UserRenamed - Signal sent out when user is renamed in the system.
[all …]
|
| H A D | PrivilegeMapperEntry.interface.yaml | 5 - name: GroupName
9 LDAP, the GroupName will be the LDAP group the user is part of.
11 - xyz.openbmc_project.Common.Error.InternalFailure
12 - xyz.openbmc_project.Common.Error.InvalidArgument
13 - xyz.openbmc_project.User.Common.Error.PrivilegeMappingExists
14 - name: Privilege
18 xyz.openbmc_project.User.Manager.AllPrivileges.
22 https://github.com/openbmc/docs/blob/master/architecture/user-management.md
25 - xyz.openbmc_project.Common.Error.InternalFailure
26 - xyz.openbmc_project.Common.Error.InvalidArgument
|
| H A D | PrivilegeMapper.interface.yaml | 2 Implement this interface to set the privilege of the user based on the group
5 xyz.openbmc_project.User.PrivilegeMapperEntry. For example in the case of
7 /xyz/openbmc_project/user/ldap/privilege_mapper/<id>. The <id> will be a
10 xyz.openbmc_project.User.Common.Error.PrivilegeMappingExists. To modify the
12 xyz.openbmc_project.User.PrivilegeMapperEntry interface needs to be set. Any
15 org.freedesktop.DBus.ObjectManager interface to figure out the D-Bus object
19 - name: Create
23 - name: GroupName
27 of LDAP, the GroupName will be the LDAP group the user is part
29 - name: Privilege
[all …]
|
| /openbmc/openbmc/meta-phosphor/recipes-phosphor/packagegroups/ |
| H A D | packagegroup-obmc-apps.bb | 1 SUMMARY = "OpenBMC - Applications"
8 ${PN}-bmc-state-mgmt \
9 ${PN}-bmcweb \
10 ${PN}-chassis-state-mgmt \
11 ${PN}-console \
12 ${PN}-dbus-monitor \
13 ${PN}-extras \
14 ${PN}-devtools \
15 ${PN}-fan-control \
16 ${PN}-health-monitor \
[all …]
|
| /openbmc/openbmc-tools/openbmctool/ |
| H A D | README.md | 12 - `-H`: The hostname or IP for the BMC
13 - `-U`: The username One of the password options:
14 - `-P`: The password, provided in-line
15 - `-A`: Prompt for a password
16 - `-E`: Take the password from envvar `OPENBMCTOOL_PASSWORD`
18 ## Enabling and Disabling Local BMC User Accounts
20 The local user accounts on the BMC, such as root, can be disabled, queried, and
21 re-enabled with the `local_users` sub-command.
23 Important: After disabling local users, an LDAP user will need to be used for
27 To view current local user account status:
[all …]
|
| /openbmc/openbmc/meta-phosphor/recipes-phosphor/images/ |
| H A D | obmc-phosphor-image.bb | 1 DESCRIPTION = "Image with Phosphor, a software stack for hardware management \
2 in devices with baseboard management controllers. The image supports the \
4 LICENSE = "Apache-2.0"
6 inherit obmc-phosphor-image
9 # Users should instead rely on /etc/os-release.
14 obmc-bmc-state-mgmt \
15 obmc-bmcweb \
16 obmc-chassis-mgmt \
17 obmc-chassis-state-mgmt \
18 obmc-console \
[all …]
|
| /openbmc/bmcweb/docs/ |
| H A D | DBUS_USAGE.md | 6 - Do not require (ie set 500 internal error on) an implementation present a
10 - If an implementation presents a property that doesn't match the type specified
12 - If the DBus interface definition has an "unknown" or "unspecified" value,
15 - All DBus interfaces on all object paths are optional. An object missing an
18 - bmcweb will code to the DBus interface itself. This means that daemons are
19 expected to handle functionally bad, but DBus-correct input in their own
21 duplication in input processing between the various user-facing daemons.
22 - There are interfaces for which there is an expectation that there will only
23 ever be one producer in the project (ex bmc networking, user management). In
26 that multiple implementations exist (ex, CPU management, Sensors).
|
| /openbmc/phosphor-certificate-manager/ |
| H A D | README.md | 1 # phosphor-certificate-manager
3 Certificate management allows to replace the existing certificate and private
5 management allows the user to install both the server and client certificates.
10 `meson builddir && ninja -C builddir`.
14 Multiple instances of `phosphor-certificate-manager` are usually run on the bmc
15 to support management of different types of certificates.
18 Usage: ./phosphor-certificate-manager [options]
20 --help Print this menu
21 --type certificate type
23 --endpoint d-bus endpoint
[all …]
|
| /openbmc/pam-ipmi/src/pam_ipmicheck/ |
| H A D | pam_ipmicheck.c | 8 // http://www.apache.org/licenses/LICENSE-2.0
31 * This module is intended to verify special group user password matches the
35 * used for other purpose like authentication, session & account management.
55 /* Password Management API's */
59 int retval = -1; in pam_sm_chauthtok()
60 const char *user = NULL; in pam_sm_chauthtok() local
79 "password - unable to get new password"); in pam_sm_chauthtok()
83 retval = pam_get_user(pamh, &user, NULL); in pam_sm_chauthtok()
90 // Verify whether the user belongs to special group. in pam_sm_chauthtok()
93 while (*(grp->gr_mem) != NULL) { in pam_sm_chauthtok()
[all …]
|
| /openbmc/ipmitool/ |
| H A D | README | 4 ipmitool-devel@lists.sourceforge.net
9 the Intelligent Platform Management Interface. IPMI is an open standard
12 service processor (or Baseboard Management Controller, BMC) is the brain
13 behind platform management and its primary purpose is to handle the
16 The ipmitool program provides a simple command-line interface to this BMC.
26 Microsystems. Sun had just embarked on a new line of general-purpose x86
29 feature for my systems in the lab and from there it grew into a multi-
33 ipmitool was not written to provide large-scale (aka Enterprise) management
37 who like the simplicity and scriptability of command-line utilities, as
44 that supports the IPMI specification. Many x86-based servers are now
[all …]
|
| /openbmc/docs/designs/management-console/ |
| H A D | VMI_Certificate_Exchange.md | 11 - HMC - Hardware Management Console : Management console for IBM enterprise
13 - PHYP - Power Hypervisor : This orchestrates and manages system virtualization.
14 - VMI - Virtual Management Interface : The interface facilitating communications
16 - KVM - Kernel Virtual Machine : Open source virtualization software
20 On enterprise POWER systems, the Hardware management console (HMC) needs to
21 establish a secure connection to the Virtualization management interface (VMI)
22 for virtualization management.
30 BMC needs to provide certificate exchange functionality to management console
33 - Host firmware (PHYP) does not have authentication mechanism.
34 - VMI trusts that BMC has authenticated and verified the authenticity of any
[all …]
|
| /openbmc/openbmc-test-automation/ |
| H A D | README.md | 5 - DMTF Redfish
6 - Out-of-band IPMI
7 - SSH to BMC and Host OS
8 - [Legacy REST](https://github.com/openbmc/openbmc-test-automation/releases/tag/v4.0-stable)
12 - Power on/off
13 - Reboot Host
14 - Reset BMC
15 - Code update BMC and host
16 - Power management
17 - Fan controller
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Certs/ |
| H A D | README.md | 1 # BMC Certificate management
5 Certificate management allows to replace the existing certificate and private
7 and private key file. Certificate management allows the user to install both the
12 ### Signed Certificate upload Design flow(Pre-generated)
14 - The REST Server copies the certificate and private key file to a temporary
16 - REST server should map the URI to the target DBus application (Certs) object.
17 The recommendation for the D-Bus application implementing certificate D-Bus
19 - The URI /xyz/openbmc_project/certs/server/https maps to instance of the
21 - The URI /xyz/openbmc_project/certs/client/ldap maps to instance of the
23 - The URI /xyz/openbmc_project/certs/authority/truststore maps to instance of
[all …]
|
| /openbmc/docs/designs/ |
| H A D | bmc-boot-ready.md | 23 services have completed running, there is a window there that a user could
29 [state][2] management interfaces in a system. The BMC, Chassis, and Host. Within
33 `multi-user.target` has successfully started all if its services.
37 1. D-Bus objects don't exist until the backend is prepared to handle them.
38 2. If a user tries something that system is not in proper state to handle then
40 3. If a user tries something that system is not in proper state to handle then
43 Option 1 is challenging because D-Bus interfaces provided by OpenBMC state
44 applications have a mix of read-only properties (like current state) and
51 the op-panel code now need to properly handle error codes like this. You can
55 Option 3 is the most user friendly option. No client or OpenBMC application
[all …]
|
| /openbmc/docs/designs/oem/ibm/ |
| H A D | system-power-mode.md | 11 Power management on POWER platforms needs assistance from the BMC for managing
23 need to send the commands if the user changes the mode or idle power save
42 - Static
43 - Power Saver
44 - Maximum Performance
51 - Enabled / Disabled
52 - Enter Delay Time (in seconds)
53 - Enter Utilization threshold (percentage)
54 - Exit Delay Time (in seconds)
55 - Exit Utilization threshold (percentage)
[all …]
|
| /openbmc/openbmc/meta-openembedded/meta-oe/recipes-support/switchtec-user/ |
| H A D | switchtec-user_4.2.bb | 1 SUMMARY = "Easy to use CLI and C library for communicating with Microsemi's Switchtec management in…
2 HOMEPAGE = "https://github.com/Microsemi/switchtec-user"
10 SRC_URI = "git://github.com/Microsemi/switchtec-user.git;protocol=https;branch=master"
15 inherit autotools-brokensep pkgconfig
|