Open CIT 2.0.7 Test Cases

ZahediAquino edited this page Apr 20, 2016 · 1 revision

Administration

Functionality Description Expected Result
Tomcat Accessing Open CIT web page using https. "http://xxxx.xxxx.xxx.xxx:8443/mtwilson-portal/home.html Browser must show the login page for Open CIT login page.
Accessing Open CIT web page using http. "http://xxxx.xxxx.xxx.xxx:8443/mtwilson-portal/home.html" Open CIT must only be accessible using https. A page error is expected when accessing the page using http.
Portal Login Login in to the portal with valid/correct admin credentials "admin" account should be able to login and access the following pages, Trust Dashboard, Whitelist page, Host Management, Edit MLE, Edit OEM, Edit OS.
Logging in to the portal with incorrect admin credentials Error "unable to retrieve the user details for authentication. Please enter again".
Register link- allows the user to do self registration Register page (Create New account page) is displayed, with username, and password as well as password confirmation field.
Self registration page using valid characters on the username System must accept the username submitted.
Select the language selection for the specific user Should allow you to select the language or go with default.
Home Page > register Self registration page using invalid characters on the username System must not accept the username submitted. Special characters are not allowed for user registration.
Keying in the password with minimum 6 characters System must accept the password entered.
Keying in the password with less than the minimum 6 characters System must not accept the username submitted.
Keying in an Invalid password [less than 6 characters] System must not accept the invalid/illegal characters as a password.
Click "Create User" after entering valid username/password Forms submitted must be accepted by the system and informational message saying that the User has been registered successfully.
Click "Create User" after entering invalid username/password Forms submitted must not be accepted by the system and warning message is displayed on the screen.
Testing the "Clear" button Clear button should clear all the entries in the form.
"Create new Account" page This page should render and display correctly without any invalid characters displayed on the screen.
Page login link without entering any username/password System must display and inform user that the "values cannot be empty or blank".
Unmatched passwords used to register a user System must display warn and inform user that passwords do not match.
Logging in to the Open CIT front page using the newly created, unapproved account After entering the valid username and password, and clicking in the "Login" button, user must be able to login to the webpage, and system displays warning message informing the user does not have required roles for Attestation, Report and Security. He is also informed that roles and access must be approved by the administrator.
Accessing the page using unapproved account The system must provide limited access to the site pages and functions
Logging into Open CIT portal/web page using valid credentials The system must accept the login credentials and display the Trust Dashboard page and "Welcome Admin". Administrator is brought to the "Trust Dashboard" page with the "Loading" status.
User registration approval for Administrator-->Pending Request link/menu System should display the "Pending Registrations" page and show a table of pending user requests if it exists.
Listing users of the system This link should take you to the page that list the registered API client and displays the users registered to the system. The page should have a Heading called "View Registered API Client".
Delete user account link/menu from drop-down This link should take you to the page where the list of system users in a table format, and a delete button at the last column called "Options".
Extend user account link/menu from drop-down This link should take you to the page that informs the system administrator which API clients are to expire in the next 3 months.
User registration approval page-"Details" button/link A page must be displayed showing the account access rights and permissions in a form format, with check boxes and the expiry date.
Deleting a user account using the "Delete" button Pressing the delete button on the Delete Currently Registered API clients.
Re-registering using the deleted/removed user account Re-registering the same user account as the deleted account should be accepted byt the system and shows up on the Pending Registration page.
Session expiration set to 10 minutes System must inform and warn the user that his/her session expired. A confirmation to login again is displayed and the user is taken to a login page.
Rejecting request for registration The system must reject the user registration and should report it in the " View Registered API" page and that there are no more pending user requests on the "Pending Request" page.
Pending registration requests page A table must be displayed on the page showing the accounts that are pending for approval.
Deleting a user account The system should delete the user account that is stored on the system.
Users that has limited privileges The system must display a warning message "User does not have required roles - 'Security' to perform the task. Ensure that user has registered with these roles and the access has been approved by the administrator. [HTTP_UNAUTHORIZED] [401]". Right now user without have right permissions can delete and revoke certificate.
Re-registering using a deleted/purged user account Re-registration of the deleted user account must be accepted by the system.
User with no privilege try to delete HOST, MLE.
User with no privilege should not create tags, selections and delete or revoke certs.
View Certificates link This link should take you to the page entitled "Certificate Download" where download buttons (blue arrow pointing downward) and allow you to download the corresponding certs: Privacy CA, TLS, and SAML.
Administrator> View Certificates Download link/button for TLS Certificate Another page will display the entire certificate.
Download link/button for Privacy CA Cert Another page will display the entire certificate.
Download link/button for SAML Certificate System will open another window and ask where to save the certificate.

Whitelist

Functionality Description Expected Result
White list Link/Menu Whitelist menu/link Drop down list must appear with the options "Import Host", Edit MLE, Edit OS, Edit OEM
Whitelist>Import from host page Import from host menu/Link A page will be displayed with heading "Import whitelist from Host"; A drop-down list under the field "Host type" is shown. The drop down list are as follows: Citrix Xen, Xen, KVM, VMWare ESXi
Importing whitelist from a Host: Open source Xen The Xen as the "Host Type" must be selected from the drop down list, a check-box and a text box with options are displayed, and the required PCRs PCR-0 has a check mark. Check box for Hypervisor (VMM) is unchecked by default, with Required PCRs 17,18,19 checked, and 20 remains unchecked, and no option is selected inside the text box below the Hypervisor (VMM) check-box. The following forms must be displayed: Whitelist Host, and Port#, Register Host check-box (checked)
Importing whitelist from a Host: Citrix Xen server The Citrix Xen as the "Host Type" must be selected from the drop down list, a check-box and a text box with options are displayed, and the required PCRs PCR-0 has a check mark.Check box for Hypervisor (VMM) is unchecked by default, with Required PCRs 17,18,19 checked, and 20 remains unchecked, and no option is selected inside the text box below the Hypervisor (VMM) check-box. The following forms are added to the page: "Whitelist Host", Port #, Username and Password
Importing whitelist from a Host: Open source KVM server The Xen as the "Host Type" must be selected from the drop down list, a check-box and a text box with options are displayed, and the required PCRs PCR-0 has a check mark. Unchecked box for Hypervisor (VMM) is unchecked by default, with Required PCRs 17,18,19 checked, and 20 remains unchecked, and no option is selected inside the text box below the Hypervisor (VMM) check-box. The following forms must be displayed: Whitelist Host, and Port#
Importing whitelist from a Host: VMWare ESXi server. Repeat this step from ESXi 5.5 environment The VMWare ESXi option as the "Host Type" must be selected from the drop down list, a check-box and a text box with options are displayed, and the required PCRs PCR-0 has a check mark. Unchecked box for Hypervisor (VMM) is unchecked by default, with Required PCRs 17,18,19 checked, and 20 remains unchecked, and no option is selected inside the text box below the Hypervisor (VMM) check-box. The following forms are added to the page: "Whitelist Host", vCenter Server, Login ID and Password
Open Source Xen Importing whitelist using a Xen Host: Host Type: Xen server, BIOS--> OEM with required PCRs- 0 checked Confirm that the MLEs PCR-0 was submitted successfully and the Name, version, Attestation type PCR, MLE type BIOS appears in the Edit MLE page
Importing whitelist using a Xen Host: SELECTED OPTIONS : Host Type: Xen, BIOS-->Host PCR-0 checked Confirm that the MLEs for PCR-0, and an entry with Attestation type PCR, MLE Type: BIOS, IP_address_BIOS name appears in the MLE table, i.e. xxx.xxx.xxx.xxx_Intel_Corp
Importing whitelist using a Xen Host: Host Type: Xen server, Hypervisor (VMM) --> OEM with required PCRs-17,18 checked Confirm that an entry with Attestation type MLE type PCR+Module, IP_address_Platform_VMM appears in the MLE table i.e. Intel_Thurley_Xen
Importing whitelist using a Xen Host: Host Type: Xen, Hypervisor (VMM) --> Host; Required PCRs-17,18,19 checked Confirm that an entry with Attestation type: PCR+Module, MLE type: VMM: IP_address_BIOS name appears in the MLE table i.e: xxx.xxx.xxx.xxx_Xen
Importing whitelist using a Xen Host: Host Type: Xen server, Hypervisor (VMM) --> Global; Required PCRs-17,18,19 checked Confirm that an entry with Attestation type MLE type PCR+Module, Name (Xen), MLE Type VMM appears in the MLE table, i.e. Xen
Open source KVM Importing whitelist using a KVM Host: Host Type: KVM, BIOS--> OEM with required PCRs- 0 checked, Dell BIOS or IBM BIOS Confirm that the MLEs PCR-0 was submitted successfully and confirm if the Name, version, Attestation type PCR, MLE type BIOS appears in the Edit MLE page
Importing whitelist using a KVM Host: Host Type: KVM, BIOS--> OEM with required PCRs- 0 checked, Same BIOS: Intel_Corp Confirm that the MLEs PCR-0 was submitted successfully. Also confirm if the Name, version, Attestation type PCR, MLE type BIOS appears in the Edit MLE page and has overwritten the MLE values of the host with the same BIOS
Importing whitelist using a KVM Host: SECTED OPTIONS : Host Type: KVM server, BIOS-->Host PCR-0, 17 checked Confirm that the MLEs for PCR-0, and an entry with Attestation type: BIOS, MLE type BIOS name appears in the MLE table, i.e. xxx.xxx.xxx.xxx_Intel_Corp
Importing whitelist using a KVM Host:Host Type: KVM, Hypervisor (VMM) --> OEM; required PCRs-18,19 checked Confirm that you find an entry with Attestation type MLE type: PCR+Module name appears in the Edit MLE page i.e. Intel_Thurley_QEMU
Importing whitelist using a KVM Host: Host Type: KVM, Hypervisor (VMM) --> Host; required PCRs-18,19 checked Confirm that an entry with Attestation type MLE type: PCR+Module and IP_address_Platform_QEMU name appears in the Edit MLE page, i.e. xxx.xxx.xxx.xxx_QEMU
Importing whitelist using a KVM Host: Host Type: KVM, Hypervisor (VMM) --> Global;required PCRs-18,19 checked Confirm that an entry with Attestation type MLE type: PCR+Module and QEMU name appears in the Edit MLE page, i.e. QEMU
Citrix Xen Importing whitelist using a Citrix XEN Server Host: Host Type:Citrix Xen server, BIOS--> OEM with required PCRs- 0 checked The system must confirm that the MLEs PCR-0 was submitted successfully and confirm if the Name, version, Attestation type PCR, MLE type BIOS appears in the MLE table
Importing whitelist using a Citrix XEN Server Host: SELECTED OPTIONS : Host Type: Citrix Xen, BIOS-->Host PCR-0, 17 checked The system must confirm that the MLEs PCR-0 was submitted successfully, and an entry with Attestation type: BIOS, IP_address_BIOS name appears in the MLE table
Importing whitelist using a Citrix XEN Server Host: Host Type: Citrix Xen server, Hypervisor (VMM) --> OEM with required PCRs-18,19 checked The system must confirm that an entry with Attestation type PCR MLE type VMM (i.e. Dell_xen) appears in the MLE table
Importing whitelist using a Citrix XEN Server Host: Host Type: Citrix Xen server, Hypervisor (VMM) --> Host with required PCRs-18,19 checked The system will confirm that an entry with Attestation type PCR, MLE type: VMM name appears in the MLE table i.e. xxx.xxx.xxx.xxx_xen
Importing whitelist using a Citrix XEN Server Host: Host Type: Citrix Xen server, Hypervisor (VMM) --> Global with required PCRs-18,19 checked, with wrong credentials, The system will confirm that an entry with Attestation type MLE type: VMM, name appears in the MLE table i.e. xen
VMWare ESXi Repeat the test for ESXi 5.5 env Importing whitelist using a ESXi Server Host: Host Type:ESXi server, BIOS--> OEM with required PCRs- 0,17 checked The system will confirm if it accepted your entries with a message saying Whitelist configuration updated successfully. An entry in the Edit MLE table, MLE type BIOS, Attestation type:PCR, should appear with the Name "Intel_Corporation"
Importing whitelist using a ESXi Server Host: Host Type:ESXi server, BIOS--> Host with required PCRs- 0, 17checked The system will confirm if it accepted your entries with a message saying WhiteList configuration updated successfully. An entry in the Edit MLE table should appear with the Name "IP_address_BIOS_name", i.e. xxx.xxx.xxx.xxx_Intel_Corporation
Importing whitelist using a VMWare ESXi Server Host: Host Type: ESXi server, Hypervisor (VMM) --> OEM with required PCRs-17,18,19,20checked The system will confirm if it accepted your entries with a message that appears and saying Whitelist configuration updated successfully. An entry in the Edit MLE table should appear with the Name "IP_address_VMWare ESXi" , i.e. xxx.xxx.xxx.xxx_Vmware_ESXi
Importing whitelist using a VMWare ESXi Server Host with a DIFFERENT platform (i.e. ROMLEY or THURLEY) Host Type: ESXi server, Hypervisor (VMM) --> OEM with required PCRs-18,19,20 checked The system will confirm if it accepted your entries with a message saying whitelist configuration updated successfully. An entry in the Edit MLE table, MLE type BIOS, Attestation type:PCR, should appear with the Name i.e."Intel_Romley_VMWare_ESXi"
Importing whitelist using a VMWare ESXi Server Host: Host Type: ESXi server, Hypervisor (VMM) --> Host, required PCRs-18,19,20 checked The system will confirm if it accepted your entries with a message saying WhiteList configuration updated successfully. An entry in the Edit MLE table should appear with the MLE Type VMM, Attestation type: PCR+Module, Name "IPaddress_Vmware ESxi", i.e. xxx.xxx.xxx.xxx_VMware_ESXi
Importing whitelist using a VMWare ESXi Server Host: Host Type: ESXi server, Hypervisor (VMM) --> Global, required PCRs-18,19 checked The system will confirm if it accepted your entries with a message saying WhiteList configuration updated successfully. An entry in the Edit MLE table should appear with the MLE Type VMM, Attestation type: PCR+Module, Name "Vmware ESxi", i.e.VMware_ESXi
Whitelisting and Registering Host (negative test cases) Whitelisting using a Citrix XEN Server Host: Host Type: Citrix Xen server, Hypervisor (VMM) --> BIOS and VMM with invalid/wrong credentials. The system will display an error that "MW Communication error"
Whitelisting using a VMWare ESXi: Host Type: VMWare ESXi, Hypervisor (VMM) --> BIOS and VMM with required PCRs-17,18,19 checked, with invalid/wrong credentials. The system will display an error that "MW Communication error"
Whitelisting using a KVM Server Host: Host Type: Citrix Xen server, Hypervisor (VMM) --> BIOS and VMM with required PCRs-17,18,19 checked, with checked Register Host. A message is displayed "Whitelist configuration updated successfully and the host has been registered". Also, the host is then added to the Trust Dashboard and Host management page
Importing whitelist using a Vmware ESXi Host: Host Type: Citrix Xen server, Hypervisor (VMM) --> BIOS and VMM with required PCRs-17,18,19 checked, with checked Register Host. A message is displayed "Whitelist configuration updated successfully and the host has been registered". Also, the host is then added to the Trust Dashboard and Host management page
Whitelisting a host with at least than 32 characters in the Whitelist Host field: Type in the Whitelist host example "intel-epsd-thurl-173.mtwilson.intel.com" The system should accept more than 20 valid characters for hostname and whitelisting is successful and confirmed if the
Support for more than 32 characters on the IP address Whitelisting a host with at least 1 junk {^%$&^%*&^]characters in the Whitelist Host field: The system must display an error
Whitelisting a host with at least 1 junk {^%$&^%*&^]characters in the Whitelist Host field: The system must display an error
whitelisting host with less than 2 char in the hostname Field The system must display an error
White List> Edit MLE Edit MLE Link You will be taken to the Edit Measured Launch Environment Configuration page and displays a table containing hosts that have been white listed
"Edit Link" under Options, MLE type BIOS (applies to Vmware, Open source and Citrix Xen) System will display another window with greyed out forms and only the description is allowed for editing, and under Manifest List - 0 Check-box with the MLE value appears on the form
Edit Link under the Options column for each case: Attestation type PCR, MLE Type VMM (VMWare only) System will display another window with greyed out forms and only the description is allowed for editing, and under Manifest List - 17,18,19,20 Check-box with the MLE value appears on the form, Buttons "Show Manifest" "Update MLE" and "Clear" button is shown on the page
Edit Link under the Options column for each case: Attestation type PCR, MLE Type VMM (VMWare only) --> Show Manifest button Another window will appear and the PCRs 17, 18, 19, and 20 values are displayed in a table format
Edit Link under the Options column for each case: Attestation type PCR, MLE Type VMM (VMWare only) --> Update MLE button Another confirmation window will pop up, hitting OK will proceed with the action. Selecting "Cancel" will take you to the same window (Edit MLE for the selected host)
Edit Link under the Options column for each case: Attestation type PCR, MLE Type VMM (VMWare only) --> Clear button The button should only clear out the "Description" field
Edit Link under the Options column for each case: Attestation type PCR, MLE Type VMM (Citrix Xen Server) System will display another window with greyed out forms and only the description and Manifest list 17 and 18 are allowed for editing. The "Choose file", "Upload", "Update MLE" and "Clear" are displayed on the page.
Edit Link under the Options column for each case: Attestation type PCR, MLE Type VMM (Citrix Xen Server)-"Choose File" with the correct file format The system will open another window to let you locate the file of the PCR. Once located and chosen the file, the file name should appear next to the "Choose File" button
Negative test case: Edit Link under the Options column for each case: Attestation type PCR, MLE Type VMM (Citrix Xen Server)-"Choose File" with the incorrect file format The system must be able to detect that the file has an incorrect file format
Edit Link under the Options column for each case: Attestation type PCR+module, MLE Type VMM (Open Source host) System will display another window with greyed out forms and only the description is allowed for editing, and under Manifest List - 17,18 Check-box are greyed out and PCR 19, 20 unchecked, and Show Manifest button, Update MLE button, Clear is displayed in the page
Show Manifest Button/Link (Open Source host) A new window will be displayed when this button is invoked. For open source host, a table of PCR 17,18 has entries, PCR 19 is blank, and initrd component has a Digest Value
White List> Edit OS "Edit OS" menu link User is taken to another page displaying a table with heading "OS/Hypervisor Combination
Deleting an OS that is associated with a Registered Host Another window will confirm your action to delete the selected OS and if you confirm, a message appears on the portal in red text informing the user that OS cannot be deleted. * OS "VMware_ESXi" is not deleted, OS 'VMware_ESXi' of version '5.1.0' cannot be deleted as it is associated with 1 MLEs. [WS_OS_ASSOCIATION_EXISTS] [2006]
"Cancel" link Action is cancelled and Edit and Delete links now appears
White List> Edit OEM Edit OEM menu/link The OEM table is displayed on the page
Editing "OEM" page, "Update" link "Edit" link should allow user to only edit the "Description" page, and "Update" link should accept /allow user to update only the Description field
Adding OEM Link Clicking this will take you to another page with the two forms, Name and Description.
Adding OEM Link -> add values to Name and Description respectively, then click on "Add" button. System must add the values in the OEM table, confirm this by going to Edit OEM top menu. The values you entered must also show here.
Clear button of the Add OEM page System must clear the values in the forms Name and Description when you press on this button
Deleting an "OEM" value from the "OEM" table (Unassociated OEM) The system confirms the action by displaying an "OK" or "Cancel" buttons on a small window". * OEM "HP" has been successfully deleted message is displayed
Deleting an "OEM" value from the "OEM" table (Associated "OEM" value) System should not allow you to delete the "OEM" that's associated with a host. * OEM "Intel Corp." is not deleted, OEM 'Intel Corp.' cannot be deleted as it is associated with 1 MLEs. [WS_OEM_ASSOCIATION_EXISTS] [2003]
White List> Logout Logging out the system from the White List page using the "Logout" link The link should redirect the user to the login page.

TrustAgent

Functionality Description Expected Result
Trust DashBoard Trust Status Dashboard table shows the list of trusted servers. Display "Host Name", "Location", "BIOS Trust Status", "VMM Trust Status", "Overall Trust Status", "Updated On', "Trust Status", "Trust Details" Trust Status Dashboard table shows the list of trusted servers. Display "Host Name", "Location", "BIOS Trust Status", "VMM Trust Status", "Overall Trust Status", "Updated On', "Trust Status", "Trust Details"
Table column: "BIOS Trust Status" A green "Check" icon is displayed if host BIOS matches the GKV from WLM Portal DB. A blue ? "Question Mark" icon is displayed if the BIOS Trust Status cannot be identified or doesn't match the GKV from the WLM portal DB
Table column: "VMM Trust Status" A red X "X" icon is displayed if the BIOS MLE doesn't match the GKV from the WLM portal DB. A green "Check" icon displayed if host VMM GKV matches the GKV from WLM Portal DB. A blue ? "Question" icon is displayed if the VMM GKV not found or doesn't match the GKV from the WLM portal DB
Table column: "Overall Trust Status" A red X "X" icon is displayed if the VMM MLE doesn't match the GKV from the WLM portal DB. A green "Check" icon if host VMM GKV matches the GKV from WLM Portal DB. A blue ? "Question" is displayed icon if the VMM GKV not found or doesn't match the GKV from the WLM portal DB.
Table column: "Updated On" This column should match the date the last time the "Refresh" button has been pressed or Trust Dashboard was refreshed
Table column: "Trust Status:" Clicking the "REFRESH" button. Successful polling Click on "Refresh" button, it should display the last date and time the host has been polled and compared its MLE with the GKV in the WLM DB. The date and time is the system time of the system that opened the page.
Table column: "Trust Status:" Clicking the "REFRESH" button. Unsuccessful polling An error message should appear on the Trust Report column "SYSTEM_ERROR. System error: Cannot retrieve PCR Manifest from xxx.xxx.xxx.xxx host
Table column: "Trust Assertion": Clicking on the "Gold Shield" icon, of a Trusted Host A new window pops up that shows the "Trust Details"-Trust Verification details displaying the MLEs of the host in XML
Table column: "Trust Assertion" : Clicking on the "Gold Shield" icon of an untrusted or a host with an Unknown Trust Assertation A new window pops-up showing Host Trust status and shows the message "Error While Getting SAML. SYSTEM_ERROR. System error: Cannot retrieve PCR Manifest from xxx.xxx.xxx.xxx"
Table column: "Trust Assertion" : Clicking on the "Notebook w/ Key" icon of a Trusted Host A new window will pop-up, called "Trust Report" and displaying a table of the PCR manifest and Whitelist Value
Table column: "Trust Assertion" : Clicking on the "Notebook w/ Key" icon of unTrusted Host A new window will pop-up, called "Trust Report" and displaying a table of the PCR manifest and Whitelist Value
Table column: "Trust Assertion" : Clicking on the "Notebook w/ Key" icon of a Host with "XX" red Shield icon in the Overall Trust Status and VMM Trust Status icon A new window will pop-up, called "Trust Report" and displaying a table of the PCR manifest and Whitelist Value and the PCR value that doesn't match the whitelist must be marked in "Red"
Table column: "Trust Status" column for a Trusted host Blank or Null
Table column: "Trust Report" column for a Trusted host, after pressing the Refresh button The message "Host Trust Status updated successfully" appears in this column
Table column: "Trust Report" column for a host with an unknown trust status after pressing the "Refresh" button A message "System Error: Cannot retrieve PCR Manifest from xxx.xxx.xxx.xxx" is displayed in the Trust Report column
Trust Report Page-->Expanding the PCR Name + sign (Vmware ESXi host) Only the PCR 19 should display several component name and will be displayed as a sub table under the component name, displaying the value, and whitelist value accordingly. The rest of the PCRs 0, 17, and 18 will display a message "This PCR does not have any module logs"
Trust Report Page-->Expanding the PCR Name + sign (Open source host) Only the PCR 19 should display another sub table containing initrd in the component name, displaying the value, and whitelist value. The rest of the PCRs 0, 17, and 18 will display a message "This PCR does not have any module logs"
Table column: Status Host Trust status updated information. After added a host and will display "blank" tab/column
Bulk Refresh & Reports Function: "Bulk Trust Refresh" Link/menu item Clicking on the button will redirect to the Bulk Trust Status Update page
"Group/Bulk Trust Status Update" page All check-boxes must allow to be marked and unchecked
"Group/Bulk Trust Status Update" page and "Update Trust Status" button with all the "host " check-boxes checked, and pressing the "Update Trust Status" button A spinning wheel will be displayed while the page waits for the system to finish polling the hosts and the Trust Dashboard is displayed.
Function: "Report" menu item A report displaying in the web page with the details of "Host Name", "BIOS Name", "BIOS Build", "VMM Name", "VMM Build"
Action/Function: "Get Report" button. User is taken to another page with tables that has information of all the Hosts added to the System, The table heading are as follows: "host name" "MLE Details", "Created", "Trust Status" and "Trust Verified"
Pressing refresh button on the Trust Dashboard, one at a time in succession The table column: Status will display a "Status bar" then a message "Host Trust Status updated successfully" will appear

HostManagement

Functionality Description Expected Result
Host Management Mouse over "menu" of Host Management Mouse over should display the drop down list for Host Management
FUNCTION: "Import" menu item Clicking the "Import" menu from the drop down list should display the "Host Registration" page with the "Host provided by" default selected "Flat file" from drop down menu.
Selecting "Flat file" as the option to Register Host, "Choose File" and "Retrieve Host" button are displayed The "Register Host" page displays without any issues
FLAT FILE UPLOAD ADDING Citrix Xen Hosts USING FLAT FILE option: Selecting "Flat file" as the option to Register Host, "Choose File" (and "Retrieve Host" button are displayed, and uploading using the Flat File function, with the correct "Flat File" format A table of all the hosts in that Flat file is displayed. If the host has not been registered with the system, the "Register" check-boxes are by default checked, and if a system is registered, the check-box is greyed out.
ADDING VMWARE ESXi Hosts USING FLAT FILE option: Selecting "Flat file" as the option to Register Host, "Choose File" and "Retrieve Host" button are displayed, and uploading using the Flat File function, with an incorrect flat file format/syntax. Ensure that the OEM are selected on the BIOS and VMM configuration "A table of all the hosts in that Flat file is displayed. If the host has not been registered with the system, the ""Register"" check-boxes are by default checked, and if a system is registered, the check-box is greyed out. The page should refresh, as soon as the refresh is done, the Trust Status for BIOS, VMM and overall trust status column should have the green check icon, and the status should say, Host Trust Status updated successfully."
ADDING VMWARE ESXi Hosts USING FLAT FILE option with a NON TXT host: Selecting "Flat file" as the option to Register Host, "Choose File" and "Retrieve Host" button are displayed, and uploading using the Flat File function, with one non-txt host (accidentally added in the file by an administrator) A message next to the "Retrieve Hosts" will appear saying "File is uploaded successfully" and that the host that is non txt will have "VMM MLE xxx is not configured in the list is properly configured"
Selecting "Flat file" as the option to Register Host, "Choose File" and "Retrieve Host" button are displayed, and uploading using the Flat File function, with an incorrect "Flat File" format The message "File is not processed properly" Please check file format. Use Help Button to know more"
The HELP file (?) Question mark icon The "Help" should provide an example of the format or correct syntax that the system can parse and process.
ADDING Citrix Xen Hosts USING FLAT FILE option: Selecting "Flat file" as the option to Register Host, "Choose File" (and "Retrieve Host" button are displayed, and uploading using the Flat File function, with the correct "Flat File" format. A table of all the hosts in that Flat file is displayed. If the host has not been registered with the system, the "Register" check-boxes are by default checked, and if a system is registered, the check-box is greyed out.
ADDING VMWARE ESXi Hosts USING FLAT FILE option: Selecting "Flat file" as the option to Register Host, "Choose File" and "Retrieve Host" button are displayed, and uploading using the Flat File function, with an incorrect flat file format/syntax. Ensure that the OEM are selected on the BIOS and VMM configuration "A table of all the hosts in that Flat file is displayed. If the host has not been registered with the system, the ""Register"" check-boxes are by default checked, and if a system is registered, the check-box is greyed out. The page should refresh, as soon as the refresh is done, the Trust Status for BIOS, VMM and overall trust status column should have the green check icon, and the status should say, Host Trust Status updated successfully."
ADDING VMWARE ESXi Hosts USING FLAT FILE option with a NON TXT host: Selecting "Flat file" as the option to Register Host, "Choose File" and "Retrieve Host" button are displayed, and uploading using the Flat File function, with one non-txt host (accidentally added in the file by an administrator) A message next to the "Retrieve Hosts" will appear saying "File is uploaded successfully" and that the host that is non txt will have "VMM MLE xxx is not configured in the list is properly configured"
Hosts that has not been added to the white list (CITRIX,VMWare, Open Source host) ADDING Citrix Xen Hosts USING FLAT FILE option: Selecting "Flat file" as the option to Register Host, "Choose File" (and "Retrieve Host" button are displayed, and uploading using the Flat File function, with the correct "Flat File" format A table of all the hosts in that Flat file is displayed. If the host has not been registered with the system, the "Register" check-boxes are by default checked, and if a system is registered, the check-box is greyed out.
ADDING VMWARE ESXi Hosts USING FLAT FILE option: Selecting "Flat file" as the option to Register Host, "Choose File" and "Retrieve Host" button are displayed, and uploading using the Flat File function, with an incorrect flat file format/syntax. Ensure that the OEM are selected on the BIOS and VMM configuration "A table of all the hosts in that Flat file is displayed. If the host has not been registered with the system, the ""Register"" check-boxes are by default checked, and if a system is registered, the check-box is greyed out. The page should refresh, as soon as the refresh is done, the Trust Status for BIOS, VMM and overall trust status column should have the green check icon, and the status should say, Host Trust Status updated successfully."
ADDING VMWARE ESXi Hosts USING FLAT FILE option with a NON TXT host: Selecting "Flat file" as the option to Register Host, "Choose File" and "Retrieve Host" button are displayed, and uploading using the Flat File function, with one non-txt host (accidentally added in the file by an administrator) A message next to the "Retrieve Hosts" will appear saying "File is uploaded successfully" and that the host that is non txt will have "VMM MLE xxx is not configured in the list is properly configured"
ADDING Open source Hosts USING FLAT FILE option: Selecting "Flat file" as the option to Register Host, "Choose File" and "Retrieve Host" button are displayed, and uploading using the Flat File function, using the correct flat file format/syntax. Ensure that the OEM are selected on the BIOS and VMM configuration. Choose the type of host (BIOS or VMM MLE) that has not been added to the White list. A message next to the "Retrieve Hosts" will appear saying "File is uploaded successfully" and a message in the Status column will appear saying "BIOS MLE is not configured in the system" or VMM MLE xxxx.xxx" is not configured in the list is properly configured"
ADDING VMWare ESXi Hosts USING FLAT FILE option: Selecting "Flat file" as the option to Register Host, "Choose File" and "Retrieve Host" button are displayed, and uploading using the Flat File function, using the correct flat file format/syntax. Ensure that the OEM are selected on the BIOS and VMM configuration. Choose the type of host (BIOS or VMM MLE) that has not been added to the White list. A message next to the "Retrieve Hosts" will appear saying "File is uploaded successfully" and a message in the Status column will appear saying "BIOS MLE is not configured in the system" or VMM MLE xxxx.xxx" is not configured in the list is properly configured"
ADDING Citrix Xen Hosts USING FLAT FILE option: Selecting "Flat file" as the option to Register Host, "Choose File" and "Retrieve Host" button are displayed, and uploading using the Flat File function, using the correct flat file format/syntax. Ensure that the OEM are selected on the BIOS and VMM configuration. Choose the type of host (BIOS or VMM MLE) that has not been added to the White list. A message next to the "Retrieve Hosts" will appear saying "File is uploaded successfully" and a message in the Status column will appear saying "BIOS MLE is not configured in the system" or VMM MLE xxxx.xxx" is not configured in the list is properly configured".
VMWARE AUTOMATION REGISTRATION Choosing "VMWare Cluster" from the "Host Provided by" drop down list The fields required to add VMWare ESXi host show up in different browsers (i.e. IE, Mozilla, and Chrome)
Add Host Menu item Users are taken to the "Host Registration" page
Selecting VMWare Cluster from the drop down list, and Adding ESXi host by filling out the fields "VMWare Cluster", Vcenter Server, Login ID, and password with valid values System informs user that all fields are required fields and displays an * at the end of the field/form
Importing/Registering ESXi host via the Import Host Page and registering hosts to Open CIT server If valid values are correctly entered here, the button "Retrieve Hosts" must be pressed trigerring the system to retrieve the list of hosts from Vcenter. A table containing the ESXi hosts found on the Vcenter's database and cluster is displayed.
Importing/Registering ESXi host via the Import Host Page and registering host to Open CIT server with Invalid "VMWare Cluster" name Informational/warning message must be displayed informing and instructing user about the invalid characters: System error message appears "Cluster configuration not found in the Vcenter database"
Importing/Registering ESXi host via the Import Host Page and registering the host to Open CIT server with Invalid "Vcenter Server" Informational/warning message must be displayed informing and instructing user about the invalid characters: System error message appears "Cluster configuration not found in the Vcenter database"
Importing/Registering ESXi host via the Import Host Page and registering the host to Open CIT server with Invalid Login credentials Informational/warning message must be displayed informing and instructing user about the invalid characters: System error message appears "Cannot complete login due to an incorrect user name and password"
Adding a host using valid characters for a hostname or IP address or FQDN on the hostname form before pressing the add button System must accept only valid FQDN, IPv4 dotted notation. System does detect the correct input for this form. It only detects the input after submitting the form or pressing the "Add Host" button
Adding Invalid IP address or FQDN on the "Hostname" form before pressing the add button System must not accept invalid IP address or FQDN. System must detect that an Invalid input and must warn the user i.e. IP address or FQDN prior must correct it before submitting/pressing "Add Host" button.
HOST MANAGEMENT-REGISTER Adding a host by leaving the form "Hostname" blank or empty before pressing the add button System must inform user that form is empty or blank. System must detect that the form is empty must warn the user i.e. to correct it before submitting/pressing "Add Host" button.
Adding Invalid characters for the IP address or FQDN on the "Hostname" form before pressing the add button Input should not be accepted as a valid entry to the hostname and a warning must be displayed to the user "Special Characters are not allowed." A warning message is displayed informing the user to correct the issue
Keying in symbols only Input like xxx.xxx.xxx.1111 is not accepted as a valid IP address. invalid IP is not accepted by the system
Typing in the valid IP format in decimal notation, separated with 3 dots No error message is displayed
Typing in an invalid IP format (xxx.xxx.xxx) System will accept the values between 0-255 that is in the IPv4 dotted notation
Putting in any character or symbol Blank and null will not be accepted. The message "Value specified is invalid" is displayed to the screen
Function: Drop down list of OEM vendor A list of OEM vendors are displayed when the drop down list is opened. DELL XEN should be diplayed as DELL Citrix Xen Server
Function: Drop down list of BIOS vendor A list of BIOS vendors in the system are displayed when the drop down list is opened.
Function: List of OS-VMM info, selecting RHEL 6.2-KVM:0.12.1 Highlights RHEL 6.2-KVM:0.12.1
Host Management-Registering Host OS-VMM info Function: List of OS-VMM info, selecting RHEL 6.2-KVM:0.12.1 Highlights RHEL 6.2-KVM:0.12.1
Function: List of OS-VMM info, selecting Ubuntu 12.04-KVM:0.14.1 Highlights Ubuntu 11.10-KVM:0.14.1
Function: List of OS-VMM info, selecting Ubuntu 12.04-Xen 4.1.1 Highlights Ubuntu 11.10-XEN:4.1.1
Host Management Registering Host, VMWare Selecting VMWare_5.1.0 Vmware_ESXi 5.1.0-799733
Host Management --> Add host --> Registering an ESXi host if any of the required fields are not filled out and syntax requirements are not satisfied, error message is displayed
Cancel button Will revert back to the "New Host Configuration" page, with empty forms
Clear button System will clear out the forms
ESX host with valid IP address, host port, host description, OEM, valid BIOS info, valid VMM info, Vcenter details (vCenter IP, Login ID, Password), Email Address The system will display the hosts present in the Vcenter's database and you have the option to choose which ESXi hosts are to be added to the system.
ESX host with the same valid IP address and Valid hostname, valid host port, valid host description, OEM, valid BIOS info, valid VMM info, invalid Vcenter details (vCenter IP, Login ID, Password), Email Address The message "System error: Cannot create Host Agent for xxx.xxx.xxx.xxx: java.io.IOException: Cannot get vmware client for host: xxx.xxx.xxx.xxx: Host 'xxx.xxx.xxx.xxx' is not found in VCenter. [SYSTEM_ERROR] [1]"is displayed. Error can be seen in log file now
Host Management --> Add host --> New host registration. Registering an ESX host with valid IP address, host port, host description, OEM, incorrect BIOS info, incorrect VMM info, Valid Vcenter details (vCenter IP, Login ID, Password), Email Address The system will be registered and will appear in the system as untrusted for the BIOS MLE, but will have a trust status for VMM MLE
Host Management --> Add host --> New host registration. ESX host with the same valid IP address and invalid hostname, valid host port, valid host description, OEM, valid BIOS info, valid VMM info, Vcenter details (vCenter IP, Login ID, Password), Email Address The message "System error: Cannot create Host Agent for ESXi 1: java.io.IOException: Cannot get vmware client for host: ESXi 1: Host 'ESXi 1' is not found in VCenter. [SYSTEM_ERROR] [1]" is displayed.Error can be seen in log file now
"Edit Host" menu item and "Edit Host" page The user is taken to another page that contains info of all hosts currently in your MW server. The column labeled Vcenter Details should not be displayed
Updating Host information for ESXi hosts --> Host Management ->Update Host button Should update the information details of an existing host. Only the Description and email address fields are allowed for updating
Updating Host information for ESXi hosts and updating the information with incorrect details like the Host IP address, Vcenter IP address, login ID or Password An error message is generated "System error: Cannot create Host Agent for xxx.xxx.xxx.xxx: java.io.IOException: Cannot get vmware client for host: xxx.xxx.xxx.xxx: com.intel.mtwilson.agent.vmware.VMwareConnectionException: Cannot connect to vcenter: xxx.xxx.xxx.xxx [SYSTEM_ERROR] [1]". Error can be seen in log file now
Updating Host information for ESXi hosts and updating the information with correct details like the Host IP address, Vcenter IP address, invalid/incorrect login ID or Password An error message is generated "System error: Cannot create Host Agent for xxx.xxx.xxx.xxx: java.io.IOException: Cannot get vmware client for host: xxx.xxx.xxx.xxx: com.intel.mtwilson.agent.vmware.VMwareConnectionException: Cannot connect to vcenter: xxx.xxx.xxx.xxx [SYSTEM_ERROR] [1]"
Changing/updating Host information: OS-VMM info System will display the VMM details with the trusted/whitelisted host on the page
Cancel button on the "Update host configuration" page Pressing this button, the System should take you to the "Edit Hosts" page
"Delete" link in the "Edit Hosts" page A confirmation window must be displayed by the system before proceeding with the action.
Clear button on the "Update Host configuration" page This action/function should only clear out the Host IP address and Host port form.
Confirming Host deletion function This action should delete the host selected and a message confirming the action is displayed "Host has been successfully deleted"
Deleting "Host" Click "OK" to execute the process of deleting a host from the dashboard
Cancelling the "Delete" action The system will not delete the host from the table or list
Host attestation using FQDN (fully qualified domain name) with more than 32 characters in the Host name form: "tested with opensource host" The system must accept this and add this host to the list of trusted host in the trust dashboard
Enter the invalid FQDN with some junk characters

TrustDashboard

Functionality Description Expected Result
Trust Dashboard Trust Status Dashboard table shows the list of trusted servers. Display "Host Name", "Location", "BIOS Trust Status", "VMM Trust Status", "Overall Trust Status", "Updated On', "Trust Status", "Trust Details" Trust Status Dashboard table shows the list of trusted servers. Display "Host Name", "Location", "BIOS Trust Status", "VMM Trust Status", "Overall Trust Status", "Updated On', "Trust Status", "Trust Details"
Table column: "BIOS Trust Status" A green "Check" icon is displayed if host BIOS matches the GKV from WLM Portal DB. A blue ? "Question Mark" icon is displayed if the BIOS Trust Status cannot be identified or doesn't match the GKV from the WLM portal DB
Table column: "VMM Trust Status" A red X "X" icon is displayed if the BIOS MLE doesn't match the GKV from the WLM portal DB. A green "Check" icon displayed if host VMM GKV matches the GKV from WLM Portal DB. A blue ? "Question" icon is displayed if the VMM GKV not found or doesn't match the GKV from the WLM portal DB.
Table column: "Overall Trust Status" A red X "X" icon is displayed if the VMM MLE doesn't match the GKV from the WLM portal DB. A green "Check" icon if host VMM GKV matches the GKV from WLM Portal DB. A blue ? "Question" is displayed icon if the VMM GKV not found or doesn't match the GKV from the WLM portal DB
Table column: "Updated On" This column should match the date the last time the "Refresh" button has been pressed or Trust Dashboard was refreshed
Table column: "Trust Status:" Clicking the "REFRESH" button. Successful polling Click on "Refresh" button, it should display the last date and time the host has been polled and compared its MLE with the GKV in the WLM DB. The date and time is the system time of the system that opened the page.
Table column: "Trust Status:" Clicking the "REFRESH" button. Unsuccessful polling An error message should appear on the Trust Report column "SYSTEM_ERROR. System error: Cannot retrieve PCR Manifest from xxx.xxx.xxx.xxx host
Table column: "Trust Assertion" : Clicking on the "Gold Shield" icon, of a Trusted Host A new window pops up that shows the "Trust Details" - Trust Verification details displaying the MLEs of the host in XML
Table column: "Trust Assertion": Clicking on the "Gold Shield" icon of an untrusted or a host with an Unknown Trust Assertation A new window pops-up showing Host Trust status and shows the message "Error While Getting SAML. SYSTEM_ERROR. System error: Cannot retrieve PCR Manifest from xxx.xxx.xxx.xxx"
Table column: "Trust Assertion": Clicking on the "Notebook w/ Key" icon of a Trusted Host A new window will pop-up, called "Trust Report" and displaying a table of the PCR manifest and Whitelist Value
Table column: "Trust Assertion": Clicking on the "Notebook w/ Key" icon of unTrusted Host A new window will pop-up, called "Trust Report" and displaying a table of the PCR manifest and Whitelist Value
Table column: "Trust Assertion": Clicking on the "Notebook w/ Key" icon of a Host with "XX" red Shield icon in the Overall Trust Status and VMM Trust Status icon A new window will pop-up, called "Trust Report" and displaying a table of the PCR manifest and Whitelist Value and the PCR value that doesn't match the whitelist must be marked in "Red"
Table column: "Trust Status" column for a Trusted host Blank or Null
Table column: "Trust Report" column for a Trusted host, after pressing the Refresh button The message "Host Trust Status updated successfully" appears in this column
Table column: "Trust Report" column for a host with an unknown trust status after pressing the "Refresh" button A message "System Error: Cannot retrieve PCR Manifest from xxx.xxx.xxx.xxx" is displayed in the Trust Report column
Trust Report Page-->Expanding the PCR Name + sign (Vmware ESXi host) Only the PCR 19 should display several component name and will be displayed as a sub table under the component name, displaying the value, and whitelist value accordingly. The rest of the PCRs 0, 17, and 18 will display a message "This PCR does not have any module logs"
Trust Report Page-->Expanding the PCR Name + sign (Open source host) Only the PCR 19 should display another sub table containing initrd in the component name, displaying the value, and whitelist value. The rest of the PCRs 0, 17, and 18 will display a message "This PCR does not have any module logs"
Table column: Status Host Trust status updated information
after added a host and will display "blank" tab/column
Bulk Refresh & Reports Function: "Bulk Trust Refresh" Link/menu item Clicking on the button will redirect to the Bulk Trust Status Update page
"Group/Bulk Trust Status Update" page All check-boxes must allow to be marked and unchecked
"Group/Bulk Trust Status Update" page and "Update Trust Status" button with all the "host " check-boxes checked, and pressing the "Update Trust Status" button A spinning wheel will be displayed while the page waits for the system to finish polling the hosts and the Trust Dashboard is displayed
Function: "Report" menu item A report displaying in the webpage with the details of "Host Name", "BIOS Name", "BIOS Build", "VMM Name", "VMM Build"
Action/Function: "Get Report" button User is taken to another page with tables that has information of all the Hosts added to the System, The table heading are as follows: "host name" "MLE Details", "Created", "Trust Status" and "Trust Verified"
Pressing refresh button on the Trust Dashboard, one at a time in succession The table column: Status will display a "Status bar" then a message "Host Trust Status updated successfully" will appear

Internationalization

Functionality Description Expected Result
Internationalization Setup STEP1: Path to installation files for UI: Tomcat: /usr/share/apache-tomcat-6.0.29/webapps/mtwilson-portal/locales/
STEP2:Make changes in the properties file for the language files /etc/intel/cloudsecurity/mtwilson.properties
i.e.: mtwilson.locales=en,en-US,es,es-MX
After Step 2, don’t restart the mtwilson services and open the mail login portal and click on Register User --> Click on Drop Down List Supported language(s) should appear under the language drop-down list. As per Developer Mtwilson restart command is not required this step is to verify that this can be done without restarting mtwilson service
Restart Mtwilson service and Open the main login portal and Click on Register User Supported language(s) should appear under the language drop-down list
Login Portal--> Login --> Top Right corner under Logout button Select User Preferences This is the second way to verify that Internationalization is work, All selected languages should appear in User Preferences page
User Registration Mtwilson Login portal --> Register User--> Enter user registration info--> Select the language for the user--Register first User User must be registered with no error
Login portal --> Register User--> Enter user registration info--> Select different language for the user--Register Second User User must be registered with no error
Login portal --> Login to the page with any existing user After login, page language should be the same as selected in user registration for the current user.
Logout --> Login with different user which has different language selection Different language should appear on the all the pages.
Host Management. Test this step with two different users with different language selection Mtwilson Login portal--> Login--> Click on Host Management --> Import --> Select flat file --> Retrieve hosts See if there is any text on the page which is not translated.
Login portal--> Login--> Click on Host Management --> Import --> Select flat file --> Retrieve hosts -- Register Host Busy Screen must be translated and status messages should be translated for the hosts
Login portal--> Login--> Click on Host Management --> Import --> Select flat file --> Retrieve hosts -- Register Host. User flat file with wrong entries Error message should be correctly translated
Login portal--> Login--> Click on Host Management --> Import --> Vmware Cluster --> Insert Cluster Info --> Retrieve Cluster See if there is any text on the page which is not translated including busy loading screen
Login portal--> Login--> Click on Host Management --> Import --> Vmware Cluster --> Insert Cluster Info --> Retrieve Cluster--> Register Hosts See if there is any text on the page which is not translated including busy loading screen and Status messages should be translated for all type of hosts
Login portal--> Login--> Click on Host Management --> Import --> Vmware Cluster --> Insert Cluster Info --> Retrieve Cluster (Use wrong password and Invalid Filed entries) Error messages should be correctly translated
Login portal--> Login--> Click on Host Management -->Add host See if there is any text on the page which is not translated.
Login portal--> Login--> Click on Host Management -->Add host (Use wrong password and Invalid or blank Field entries) Look for error messages which are not translated
Login portal--> Login--> Click on Host Management -->Add host --Add Host Host should be registered with the right message
Login portal--> Login--> Click on Host Management --> Edit Host See if there is any text on the page which is not translated.
Login portal--> Login--> Click on Host Management --> Edit Host--> Delete Message should appear in correct language
Login portal--> Login--> Click on Host Management --> Edit Host --> Edit See if there is any text on the page which is not translated.
Login portal--> Login--> Click on Host Management --> Edit Host --> Edit --> Update the host with the valid record Appeared message must be translated in the correct language.
Login portal--> Login--> Click on Host Management --> Edit Host --> Edit --> Update the host with the invalid entries Error must be translated in the correct language.
Login portal--> Login--> Click on Host Management --> View Host See if there is any text on the page which is not translated.
Login portal--> Login--> Click on Host Management --> View Host page 2 if any See if there is any text on the page which is not translated.
Whitelist. Test this step with two different users with different language selection Login portal--> Login--> Whitelist --> Import From Trusted Host See if there is any text on the page which is not translated.
Login portal--> Login--> Whitelist --> Import From Trusted Host See if there is any text on the page which is not translated.
Login portal--> Login--> Whitelist --> Import From Trusted Host --> Select Citrix Xen Server --> Check BIOS select OEM --> Check HyperVisor select OEM --> Select required PCRs --> Enter Valid Host Details --> Click on Import White List (Leave register host Unchecked) See if message thrown is correctly translated.
Login portal--> Login--> Whitelist --> Import From Trusted Host --> Select Citrix Xen Server --> Check BIOS select OEM --> Check HyperVisor select OEM --> Select required PCRs --> Enter Invalid Host Details --> Click on Import White List (Leave register host Unchecked) See if error thrown is correctly translated.
Login portal--> Login--> Whitelist --> Import From Trusted Host --> Select Citrix Xen Server --> Check BIOS select OEM --> Check HyperVisor select OEM --> Select required PCRs --> Enter Valid Host Details --> check Register Host -->Click on Import White List See if message thrown is correctly translated.
Login portal--> Login--> Whitelist --> Import From Trusted Host --> KVM --> Check BIOS select OEM --> Check HyperVisor select OEM --> Select required PCRs --> Enter Valid Host Details --> Click on Import White List (Leave register host Unchecked) See if message thrown is correctly translated.
Login portal--> Login--> Whitelist --> Import From Trusted Host --> KVM --> Check BIOS select OEM --> Check HyperVisor select OEM --> Select required PCRs --> Enter invalid Host Details --> Click on Import White List (Leave register host Unchecked) See if error thrown is correctly translated.
Login portal--> Login--> Whitelist --> Import From Trusted Host --> KVM --> Check BIOS select OEM --> Check HyperVisor select OEM --> Select required PCRs --> Enter Valid Host Details --> Check Register Host -->Click on Import White List See if message thrown is correctly translated.
Login portal--> Login--> Whitelist --> Import From Trusted Host --> Vmware ESXI--> Check BIOS select OEM --> Check HyperVisor select OEM --> Select required PCRs --> Enter Valid Host Details --> Click on Import White List (Leave register host Unchecked) See if message thrown is correctly translated.
Login portal--> Login--> Whitelist --> Import From Trusted Host --> VMWare ESXi--> Check BIOS select OEM --> Check HyperVisor select OEM --> Select required PCRs --> Enter invalid Host Details --> Click on Import White List (Leave register host Unchecked) See if error thrown is correctly translated.
Login portal--> Login--> Whitelist --> Import From Trusted Host --> Vmware ESXi--> Check BIOS select OEM --> Check HyperVisor select OEM --> Select required PCRs --> Enter Valid Host Details --> Check Register Host -->Click on Import White List See if message thrown is correctly translated.
Login portal--> Login--> Whitelist --> Import From Trusted Host -->Xen--> Check BIOS select OEM --> Check HyperVisor select OEM --> Select required PCRs --> Enter Valid Host Details --> Click on Import White List (Leave register host Unchecked) See if message thrown is correctly translated.
Login portal--> Login--> Whitelist --> Import From Trusted Host -->Xen-> Check BIOS select OEM --> Check HyperVisor select OEM --> Select required PCRs --> Enter invalid Host Details --> Click on Import White List (Leave register host Unchecked) See if error thrown is correctly translated.
Login portal--> Login--> Whitelist --> Import From Trusted Host --> Xen--> Check BIOS select OEM --> Check HyperVisor select OEM --> Select required PCRs --> Enter Valid Host Details --> Check Register Host -->Click on Import White List See if message thrown is correctly translated.
Edit MLE. Test this step with two different users with different language selection Mtwilson Login portal--> Login--> Whitelist --> Edit MLE See if there is any text on the page which is not translated.
Login portal--> Login--> Whitelist --> Edit MLE -- > Edit Xenserver MLE See if there is any text on the page which is not translated.
Login portal--> Login--> Whitelist --> Edit MLE -- > Edit Xenserver MLE --> Change MLE and update See if message thrown is correctly translated.
Login portal--> Login--> Whitelist --> Edit MLE --> Edit open source host MLE and click on Show Manifest See if there is any text on the page which is not translated.
Login portal--> Login--> Whitelist --> Edit MLE --> Edit open source host MLE and update it See if message thrown is correctly translated.
Login portal--> Login--> Whitelist --> Edit MLE --> Edit ESXi host MLE and click on Show Manifest See if there is any text on the page which is not translated.
Login portal--> Login--> Whitelist --> Edit MLE --> Edit ESXi host MLE and update it See if message thrown is correctly translated.
Edit OS. Test this step with two different users with different language selection Login portal--> Login--> Whitelist --> Edit OS See if there is any text on the page which is not translated.
Login portal--> Login--> Whitelist --> Edit OS -- Edit and Update description See if message thrown is correctly translated and it should update the field.
Login portal--> Login--> Whitelist --> Edit OS -- Add OS See if there is any text on the page which is not translated.
Login portal--> Login--> Whitelist --> Edit OS -- Add OS--> Enter Valid Entries and click Add See if message thrown is correctly translated.
Login portal--> Login--> Whitelist --> Edit OS -- Add OS--> Enter invalid Entries and click Add See if message thrown is correctly translated.
Login portal--> Login--> Whitelist --> Edit OS -- Delete OS Delete message must be translated and if OS is associated with any MLE then error message is also translated.
Edit OEM. Test this step with two different users with different language selection Login portal--> Login--> Whitelist --> Edit OEM See if there is any text on the page which is not translated.
Login portal--> Login--> Whitelist --> Edit OEM-- Edit and Update description See if message thrown is correctly translated and it should update the field.
Login portal--> Login--> Whitelist --> Edit OEM -- Add OEM See if there is any text on the page which is not translated.
Login portal--> Login--> Whitelist --> Edit OEM-- Add OEM--> Enter Valid Entries and click Add See if message thrown is correctly translated.
Login portal--> Login--> Whitelist --> Edit OEM -- Add OEM--> Enter invalid Entries and click Add See if message thrown is correctly translated.
Login portal--> Login--> Whitelist --> Edit OS -- Delete OEM Delete message must be translated and if OEM is associated with any MLE then error message is also translated.
Administration. Test this step with two different users with different language selection Login portal--> Login-->Administration --> Pending request See if there is any text on the page which is not translated.
Login portal--> Login-->Administration --> List Users See if there is any text on the page which is not translated.
Login portal--> Login-->Administration --> Delete Users See if there is any text on the page which is not translated.
Login portal--> Login-->Administration --> Delete Users --> Delete See if message thrown is correctly translated.
Login portal--> Login-->Administration -->Extend User See if there is any text on the page which is not translated.
Login portal--> Login-->Administration -->View Certificates --> Download each See if there is any text on the page which is not translated.
Dashboard. Test this step with two different users with different language selection Login portal --> Login--> Dashboard See if there is any text on the page which is not translated.
Login portal --> Login--> Dashboard--> Click on Trust Report See if there is any text on the page which is not translated on Trust Report.
Login portal --> Login--> Dashboard--> Click on Trust Assertion See if there is any text on the page which is not translated.
Login portal--> Login--> Dashboard--> Hit Refresh for trusted host Status must be translated.
Login portal--> Login--> Dashboard--> Hit Refresh for Untrusted host Status must be translated.
Login portal --> Login--> Dashboard--> Hit Refresh for Unreachable host Status must be translated.
Login portal --> Login--> Dashboard--> Hit Refresh Status must be translated.
Bulk Refresh. Test this step with two different users with different language selection Login portal--> Login--> Click on Trust-->Bulk Refresh--> Select all the hosts and hit refresh See if there is any text on the page which is not translated including busy page Loading status.
Login portal--> Login--> Click on Trust --> Bulk Refresh--> Click on page 2 if any--> Select all the hosts and hit refresh See if there is any text on the page which is not translated including busy page Loading status.
Reports. Test this step with two different users with different language selection Login portal--> Login--> Click on Trust --> Reports--> Select all hosts and get report See if there is any text on the page which is not translated including busy page Loading status.
User Preferences Login portal--> User Preferences See if there is any text on the page which is not translated including busy page Loading status.
Login portal--> User Preferences --> Change language and login with the first user See if there is any text on the page which is not translated.
Login portal--> User Preferences --> Change language and login with the Second user with different language See if there is any text on the page which is not translated.
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
Press h to open a hovercard with more details.