CA/Information Checklist: Difference between revisions

Jump to navigation Jump to search
→‎Create a Root Inclusion Case: Additional changes for new CCADB processes
(→‎Create a Root Inclusion Case: Changes in progress)
(→‎Create a Root Inclusion Case: Additional changes for new CCADB processes)
Line 13: Line 13:
== Create a Root Inclusion Case ==
== Create a Root Inclusion Case ==


'''UNDER REVISION'''
More detailed CCADB guidance on adding root certificates to the CCADB is also available [https://docs.google.com/document/d/1ttmeeqO6WxDWe_deDNsGUgDO_LpsvoduFNZeHHMw_f8 here].


If your CA does not yet have access to the CCADB, then you may request access here:  
If your CA does not yet have access to the CCADB, then you may request access here:  
Line 31: Line 31:


'''CA OWNER'''
'''CA OWNER'''
 
Required fields include:
#CA Owner Name
#Address
#Company Website
#A CA Email Alias (distribution list) email address


'''ROOT INFORMATION'''
'''ROOT INFORMATION'''
Line 39: Line 43:
#Fill in the data for the required fields for the root under the “ROOT INFORMATION” tab.
#Fill in the data for the required fields for the root under the “ROOT INFORMATION” tab.
#Repeat this process for each of the Root Certificates that need to be added.
#Repeat this process for each of the Root Certificates that need to be added.
 
#Explain why each root certificate needs to be included in the root store
#  
#* Explain why this root certificate needs to be included in the root store
 
 


'''AUDITS'''
'''AUDITS'''
Line 52: Line 52:
#*For each root certificate to be considered in your request, check the appropriate boxes in the "Root Stores Applying To" column
#*For each root certificate to be considered in your request, check the appropriate boxes in the "Root Stores Applying To" column
#*For each root certificate to be considered in your request, check the boxes corresponding to the audit statements that apply.  
#*For each root certificate to be considered in your request, check the boxes corresponding to the audit statements that apply.  
#*Then click on the 'Apply Changes' button. This will create corresponding Root Cases.


'''POLICY DOCUMENTS'''
'''POLICY DOCUMENTS'''
Line 61: Line 60:


'''TEST WEBSITES'''
'''TEST WEBSITES'''
#Click on the ‘Edit Test Websites’ button (which may be in the button overflow – upside down triangle) to enter the test websites for new root certificates if you are requesting the Websites (TLS/SSL) trust bit.
#Click on the ‘Edit Test Websites’ button (which may be in the button overflow – upside down triangle) to enter the test websites for new root certificates if you are requesting the Websites (TLS server authentication) trust bit.
#* Click on the 'Test Websites Validation' button, resolve all failures, then click on 'Re-run Validation'
#* Click on the 'Test Websites Validation' button, resolve all failures, then click on 'Re-run Validation'
#* Provide evidence of testing and results
#* Provide evidence of testing and results
Line 77: Line 76:
#Click on the 'Get URLs' button (which may be in the button overflow – upside down triangle) and copy the line that begins with “Mozilla Root Inclusion Case Information:” into a Comment in [[CA/Application_Instructions#Create_Root_Inclusion.2FUpdate_Request|your Bugzilla Bug]]. The line to copy and paste into the Bugzilla Bug looks like:  
#Click on the 'Get URLs' button (which may be in the button overflow – upside down triangle) and copy the line that begins with “Mozilla Root Inclusion Case Information:” into a Comment in [[CA/Application_Instructions#Create_Root_Inclusion.2FUpdate_Request|your Bugzilla Bug]]. The line to copy and paste into the Bugzilla Bug looks like:  
#*Mozilla Root Inclusion Case Information: https://ccadb-public.secure.force.com/mozilla/PrintViewForCase?CaseNumber=00000341
#*Mozilla Root Inclusion Case Information: https://ccadb-public.secure.force.com/mozilla/PrintViewForCase?CaseNumber=00000341
#*This will trigger step 2 of Mozilla’s root inclusion process.


IMPORTANT:
IMPORTANT:
Confirmed users
377

edits

Navigation menu