* Initial changes to pull down the serial from the validation reports page and transfer them to the certificates details page. This will then allow the certificate details page to reference the serial numbers that are in failure.
* This is an attempt to transfer data from page to page via the certificate manager.
* Previous attempt didn't work, the manager isn't saving the summary. Switching to augmenting the database by adding a new column for platform credentials.
* These changes add identifying color to the components that fail validation in the base certificate. This code however does change the database by adding a new column to track the fails and pass to the classes that display the information.
* Updated the jsp display of the highlighted component to red background with a white foreground. Updated the index of the string parse to not use magic numbers.
* The base certificate is getting a failure when the delta fixed the problem. The code is being modified to ignore the attribute validation of the base certificate and redo the trust chain check. The code now has a cleaner platform evaluation set up and store.
* This pull request contains 2 main changes, the first is transferring the status text from the attributes failure to the icon specifically for platform trust chain validation. Then this removes the third column on the validation page that singles out the icons for the attribute status. In addition, this status is also rolled up to the summary status icon and displays the text there as well for all that have failed. This last change meant a change to the sizes of the columns in the database.
The validation of a single base certificate with an error was not handled in the code base. Due to the changes with the introduction of delta certifications, the validation was modified and only handled changes presented by the deltas and ignored errors in the base certificate. This commit modifies the code that if there is just a single base certificate that is bad and error is thrown.
* This code change will add in the delta certficates to the platform validation check. The current base passes the policy check as long as the base is valid. The deltas are ignored. This is because the validation pulls in what is associated with a particular EK associated with the machine provisioning.
* This code adds functionality to check the delta certificates in a chain. The main operation validates that the delta belongs in that chain and then that the chain establishes correct component modification. No removes before an add, no add to a component that exists, no remove to a component that doesn't exist. The unit test was updated to not use any flat file certificate.
Closes#109
* Changes were made to the validation of a delta certificate based on newer information. There can be multiple bases and multiple leaves in a tree of associated certificates. However currently we don't have certificates to validate the entirety of the code to test.
* Updated the code to treat the platform attributes policy, if v2, against all in the chain rather than one at a time.
* Added methods and placeholders for checking the supply chain for base and delta credentials according to the new TCG spec
Checkstyle changes
Created a new SupplyChainValidation.ValidationType for delta credential attributes. The existing PLATFORM_CREDENTIAL
ValidationType will be used for both base and delta platform credentials from spec 1.1.
* Checkstyle error: trailing spaces
Added an additional null check for a platform supply validation. Added a mapping object for platform credential to the associated attributes during validations.
Added an additional null check for a platform supply validation. Added a mapping object for platform credential to the associated attributes during validations. Missed import statement.
