1711589 - Enable CAs to update their non-audit information more frequently

Status: RESOLVED FIXED

(CA Program :: Common CA Database, task)

Description

[Kathleen Wilson]

Enable CAs to update their non-audit information more frequently on root certs (CP/CPS, test websites, full CRLs, etc.) and CA Owner records.

New Case Type: CA Information Update Request (Non-Audit)

What CAs should be able to update mid-year:

• Root Cert Page
  ** Policy Documents (similar to Root Inclusion Case)
  ** Test Websites (similar to Root Inclusion Case)
  ** Full CRL Issued By This CA
  ** JSON Array of Partitioned CRLs
  ** Description
• CA Owner Page
  ** Every field on the CA Owner DETAILS page other than CA Owner/Certificate Record Type, Type, CA Owner/Certificate Number, Status, and the root-store-operator-specific sections.

Start with copying the way we currently do Audit Cases, and copy current mechanisms for the 'Update Policy Documents' and 'Edit Test Websites' buttons. But do not copy over all of the auditor and audit sections/fields.

Then work on new flow, so the user would:

1. enter any updated CA Owner data
2. select root certificates to update
3. update cp/cps documents (if any root certs selected)
4. edit test websites (if any root certs selected)

Simplify the process for a root store operator to review/verify the changed data and copy it over to the CA Owner and Root Certificate records.

Redesign flow and pages using the Lightning components (migrate from VisualForce, which is in maintenance mode) -- adds development time to the project, but long term this will be better for performance, usability, future features, support, etc.

Comment 1

[Poonam Bhargava]

Hi Kathleen,

Some of the non-audit case changes are ready for you to preview in sandbox. We have redesigned it using LWC (Lightning Web Component) which are reusable custom HTML elements built using HTML and JavaScript. It is light-weight and gives better performance.

The general flow would be to first start with the CA Owner record -> go to Case related list -> click on 'New' -> select Non-Audit record type -> 'Save' -> go to the newly created case & update the information.

The new case layout has 4 tabs:

• CA Owner
• Select Root Certificates
• Policy Documents
• Test Websites
• Other Fields

The fields on 'CA Owner' page default to the values from CA Owner record. Based on the selection made on 'Select Root Certificates' page, the data will be pre-filled on 'Policy Documents', 'Test Websites' and 'Other Fields' pages. 'Edit'/'Save' buttons are on available on each page. On 'Policy Documents' records, use the down arrow on the section header to edit the record. It is not fully functional yet. 'Show Changes' and 'Sync' are also being developed.

I would appreciate any feedback on the work done so far. Thank you.

Regards,
Poonam

(In reply to Kathleen Wilson from comment #0)

Enable CAs to update their non-audit information more frequently on root certs (CP/CPS, test websites, full CRLs, etc.) and CA Owner records.

New Case Type: CA Information Update Request (Non-Audit)

What CAs should be able to update mid-year:

• Root Cert Page
  ** Policy Documents (similar to Root Inclusion Case)
  ** Test Websites (similar to Root Inclusion Case)
  ** Full CRL Issued By This CA
  ** JSON Array of Partitioned CRLs
  ** Description
• CA Owner Page
  ** Every field on the CA Owner DETAILS page other than CA Owner/Certificate Record Type, Type, CA Owner/Certificate Number, Status, and the root-store-operator-specific sections.

Start with copying the way we currently do Audit Cases, and copy current mechanisms for the 'Update Policy Documents' and 'Edit Test Websites' buttons. But do not copy over all of the auditor and audit sections/fields.

Then work on new flow, so the user would:

1. enter any updated CA Owner data
2. select root certificates to update
3. update cp/cps documents (if any root certs selected)
4. edit test websites (if any root certs selected)

Simplify the process for a root store operator to review/verify the changed data and copy it over to the CA Owner and Root Certificate records.

Redesign flow and pages using the Lightning components (migrate from VisualForce, which is in maintenance mode) -- adds development time to the project, but long term this will be better for performance, usability, future features, support, etc.

Comment 2

[Kathleen Wilson]

This new Case type called “CA Information Update Request (Non-Audit)" may be used now. Instructions

Comment 3

[Kathleen Wilson]

Remaining items to resolve:

• The 'Open CA Information Update Cases..' report needs to be visible in the Task List for all root store operators. And the report should be reverse sorted so that the rows with "Verification By Root Store" status are at the top.

• In the Cases tab, change the columns of the "All CA Information Update Request Cases" and "Open CA Information Update Request Cases" to: Case Number, Subject, Case Request Status, CA Owner, Last Modified Date, Last Modified By Alias

• Change the Case Request Status to Complete and close the Case when the case has been submitted to the root store operator and all Tabs are either "Data Synced" or "No Data to Verify".

• Add Help text to all of the fields in the Case page that have corresponding help text in the CA Owner and Root Certificate pages. i.e. Copy the help text from the corresponding fields on the CA Owner and Root Certificate records.

• Add check to make sure that the value entered into 'Full CRL Issued By This CA' on the OTHER FIELDS tab is a valid URL (e.g. begins with http://)

• Add ability to un-delete a document that has been deleted in the same Case.

• When the user has clicked on the "Show Changes" button and then goes to another tab, reset the tab that they are leaving so that when they go back to that tab they are not still on "Show Changes".

Comment 4

[Poonam Bhargava]

Hi Kathleen,

Most of the changes are done. Please see my comments below:

• The 'Open CA Information Update Cases..' report needs to be visible in the Task List for all root store operators. And the report should be reverse sorted so that the rows with "Verification By Root Store" status are at the top.

      Added the report for all root store with reverse sort on Status field.
  

• In the Cases tab, change the columns of the "All CA Information Update Request Cases" and "Open CA Information Update Request Cases" to: Case Number, Subject, Case Request Status, CA Owner, Last Modified Date, Last Modified By Alias

      List view updates in production, SbxCCADB & NonAudit sandboxes.
  

• Change the Case Request Status to Complete and close the Case when the case has been submitted to the root store operator and all Tabs are either "Data Synced" or "No Data to Verify".

       Updated the code to mark the case 'Complete' when all Tabs are either "Data Synced" or "No Data to Verify".
  

• Add Help text to all of the fields in the Case page that have corresponding help text in the CA Owner and Root Certificate pages. i.e. Copy the help text from the corresponding fields on the CA Owner and Root Certificate records.

        Currently working on adding Help text to all fields.
  

• Add check to make sure that the value entered into 'Full CRL Issued By This CA' on the OTHER FIELDS tab is a valid URL (e.g. begins with http://)

        A trigger now validates the Full CRL links separated by comma.
  

• Add ability to un-delete a document that has been deleted in the same Case.

        Not yet started 
  

• When the user has clicked on the "Show Changes" button and then goes to another tab, reset the tab that they are leaving so that when they go back to that tab they are not still on "Show Changes".

         Changed the program logic to reset the tab.
  

Let me know if I have missed anything during your testing.

Regards,
Poonam

Comment 5

[Kathleen Wilson]

I noticed two new items to resolve:

1. In production Case #00000862 in the POLICY DOCUMENTS tab, Policy Document ID - 1936 has Change Status of "Data to Verify", but it is not clear what data needs to be verified. And when I click on the Show Changes button there are no changes to be synced for that policy document.

2. Please add the 'Get URLs' button to the new Case type (after the 'Help' button)

I verified the completed items per Comment #4 in production, so the remaining items are:

• Add Help text to all of the fields in the Case page that have corresponding help text in the CA Owner and Root Certificate pages. i.e. Copy the help text from the corresponding fields on the CA Owner and Root Certificate records.

        Currently working on adding Help text to all fields.
  

• Add ability to un-delete a document that has been deleted in the same Case.

        Not yet started 
  

Thanks!

Comment 6

[Poonam Bhargava]

Hi Kathleen,

The 'Get URLs' button is now available in production on Non-Audit cases.

Additional changes have been done in both sandboxes (SbxCCADB & NonAudit).

• For Case #862, necessary code changes were done to correct the issue.

• 'Help' text was added to fields.

• Added un-delete to Policy Doc records on Non-Audit cases.

Please send me your feedback, after you have verified the changes the NonAudit sandbox.

Thank you.
Poonam

Comment 7

[Kathleen Wilson]

(In reply to Poonam Bhargava from comment #6)

The 'Get URLs' button is now available in production on Non-Audit cases.

Verified in production.

• For Case #862, necessary code changes were done to correct the issue.

Verified in NonAudit sandbox, please move to production.

• Added un-delete to Policy Doc records on Non-Audit cases.

Verified in NonAudit sandbox Case #890. Seemed to work fine, but later got a "Component Error" when I went to the TEST WEBSITES tab within the same case. I'll attach a screenshot of the error. I was able to get out of it by going back to the Cases tab at the top and re-opening the case, and then the TEST WEBSITES tab worked.

• 'Help' text was added to fields.

Verified in NonAudit sandbox. Please make the following minor changes to the help text in the POLICY DOCUMENTS tab, then move all help text updates to production:

-- Change help for CA Document Repository field to: URL to where the CA's policy documentation may be found. More than one URL may be provided as a semicolon-separated list.

-- Chang help for Policy Documentation field to: Optional explanation about the CA's policy documentation

-- Delete help from Associated Trust Bits and Additional Policy identifiers

Comment 8

[Kathleen Wilson]

Attachment: Screen Shot 2021-11-10 at 3.11.22 PM.png

Comment 9

[Kathleen Wilson]

During testing, I noticed one more thing that we should fix...

The "Document Last Update Date" field in the POLICY DOCUMENTS tab is displaying the date in format yyyy-mm-dd. But when I edit the date, it is displayed in format MMM dd, yyyy.

Please update this "Document Last Update Date" field to use, display, and require the date format that is used everywhere else in the CCADB: mm/dd/yyyy

Also, note that the first time I copied the date 2021-05-04 into the edit of this field, I think I was blocked from saving the date in that format. But now in Case 890 in sandbox, it appears to be saving the date, but then the resulting date is empty.

Comment 10

[Poonam Bhargava]

I could not reproduce the component error (related to the screen shot). If you are able to do it again, please send me the steps. It is usually does to access issue which you already have, or it could be due to caching of older version of the program.

The 'help' text have been updated on the fields which you have specified.

Comment 11

[Poonam Bhargava]

Corrections related to "Document Last Update Date" field are also done. The date format mm/dd/yyyy is now consistent in non-audit cases.

Comment 12

[Kathleen Wilson]

Tested in nonaudit sandbox, and ready to be moved to production:

• For Case #862, necessary code changes were done to correct the issue.
• 'Help' text was added to fields.
• Added un-delete to Policy Doc records on Non-Audit cases.
• Corrections related to "Document Last Update Date" field are also done. The date format mm/dd/yyyy is now consistent in non-audit cases.

I was not able to reproduce the error in comment #8.

Comment 13

[Poonam Bhargava]

(In reply to Kathleen Wilson from comment #12)

Tested in nonaudit sandbox, and ready to be moved to production:

• For Case #862, necessary code changes were done to correct the issue.
• 'Help' text was added to fields.
• Added un-delete to Policy Doc records on Non-Audit cases.
• Corrections related to "Document Last Update Date" field are also done. The date format mm/dd/yyyy is now consistent in non-audit cases.

I was not able to reproduce the error in comment #8.

These changes have been deployed in production.

Comment 14

[Kathleen Wilson]

Thanks!