This article will explain what an IPAWS Collaborative Operating Group, or COG, is and how to add or update their configurations and certificates in the system.
Article Navigation
- Collaborative Operating Group Overview
- Add a COG to IPAWS
- Update a COG Configuration
- Article Glossary
Not finding what you are looking for? View additional resources
Collaborative Operating Groups Overview
A Collaborative Operating Group, or COG, is a term used by IPAWS to designate an organization that is responsible for emergency alerting. A COG is established with IPAWS when a Federal, State, local, or tribal alerting authority executes an MOA with FEMA in order to use IPAWS. Further information regarding this process may be found in our Apply for Access to IPAWS article.
Types of COGs
- Demo COG: Demo COGs are used to carry out FEMA-required training and tests, as well as carrying out internal training and testing beyond FEMA requirements.
- Live COG: A Live COG is required to send out live WEA and EAS alerts.
Add a COG to IPAWS
Once you have received IPAWS COG information for your Live COG, Demo COG, or both, you can configure them and add their certificates to our system by following the steps below.
- Log in to the IPAWS website if you have not already
Note: You can navigate to the IPAWS website using the website URL, or you can sign in to the Mass Notification system (formerly CivicReady) and click the Public Communication and Send IPAWS Alert options on the left-hand menu of the dashboard. If you do not see the Send IPAWS Alert option, you may not have permission to send alerts.
- Navigate to the Admin tab, then click the Configurations option
- Click the Create New link to create a new configuration
- You will be taken to the Create an IPAWS Configuration page
- Enter a name for the configuration in the Name field, if desired
Note: This name will be displayed on the message creation form. - Fill in the IPAWS-OPEN Endpoint fields
- IPAWS-OPEN Endpoint: Choose 'Live' if your COG ID begins with a 2, or choose 'Demo' if your COG ID begins with a 3
- COG ID: Enter the six-digit number associated with your COG
- COG Username: Enter the name of the agency associated with your COG
- Fill in the Certificate (JKS) fields
-
Cert Alias: Enter the filename of the certificate (.jks file) sent to you, minus the .jks file extension
- Example: IPAWS120028
- Keystore Password & Key Password: These values are stored in a text file in the same zip file that contains the certificate above
-
Cog Certificate: Click the Choose File button to locate and attach the .jks file that matches the details entered above
Note: These values must match or the certificate configuration will be invalid.
-
Cert Alias: Enter the filename of the certificate (.jks file) sent to you, minus the .jks file extension
- Click the Create button to save the configuration
Note: Click the Back to List link to return to the IPAWS Configurations page.
Update a COG Configuration
This section will show you how to update the configuration and certificates for your Live COGs and Demo COGs.
- Log in to the IPAWS website if you have not already
Note: You can navigate to the IPAWS website using the website URL, or you can sign in to the Mass Notification system (formerly CivicReady) and click the Public Communication and Send IPAWS Alert options on the left-hand menu of the dashboard. If you do not see the Send IPAWS Alert option, you may not have permission to send alerts.
- Navigate to the Admin tab, then click the Configurations option
- Click the name of the configuration you want to update
- You will be taken to the Edit an IPAWS Configuration page
Note: The Upload new certificate link in the IPAWS-OPEN Endpoint section must be clicked to expand and display the Certificate (JKS) section. - Enter or edit the name of the configuration in the Name field, if desired
- Edit the IPAWS-OPEN Endpoint fields, if desired
- IPAWS-OPEN Endpoint: The Live or Demo endpoint for the configuration
- COG ID: The six-digit ID associated with your COG
- COG Username: The name of the agency associated with your COG
- Certificate Issue Date: Auto-fills with the date the certificate was issued
- Certificate Expiration Date: Auto-fills with the date the certificate will expire
-
Certificate Alias: Auto-fills with the filename of the certificate (.jks file) sent to you, minus the .jks file extension
- Example: IPAWS120028
- Upload new certificate: Click this link to reveal or hide the Certificate (JKS) section, which is where you can replace an expiring configuration with a new certificate
- View Permissions: Click this button to retrieve and display the current configuration of this certificate from the IPAWS servers
- Update Permissions: Click this button to retrieve, update, and display the current configuration of this certificate from the IPAWS servers.
- Delete Configuration: Click this button to remove this configuration from IPAWS entirely
- Fill in or edit the Certificate (JKS) fields to replace the existing configuration with a new certificate, if needed
-
Cert Alias: The filename of the certificate (.jks file) sent to you, minus the .jks file extension
- Example: IPAWS120028
- Keystore Password & Key Password: These values are stored in a text file in the same zip file that contains the certificate above
-
Cog Certificate: Click the Choose File button to locate and attach the .jks file that matches the details entered above
Note: These values must match or the certificate configuration will be invalid.
-
Cert Alias: The filename of the certificate (.jks file) sent to you, minus the .jks file extension
- Click the Save button to save all changes
Note: Click the Back to List link to return to the IPAWS Configurations page.
Article Glossary
The terms located in this section are listed alphabetically.
- .jks: Java KeyStore file extension
- COG: Collaborative Operating Group
- DEMO: Demonstration
- EAS: Emergency Alert System
- FEMA: Federal Emergency Management Agency
- ID: Identification Number
- IPAWS: Integrated Public Alert and Warning System (IPAWS)
- IPAWS-OPEN: Integrated Public Alert and Warning System Open Platform for Emergency Networks
- JKS: Java KeyStore
- MOA: Memorandum of Agreement
- WEA: Wireless Emergency Alerts
Resources
Comments
Let us know what was helpful or not helpful about the article.0 comments
Please sign in to leave a comment.