| /openbmc/bmcweb/redfish-core/schema/oem/openbmc/json-schema/ |
| H A D | OpenBMCAccountService.v1_0_0.json | 34 "description": "Authorization Methods configuration.",
42 "description": "Authorization Methods configuration.",
60 "description": "Indicates whether BasicAuth authorization is enabled.",
61 … value of this property shall be a boolean indicating whether BasicAuth authorization is enabled.",
66 "description": "Indicates whether Cookie authorization is enabled.",
67 …The value of this property shall be a boolean indicating whether Cookie authorization is enabled.",
72 "description": "Indicates whether SessionToken authorization is enabled.",
73 …lue of this property shall be a boolean indicating whether SessionToken authorization is enabled.",
78 "description": "Indicates whether TLS authorization is enabled.",
79 …: "The value of this property shall be a boolean indicating whether TLS authorization is enabled.",
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/oem/openbmc/csdl/ |
| H A D | OpenBMCAccountService_v1.xml | 32 <Annotation Term="OData.Description" String="Authorization Methods configuration."/>
38 <Annotation Term="OData.Description" String="Authorization Methods configuration."/>
42 …<Annotation Term="OData.Description" String="Indicates whether BasicAuth authorization is enabled.…
43 …value of this property shall be a boolean indicating whether BasicAuth authorization is enabled."/>
47 … <Annotation Term="OData.Description" String="Indicates whether Cookie authorization is enabled."/>
48 …he value of this property shall be a boolean indicating whether Cookie authorization is enabled."/>
52 …<Annotation Term="OData.Description" String="Indicates whether SessionToken authorization is enabl…
53 …ue of this property shall be a boolean indicating whether SessionToken authorization is enabled."/>
57 … <Annotation Term="OData.Description" String="Indicates whether XToken authorization is enabled."/>
58 …he value of this property shall be a boolean indicating whether XToken authorization is enabled."/>
[all …]
|
| /openbmc/qemu/qapi/ |
| H A D | authz.json | 6 # User authorization
13 # The authorization policy result
28 # The authorization policy match format
43 # A single authorization rule.
66 # @rules: Authorization rules based on matching user
99 # @service: PAM service name to use for authorization
112 # network service that authorization object is associated with.
|
| /openbmc/qemu/docs/system/ |
| H A D | authz.rst | 1 .. _client authorization:
3 Client authorization
8 their identity. If the authorization identity database is scoped to the QEMU
12 finer grained authorization on clients post-authentication.
36 the certificate can be used as an identity in the QEMU authorization
47 in, it can be used with the QEMU authorization framework.
49 Authorization drivers
52 The QEMU authorization framework is a general purpose design with choice of
60 This authorization driver provides a simple mechanism for granting access
96 clients. This authorization driver provides a list mechanism for granting
[all …]
|
| /openbmc/docs/designs/ |
| H A D | ci-authorization.md | 1 # Continuous integration and authorization for OpenBMC
16 amount of authorization of contributors must occur to provide some level of
19 The project already has contributor authorization for CI. This proposal serves
25 The current authorization solution checks the user for membership in the
40 The existing method for authorization has a singular problem - the GitHub
49 An alternative authorization method for CI should:
53 - Enable a hierarchical trust model for user authorization (groups nested within
|
| H A D | redfish-authorization.md | 1 # Dynamic Redfish Authorization
9 The Redfish authorization subsystem controls which authenticated users have
12 DMTF has already defined the authorization model and schemas. This design is to
14 systems exposes interfaces to change authorization behavior at runtime without
19 ### Redfish Authorization Model
21 The Redfish authorization model consists of the privilege model and the
115 Redfish Privileges. An authorization action is performed when a BMCWeb route
130 As mentioned above, majority of the current Redfish authorization settings are
161 BMC implements a dynamic Redfish authorization system:
178 7. Existing systems with the static authorization shall work as if this feature
[all …]
|
| /openbmc/qemu/include/authz/ |
| H A D | base.h | 2 * QEMU authorization framework base class
38 * for providing an authorization driver for services
58 * @authz: the authorization object
81 * @authzid: ID of the authorization object
|
| H A D | simple.h | 2 * QEMU simple authorization driver
37 * This authorization driver provides a simple mechanism
|
| H A D | list.h | 2 * QEMU list authorization driver
38 * This authorization driver provides a list mechanism
|
| H A D | pamacct.h | 2 * QEMU PAM authorization driver
38 * This authorization driver provides a PAM mechanism
|
| H A D | listfile.h | 2 * QEMU list file authorization driver
38 * This authorization driver provides a file mechanism
|
| /openbmc/openbmc/poky/meta/recipes-extended/pam/libpam/pam.d/ |
| H A D | common-account | 2 # /etc/pam.d/common-account - authorization settings common to all services
5 # and should contain a list of the authorization modules that define
|
| /openbmc/openbmc/meta-phosphor/recipes-extended/pam/libpam/pam.d/ |
| H A D | common-account | 2 # /etc/pam.d/common-account - authorization settings common to all services
5 # and should contain a list of the authorization modules that define
|
| /openbmc/openbmc/meta-ibm/recipes-extended/pam/libpam/pam.d/ |
| H A D | common-account | 2 # /etc/pam.d/common-account - authorization settings common to all services
5 # and should contain a list of the authorization modules that define
|
| /openbmc/bmcweb/ |
| H A D | README.md | 42 ### Authorization subsection
44 All authorization in bmcweb is determined at routing time, and per route, and
|
| /openbmc/qemu/tests/tcg/aarch64/ |
| H A D | pauth-2.c | 39 /* A valid salt must produce a valid authorization. */ in do_test()
44 * An invalid salt usually fails authorization, but again there in do_test()
|
| /openbmc/openbmc/meta-security/meta-tpm/recipes-tpm1/openssl-tpm-engine/files/ |
| H A D | 0002-libtpm-support-env-TPM_SRK_PW.patch | 42 - if (!tpm_engine_get_auth(ui, (char *)auth, 128, "SRK authorization: ",
64 + "SRK authorization: ", cb_data)) {
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Channel/ |
| H A D | ChannelAccess.interface.yaml | 3 is used for channel authorization. Application must determine channel level
|
| /openbmc/openbmc/poky/meta/recipes-graphics/xorg-app/ |
| H A D | xauth_1.1.4.bb | 3 DESCRIPTION = "X application to edit and display the authorization \
|
| /openbmc/entity-manager/schemas/ |
| H A D | satellite_controller.json | 18 "description": "Type of authorization to use with satellite controller",
|
| /openbmc/openbmc/poky/meta/files/common-licenses/ |
| H A D | curl | 10 …he sale, use or other dealings in this Software without prior written authorization of the copyrig…
|
| H A D | MIT-open-group | 22 or other dealings in this Software without prior written authorization
|
| H A D | XFree86-1.0 | 22 in this Software without prior written authorization from the XFree86 Project.
|
| /openbmc/openbmc/meta-openembedded/meta-networking/recipes-support/fwknop/ |
| H A D | fwknop_2.6.11.bb | 1 SUMMARY = "fwknop - Single Packet Authorization"
|
| /openbmc/u-boot/Licenses/ |
| H A D | x11.txt | 23 this Software without prior written authorization from the X Consortium.
|