<feed xmlns='http://www.w3.org/2005/Atom'>
<title>bmcweb/redfish-core/lib, branch master</title>
<subtitle>OpenBMC Web server</subtitle>
<id>https://git.raptorcs.com/git/bmcweb/atom?h=master</id>
<link rel='self' href='https://git.raptorcs.com/git/bmcweb/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bmcweb/'/>
<updated>2020-02-10T20:23:25+00:00</updated>
<entry>
<title>Add a pid controller size limit</title>
<updated>2020-02-10T20:23:25+00:00</updated>
<author>
<name>James Feist</name>
<email>james.feist@linux.intel.com</email>
</author>
<published>2020-02-07T20:23:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bmcweb/commit/?id=e69d9de2d9453ff301e727554dc74fa8bc0f8482'/>
<id>urn:sha1:e69d9de2d9453ff301e727554dc74fa8bc0f8482</id>
<content type='text'>
Right now there is no limit, so someone could attack
the bmc by adding a very large number of controllers.
Create a limit so this isn't possible.

Tested: Add / Remove functionality still works

Change-Id: Ib408293431250d93b0af71616a1668f6a3d0904a
Signed-off-by: James Feist &lt;james.feist@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>PID: Don't attempt to delete unknown objects</title>
<updated>2020-02-10T20:23:16+00:00</updated>
<author>
<name>James Feist</name>
<email>james.feist@linux.intel.com</email>
</author>
<published>2020-02-07T00:25:27+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bmcweb/commit/?id=6ee7f774bf6393d48c7215e02d6dbf00322bc9f5'/>
<id>urn:sha1:6ee7f774bf6393d48c7215e02d6dbf00322bc9f5</id>
<content type='text'>
This puts a block in to return early if we are asked
to delete something we can't find on D-Bus. This code
path was creating a segfault, but theres no reason to
continue after we can't find an object we are asked to
delete, so we can just avoid it. Also clean up the end
iterator dereference so it doesn't happen in any other
path.

Tested: Segfault goes away

Change-Id: I33622e5e8ab09fba0681e4f86f4a7068f6ef0be7
Signed-off-by: James Feist &lt;james.feist@linux.intel.com&gt;
</content>
</entry>
<entry>
<title>Update AccountService Privilege</title>
<updated>2020-02-10T18:34:06+00:00</updated>
<author>
<name>Gunnar Mills</name>
<email>gmills@us.ibm.com</email>
</author>
<published>2020-01-29T21:21:30+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bmcweb/commit/?id=3c5a376e005d97f5d586c5aa163267eb3b0381aa'/>
<id>urn:sha1:3c5a376e005d97f5d586c5aa163267eb3b0381aa</id>
<content type='text'>
"GET" should be a "Login" Privilege for the AccountService
resource. This makes sense, a "Readonly" and "Operator" user
should be able to see properties like MaxPasswordLength and
MinPasswordLength since they are allowed to change their own
password.

This was changed in Redfish 2019.3, redfish issue 1914 explains
more.

From Redfish_1.0.4_PrivilegeRegistry.json:
            "Entity": "AccountService",
            "OperationMap": {
                "GET": [
                    {
                        "Privilege": [
                            "Login"
                        ]
                    }
                ],
                "HEAD": [
                    {
                        "Privilege": [
                            "Login"
                        ]
                    }
                ],
                "PATCH": [
                    {
                        "Privilege": [
                            "ConfigureUsers"
                        ]
                    }
                ],
                "PUT": [
                    {
                        "Privilege": [
                            "ConfigureUsers"
                        ]
                    }
                ],
                "DELETE": [
                    {
                        "Privilege": [
                            "ConfigureUsers"
                        ]
                    }
                ],
                "POST": [
                    {
                        "Privilege": [
                            "ConfigureUsers"
                        ]
                    }
                ]

Change-Id: Iab8acbac97a58aed865bf94f665d6c9a32de81dd
Tested: Build for Witherspoon and AccountService looks good.
Signed-off-by: Gunnar Mills &lt;gmills@us.ibm.com&gt;
</content>
</entry>
<entry>
<title>Add Power Supply Attributes</title>
<updated>2020-02-07T21:15:21+00:00</updated>
<author>
<name>Gunnar Mills</name>
<email>gmills@us.ibm.com</email>
</author>
<published>2019-08-15T20:26:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bmcweb/commit/?id=42cbe53889b5f2d358d1174245df51a23efcb3f8'/>
<id>urn:sha1:42cbe53889b5f2d358d1174245df51a23efcb3f8</id>
<content type='text'>
Map DeratingFactor from PowerSupplyAttributes.interface.yaml
to the Redfish property PowerSupply "EfficiencyPercent".

Only do this call when the "Power" schema is called.
Use the InventoryItem class introduced in
adc4f0db57568c5e5d2a3398fce00dbb050a3b72

Tested: Power, Thermal, all look good.
        Passed the Redfish Validator.
  "PowerSupplies": [
    {
      "@odata.id": "/redfish/v1/Chassis/chassis/Power#/PowerSupplies/0",
      "EfficiencyPercent": 90,
      "IndicatorLED": "Off",
      "Manufacturer": "",
      "MemberId": "powersupply0",
      "Model": "2B1D",
      "Name": "powersupply0",
      "PartNumber": "01KL471",
      "PowerInputWatts": 12.0,
      "SerialNumber": "71G370",
      "Status": {
        "Health": "OK",
        "State": "Enabled"
      }
    },

Change-Id: I344577a7a3d72cd37d5f6bab03edbdce13b9f764
Signed-off-by: Gunnar Mills &lt;gmills@us.ibm.com&gt;
</content>
</entry>
<entry>
<title>Move Crashdump to OemCrashdump</title>
<updated>2020-02-07T19:07:33+00:00</updated>
<author>
<name>Gunnar Mills</name>
<email>gmills@us.ibm.com</email>
</author>
<published>2020-02-06T21:29:57+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bmcweb/commit/?id=4f50ae4b71fc0821f0013cbf586579f7c9a17a2c'/>
<id>urn:sha1:4f50ae4b71fc0821f0013cbf586579f7c9a17a2c</id>
<content type='text'>
All other Oem Schemas start with Oem.
This is used by the update_schemas.py to determine an Oem
schema and is a reasonable requirement for Oem schemas.

https://github.com/openbmc/bmcweb/blob/a3268f98f308ca7c8660b1ace44d5b9a40be204b/scripts/update_schemas.py#L43

Tested: Ran the validator against this change on a Witherspoon
        with BMCWEB_ENABLE_REDFISH_CPU_LOG enabled and OemCheck
        true. Validator passed. Might be worth running on a
        system that actually uses BMCWEB_ENABLE_REDFISH_CPU_LOG.

curl -k https://${bmc}/redfish/v1/Systems/system/LogServices/Crashdump
{
  "@odata.context": "/redfish/v1/$metadata#LogService.LogService",
  "@odata.id": "/redfish/v1/Systems/system/LogServices/Crashdump",
  "@odata.type": "#LogService.v1_1_0.LogService",
  "Actions": {
    "#LogService.ClearLog": {
      "target": "/redfish/v1/Systems/system/LogServices/Crashdump/Actions/LogService.ClearLog"
    },
    "Oem": {
      "#Crashdump.OnDemand": {
        "target": "/redfish/v1/Systems/system/LogServices/Crashdump/Actions/Oem/Crashdump.OnDemand"
      }
    }
  },
  "Description": "Oem Crashdump Service",
  "Entries": {
    "@odata.id": "/redfish/v1/Systems/system/LogServices/Crashdump/Entries"
  },
  "Id": "Oem Crashdump",
  "MaxNumberOfRecords": 3,
  "Name": "Open BMC Oem Crashdump Service",
  "OverWritePolicy": "WrapsWhenFull"
}

Change-Id: Iacc11be1284b99c2ed9a6c2ca0a936bd97855afb
Signed-off-by: Gunnar Mills &lt;gmills@us.ibm.com&gt;
</content>
</entry>
<entry>
<title>Add support to fetch the 'Updateable' components</title>
<updated>2020-02-03T17:57:27+00:00</updated>
<author>
<name>AppaRao Puli</name>
<email>apparao.puli@linux.intel.com</email>
</author>
<published>2020-01-28T21:06:32+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bmcweb/commit/?id=3f8a743a5179eb618518ff04b98202a997342bb0'/>
<id>urn:sha1:3f8a743a5179eb618518ff04b98202a997342bb0</id>
<content type='text'>
Currently 'Updateable' property value in SoftwareInventory schema
is hardcoded. Added support to  look through the updateable
software associations objects and use it for 'Updateable'
Redfish property in SoftwareInventory.

Tested:
 - Checked 'Updateable' Property value for both
   programmable and non-programmable firmware inventory
   components and it works as expected.
 - Ran the Redfish validator and no new issues found.

Signed-off-by: AppaRao Puli &lt;apparao.puli@linux.intel.com&gt;
Change-Id: Ia24f942f3afe49674ec3628cac0356a5496ef337
</content>
</entry>
<entry>
<title>Enhance return value from pamAuthenticateUser</title>
<updated>2020-01-30T16:24:12+00:00</updated>
<author>
<name>Joseph Reynolds</name>
<email>joseph-reynolds@charter.net</email>
</author>
<published>2020-01-14T22:34:09+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bmcweb/commit/?id=d887fff197b2fc3357bcbb1adb028521699a204a'/>
<id>urn:sha1:d887fff197b2fc3357bcbb1adb028521699a204a</id>
<content type='text'>
This enhances the return value from the pamAuthenticateUser function so
callers can articulate PAM error codes like PAM_NEW_AUTHTOK_REQD which
means the credentials are correct, but the password must be changed.

Tested: Yes, scenarios via both Redfish login and Basic Auth:
 - correct username and password, password is not expired
 - correct username and password, password is expired
 - correct username and incorrect password, password is not expired
 - correct username and incorrect password, password is expired
 - non-existent user (passsword is not relevant)

Signed-off-by: Joseph Reynolds &lt;joseph-reynolds@charter.net&gt;
Change-Id: I1114d6c9cc591fb0a1853cb4edea32ad22f7b015
</content>
</entry>
<entry>
<title>Add OemVirtualMedia schema</title>
<updated>2020-01-27T09:53:14+00:00</updated>
<author>
<name>Przemyslaw Czarnowski</name>
<email>przemyslaw.hawrylewicz.czarnowski@intel.com</email>
</author>
<published>2020-01-21T11:41:56+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bmcweb/commit/?id=d04ba325f3ef4e60eb4fd8e7477af78d1be0d79d'/>
<id>urn:sha1:d04ba325f3ef4e60eb4fd8e7477af78d1be0d79d</id>
<content type='text'>
OEM Schema for VirtualMedia added.
Also OpenBMC level has been added to OEM field in the code to
conform to schema standard.

Tested:
Manually using full stack of VirtualMedia.
* Inserting/ejecting media in both legacy and proxy mode
* Redfish Service Validator 1.3.2 ran

Change-Id: Iaa87dd767a4bf2062bd4e74dd790a2496aca96de
Signed-off-by: Przemyslaw Czarnowski &lt;przemyslaw.hawrylewicz.czarnowski@intel.com&gt;
</content>
</entry>
<entry>
<title>InsertMedia and EjectMedia actions added to VirtualMedia schema</title>
<updated>2020-01-27T09:53:00+00:00</updated>
<author>
<name>Przemyslaw Czarnowski</name>
<email>przemyslaw.hawrylewicz.czarnowski@intel.com</email>
</author>
<published>2019-09-02T15:32:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bmcweb/commit/?id=e13c27606f49f70910eca01f0ee496e7e9a6b330'/>
<id>urn:sha1:e13c27606f49f70910eca01f0ee496e7e9a6b330</id>
<content type='text'>
As continuation for VirtualMedia Redfish support, this patch adds
insertion and eject actions into existing VirtualMedia code base.

Testing:
* Manual tests together with nbd proxy and virtual media app
  - For requests: Postman and/or HTTPie, with logs enabled and Valgrind)
  - Manual result validation
* Tests run:
  - GET on collection with manual validation
  - PUT/POST/DELETE on collection
  - GET on item/nonexistent item
  - PUT/POST/DELETE on item
  - GET/PUT/DELETE on action
  - POST on action - EjectMedia/InsertMedia, legacy mode
  - POST on action - InsertMedia, proxy mode
  - POST on action - input validation (empty, invalid URL), legacy mode
* Redfish Service Validator tested, no new issues found.

Change-Id: Icccc433c1e84bc2ac37d9c295fe72749187fb735
Signed-off-by: Przemyslaw Czarnowski &lt;przemyslaw.hawrylewicz.czarnowski@intel.com&gt;
</content>
</entry>
<entry>
<title>Add VirtualMedia schema to Redfish</title>
<updated>2020-01-27T09:52:18+00:00</updated>
<author>
<name>Przemyslaw Czarnowski</name>
<email>przemyslaw.hawrylewicz.czarnowski@intel.com</email>
</author>
<published>2019-07-11T08:16:43+00:00</published>
<link rel='alternate' type='text/html' href='https://git.raptorcs.com/git/bmcweb/commit/?id=107077def176ad4a29557fae353de9bb00381ca9'/>
<id>urn:sha1:107077def176ad4a29557fae353de9bb00381ca9</id>
<content type='text'>
This change adds VirtualMedia scheme to Redfish.
Implementation is based on input from virtual-media module
and nbd proxy which is a bmcweb part. The code is used
only in case ndb-proxy is supported in bmcweb
(BMCWEB_ENABLE_VM_NBDPROXY compilation flag).

Tested:
* Manual tests together with nbd proxy and virtual media app
  - For requests: Postman and/or HTTPie, started with logs
    enabled and Valgrind
  - Manual result validation
* Tests ran:
  - GET on collection with manual validation
  - PUT/POST/DELETE on collection
  - GET on item/nonexistent item
  - PUT/POST/DELETE on item
* Redfish Service Validator tested, no new issues found.

Signed-off-by: Przemyslaw Czarnowski &lt;przemyslaw.hawrylewicz.czarnowski@intel.com&gt;
Change-Id: I5415dc0ffe52069fd35bc614b0378bbc4ad41ff6
</content>
</entry>
</feed>
