emass_client 3.4.0 → 3.9.1

data/lib/emass_client/models/artifacts_response_del_data_inner.rb

@@ -3,10 +3,10 @@
 
 #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records.   <strong>Register External Application (that use the eMASS API)</strong></br> New users will need to [register](https://nisp.emass.apps.mil/Content/Help/jobaids/eMASS_OT_NewUser_Job_Aid.pdf) an API key with the eMASS development team prior to accessing the site for the first time. The eMASS REST API  requires a client certificate (SSL/TLS, DoD PKI only). Use the `Registration` endpoint to register the client certificate.</br></br>  Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key.  The API key must be provided in the request header for all endpoint calls (api-key). If the service receives an untrusted certificate or API key, a 401 error response code will be returned along with an error message.</br></br>  <strong>Available Request Headers</strong></br> <table>   <tr>     <th align=left>key</th>     <th align=left>Example Value</th>     <th align=left>Description</th>   </tr>   <tr>     <td>`api-key`</td>     <td>api-key-provided-by-emass</td>     <td>This API key must be provided in the request header for all endpoint calls</td>   </tr>   <tr>     <td>`user-uid`</td>     <td>USER.UID.KEY</td>     <td>This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls</td>   </tr>   <tr>     <td></td><td></td>     <td>       Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC     </td>   </tr> </table>  </br><strong>Approve API Client for Actionable Requests</strong></br> Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records.  To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: 
 
-The version of the OpenAPI document: v3.4
+The version of the OpenAPI document: v3.9
 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 6.1.1-SNAPSHOT
+OpenAPI Generator version: 7.0.0-SNAPSHOT
 
 =end
 

data/lib/emass_client/models/artifacts_response_get.rb

@@ -3,10 +3,10 @@
 
 #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records.   <strong>Register External Application (that use the eMASS API)</strong></br> New users will need to [register](https://nisp.emass.apps.mil/Content/Help/jobaids/eMASS_OT_NewUser_Job_Aid.pdf) an API key with the eMASS development team prior to accessing the site for the first time. The eMASS REST API  requires a client certificate (SSL/TLS, DoD PKI only). Use the `Registration` endpoint to register the client certificate.</br></br>  Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key.  The API key must be provided in the request header for all endpoint calls (api-key). If the service receives an untrusted certificate or API key, a 401 error response code will be returned along with an error message.</br></br>  <strong>Available Request Headers</strong></br> <table>   <tr>     <th align=left>key</th>     <th align=left>Example Value</th>     <th align=left>Description</th>   </tr>   <tr>     <td>`api-key`</td>     <td>api-key-provided-by-emass</td>     <td>This API key must be provided in the request header for all endpoint calls</td>   </tr>   <tr>     <td>`user-uid`</td>     <td>USER.UID.KEY</td>     <td>This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls</td>   </tr>   <tr>     <td></td><td></td>     <td>       Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC     </td>   </tr> </table>  </br><strong>Approve API Client for Actionable Requests</strong></br> Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records.  To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: 
 
-The version of the OpenAPI document: v3.4
+The version of the OpenAPI document: v3.9
 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 6.1.1-SNAPSHOT
+OpenAPI Generator version: 7.0.0-SNAPSHOT
 
 =end
 

data/lib/emass_client/models/artifacts_response_put_post.rb

@@ -3,10 +3,10 @@
 
 #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records.   <strong>Register External Application (that use the eMASS API)</strong></br> New users will need to [register](https://nisp.emass.apps.mil/Content/Help/jobaids/eMASS_OT_NewUser_Job_Aid.pdf) an API key with the eMASS development team prior to accessing the site for the first time. The eMASS REST API  requires a client certificate (SSL/TLS, DoD PKI only). Use the `Registration` endpoint to register the client certificate.</br></br>  Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key.  The API key must be provided in the request header for all endpoint calls (api-key). If the service receives an untrusted certificate or API key, a 401 error response code will be returned along with an error message.</br></br>  <strong>Available Request Headers</strong></br> <table>   <tr>     <th align=left>key</th>     <th align=left>Example Value</th>     <th align=left>Description</th>   </tr>   <tr>     <td>`api-key`</td>     <td>api-key-provided-by-emass</td>     <td>This API key must be provided in the request header for all endpoint calls</td>   </tr>   <tr>     <td>`user-uid`</td>     <td>USER.UID.KEY</td>     <td>This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls</td>   </tr>   <tr>     <td></td><td></td>     <td>       Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC     </td>   </tr> </table>  </br><strong>Approve API Client for Actionable Requests</strong></br> Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records.  To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: 
 
-The version of the OpenAPI document: v3.4
+The version of the OpenAPI document: v3.9
 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 6.1.1-SNAPSHOT
+OpenAPI Generator version: 7.0.0-SNAPSHOT
 
 =end
 

data/lib/emass_client/models/artifacts_response_put_post_data_inner.rb

@@ -3,10 +3,10 @@
 
 #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records.   <strong>Register External Application (that use the eMASS API)</strong></br> New users will need to [register](https://nisp.emass.apps.mil/Content/Help/jobaids/eMASS_OT_NewUser_Job_Aid.pdf) an API key with the eMASS development team prior to accessing the site for the first time. The eMASS REST API  requires a client certificate (SSL/TLS, DoD PKI only). Use the `Registration` endpoint to register the client certificate.</br></br>  Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key.  The API key must be provided in the request header for all endpoint calls (api-key). If the service receives an untrusted certificate or API key, a 401 error response code will be returned along with an error message.</br></br>  <strong>Available Request Headers</strong></br> <table>   <tr>     <th align=left>key</th>     <th align=left>Example Value</th>     <th align=left>Description</th>   </tr>   <tr>     <td>`api-key`</td>     <td>api-key-provided-by-emass</td>     <td>This API key must be provided in the request header for all endpoint calls</td>   </tr>   <tr>     <td>`user-uid`</td>     <td>USER.UID.KEY</td>     <td>This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls</td>   </tr>   <tr>     <td></td><td></td>     <td>       Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC     </td>   </tr> </table>  </br><strong>Approve API Client for Actionable Requests</strong></br> Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records.  To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: 
 
-The version of the OpenAPI document: v3.4
+The version of the OpenAPI document: v3.9
 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 6.1.1-SNAPSHOT
+OpenAPI Generator version: 7.0.0-SNAPSHOT
 
 =end
 

data/lib/emass_client/models/cac_get.rb

@@ -3,10 +3,10 @@
 
 #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records.   <strong>Register External Application (that use the eMASS API)</strong></br> New users will need to [register](https://nisp.emass.apps.mil/Content/Help/jobaids/eMASS_OT_NewUser_Job_Aid.pdf) an API key with the eMASS development team prior to accessing the site for the first time. The eMASS REST API  requires a client certificate (SSL/TLS, DoD PKI only). Use the `Registration` endpoint to register the client certificate.</br></br>  Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key.  The API key must be provided in the request header for all endpoint calls (api-key). If the service receives an untrusted certificate or API key, a 401 error response code will be returned along with an error message.</br></br>  <strong>Available Request Headers</strong></br> <table>   <tr>     <th align=left>key</th>     <th align=left>Example Value</th>     <th align=left>Description</th>   </tr>   <tr>     <td>`api-key`</td>     <td>api-key-provided-by-emass</td>     <td>This API key must be provided in the request header for all endpoint calls</td>   </tr>   <tr>     <td>`user-uid`</td>     <td>USER.UID.KEY</td>     <td>This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls</td>   </tr>   <tr>     <td></td><td></td>     <td>       Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC     </td>   </tr> </table>  </br><strong>Approve API Client for Actionable Requests</strong></br> Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records.  To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: 
 
-The version of the OpenAPI document: v3.4
+The version of the OpenAPI document: v3.9
 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 6.1.1-SNAPSHOT
+OpenAPI Generator version: 7.0.0-SNAPSHOT
 
 =end
 

data/lib/emass_client/models/cac_response_get.rb

@@ -3,10 +3,10 @@
 
 #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records.   <strong>Register External Application (that use the eMASS API)</strong></br> New users will need to [register](https://nisp.emass.apps.mil/Content/Help/jobaids/eMASS_OT_NewUser_Job_Aid.pdf) an API key with the eMASS development team prior to accessing the site for the first time. The eMASS REST API  requires a client certificate (SSL/TLS, DoD PKI only). Use the `Registration` endpoint to register the client certificate.</br></br>  Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key.  The API key must be provided in the request header for all endpoint calls (api-key). If the service receives an untrusted certificate or API key, a 401 error response code will be returned along with an error message.</br></br>  <strong>Available Request Headers</strong></br> <table>   <tr>     <th align=left>key</th>     <th align=left>Example Value</th>     <th align=left>Description</th>   </tr>   <tr>     <td>`api-key`</td>     <td>api-key-provided-by-emass</td>     <td>This API key must be provided in the request header for all endpoint calls</td>   </tr>   <tr>     <td>`user-uid`</td>     <td>USER.UID.KEY</td>     <td>This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls</td>   </tr>   <tr>     <td></td><td></td>     <td>       Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC     </td>   </tr> </table>  </br><strong>Approve API Client for Actionable Requests</strong></br> Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records.  To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: 
 
-The version of the OpenAPI document: v3.4
+The version of the OpenAPI document: v3.9
 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 6.1.1-SNAPSHOT
+OpenAPI Generator version: 7.0.0-SNAPSHOT
 
 =end
 

data/lib/emass_client/models/cac_response_post.rb

@@ -3,10 +3,10 @@
 
 #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records.   <strong>Register External Application (that use the eMASS API)</strong></br> New users will need to [register](https://nisp.emass.apps.mil/Content/Help/jobaids/eMASS_OT_NewUser_Job_Aid.pdf) an API key with the eMASS development team prior to accessing the site for the first time. The eMASS REST API  requires a client certificate (SSL/TLS, DoD PKI only). Use the `Registration` endpoint to register the client certificate.</br></br>  Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key.  The API key must be provided in the request header for all endpoint calls (api-key). If the service receives an untrusted certificate or API key, a 401 error response code will be returned along with an error message.</br></br>  <strong>Available Request Headers</strong></br> <table>   <tr>     <th align=left>key</th>     <th align=left>Example Value</th>     <th align=left>Description</th>   </tr>   <tr>     <td>`api-key`</td>     <td>api-key-provided-by-emass</td>     <td>This API key must be provided in the request header for all endpoint calls</td>   </tr>   <tr>     <td>`user-uid`</td>     <td>USER.UID.KEY</td>     <td>This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls</td>   </tr>   <tr>     <td></td><td></td>     <td>       Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC     </td>   </tr> </table>  </br><strong>Approve API Client for Actionable Requests</strong></br> Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records.  To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: 
 
-The version of the OpenAPI document: v3.4
+The version of the OpenAPI document: v3.9
 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 6.1.1-SNAPSHOT
+OpenAPI Generator version: 7.0.0-SNAPSHOT
 
 =end
 

data/lib/emass_client/models/cac_response_post_data_inner.rb

@@ -3,10 +3,10 @@
 
 #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records.   <strong>Register External Application (that use the eMASS API)</strong></br> New users will need to [register](https://nisp.emass.apps.mil/Content/Help/jobaids/eMASS_OT_NewUser_Job_Aid.pdf) an API key with the eMASS development team prior to accessing the site for the first time. The eMASS REST API  requires a client certificate (SSL/TLS, DoD PKI only). Use the `Registration` endpoint to register the client certificate.</br></br>  Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key.  The API key must be provided in the request header for all endpoint calls (api-key). If the service receives an untrusted certificate or API key, a 401 error response code will be returned along with an error message.</br></br>  <strong>Available Request Headers</strong></br> <table>   <tr>     <th align=left>key</th>     <th align=left>Example Value</th>     <th align=left>Description</th>   </tr>   <tr>     <td>`api-key`</td>     <td>api-key-provided-by-emass</td>     <td>This API key must be provided in the request header for all endpoint calls</td>   </tr>   <tr>     <td>`user-uid`</td>     <td>USER.UID.KEY</td>     <td>This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls</td>   </tr>   <tr>     <td></td><td></td>     <td>       Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC     </td>   </tr> </table>  </br><strong>Approve API Client for Actionable Requests</strong></br> Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records.  To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: 
 
-The version of the OpenAPI document: v3.4
+The version of the OpenAPI document: v3.9
 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 6.1.1-SNAPSHOT
+OpenAPI Generator version: 7.0.0-SNAPSHOT
 
 =end
 

data/lib/emass_client/models/cloud_resources_post.rb

@@ -3,10 +3,10 @@
 
 #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records.   <strong>Register External Application (that use the eMASS API)</strong></br> New users will need to [register](https://nisp.emass.apps.mil/Content/Help/jobaids/eMASS_OT_NewUser_Job_Aid.pdf) an API key with the eMASS development team prior to accessing the site for the first time. The eMASS REST API  requires a client certificate (SSL/TLS, DoD PKI only). Use the `Registration` endpoint to register the client certificate.</br></br>  Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key.  The API key must be provided in the request header for all endpoint calls (api-key). If the service receives an untrusted certificate or API key, a 401 error response code will be returned along with an error message.</br></br>  <strong>Available Request Headers</strong></br> <table>   <tr>     <th align=left>key</th>     <th align=left>Example Value</th>     <th align=left>Description</th>   </tr>   <tr>     <td>`api-key`</td>     <td>api-key-provided-by-emass</td>     <td>This API key must be provided in the request header for all endpoint calls</td>   </tr>   <tr>     <td>`user-uid`</td>     <td>USER.UID.KEY</td>     <td>This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls</td>   </tr>   <tr>     <td></td><td></td>     <td>       Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC     </td>   </tr> </table>  </br><strong>Approve API Client for Actionable Requests</strong></br> Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records.  To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: 
 
-The version of the OpenAPI document: v3.4
+The version of the OpenAPI document: v3.9
 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 6.1.1-SNAPSHOT
+OpenAPI Generator version: 7.0.0-SNAPSHOT
 
 =end
 

data/lib/emass_client/models/cloud_resources_response_post.rb

@@ -3,10 +3,10 @@
 
 #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records.   <strong>Register External Application (that use the eMASS API)</strong></br> New users will need to [register](https://nisp.emass.apps.mil/Content/Help/jobaids/eMASS_OT_NewUser_Job_Aid.pdf) an API key with the eMASS development team prior to accessing the site for the first time. The eMASS REST API  requires a client certificate (SSL/TLS, DoD PKI only). Use the `Registration` endpoint to register the client certificate.</br></br>  Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key.  The API key must be provided in the request header for all endpoint calls (api-key). If the service receives an untrusted certificate or API key, a 401 error response code will be returned along with an error message.</br></br>  <strong>Available Request Headers</strong></br> <table>   <tr>     <th align=left>key</th>     <th align=left>Example Value</th>     <th align=left>Description</th>   </tr>   <tr>     <td>`api-key`</td>     <td>api-key-provided-by-emass</td>     <td>This API key must be provided in the request header for all endpoint calls</td>   </tr>   <tr>     <td>`user-uid`</td>     <td>USER.UID.KEY</td>     <td>This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls</td>   </tr>   <tr>     <td></td><td></td>     <td>       Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC     </td>   </tr> </table>  </br><strong>Approve API Client for Actionable Requests</strong></br> Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records.  To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: 
 
-The version of the OpenAPI document: v3.4
+The version of the OpenAPI document: v3.9
 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 6.1.1-SNAPSHOT
+OpenAPI Generator version: 7.0.0-SNAPSHOT
 
 =end
 

data/lib/emass_client/models/cmmc_get.rb

@@ -3,10 +3,10 @@
 
 #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records.   <strong>Register External Application (that use the eMASS API)</strong></br> New users will need to [register](https://nisp.emass.apps.mil/Content/Help/jobaids/eMASS_OT_NewUser_Job_Aid.pdf) an API key with the eMASS development team prior to accessing the site for the first time. The eMASS REST API  requires a client certificate (SSL/TLS, DoD PKI only). Use the `Registration` endpoint to register the client certificate.</br></br>  Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key.  The API key must be provided in the request header for all endpoint calls (api-key). If the service receives an untrusted certificate or API key, a 401 error response code will be returned along with an error message.</br></br>  <strong>Available Request Headers</strong></br> <table>   <tr>     <th align=left>key</th>     <th align=left>Example Value</th>     <th align=left>Description</th>   </tr>   <tr>     <td>`api-key`</td>     <td>api-key-provided-by-emass</td>     <td>This API key must be provided in the request header for all endpoint calls</td>   </tr>   <tr>     <td>`user-uid`</td>     <td>USER.UID.KEY</td>     <td>This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls</td>   </tr>   <tr>     <td></td><td></td>     <td>       Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC     </td>   </tr> </table>  </br><strong>Approve API Client for Actionable Requests</strong></br> Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records.  To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: 
 
-The version of the OpenAPI document: v3.4
+The version of the OpenAPI document: v3.9
 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 6.1.1-SNAPSHOT
+OpenAPI Generator version: 7.0.0-SNAPSHOT
 
 =end
 
@@ -21,14 +21,11 @@ module EmassClient
     # [Read-Only] The name of the DIB Company.
     attr_accessor :hq_organization_name
 
-    # [Read-Only] The Data Universal Numbering System (DUNS) number.
-    attr_accessor :duns
-
     # [Read-Only] The Unique Entity Identifier assigned to the DIB Company.
-    attr_accessor :unique_entity_identifier
+    attr_accessor :uei
 
     # [Read-Only] The five position code(s) associated with the Organization Seeking Certification (OSC).
-    attr_accessor :cage_codes
+    attr_accessor :cage_codes_in_scope
 
     # [Read-Only] The name of the Organization Seeking Certification.
     attr_accessor :osc_name
@@ -46,11 +43,35 @@ module EmassClient
     attr_accessor :expiration_date
 
     # [Read-Only] Unique identifier for the assessment/certificate.
-    attr_accessor :certificate_id
+    attr_accessor :assessment_id
 
     # [Read-Only] Version of the CMMC Model used as part of the assessment.
     attr_accessor :model_version
 
+    # [Read-Only] Identifies the highest-level CAGE Code associated with a given organization.
+    attr_accessor :highest_level_cage_code
+
+    # [Read-Only] Identifies the unique ID that is associated with a given CMMC certification for an organization.
+    attr_accessor :certification_unique_id
+
+    # [Read-Only] Identifies whether any security requirements received a POA&M during the assessment.
+    attr_accessor :poam
+
+    # [Read-Only] Identifies the overall calculated score for the assessment based on the assigned values to each applicable security requirement.
+    attr_accessor :overall_score
+
+    # [Read-Only] Last name of the company official contracting with the C3PAO for the assessment.
+    attr_accessor :osc_assessment_official_last_name
+
+    # [Read-Only] First name of the company official contracting with the C3PAO for the assessment.
+    attr_accessor :osc_assessment_official_first_name
+
+    # [Read-Only] Email of the company official contracting with the C3PAO for the assessment.
+    attr_accessor :osc_assessment_official_email
+
+    # [Read-Only] Title of the company official contracting with the C3PAO for the assessment.
+    attr_accessor :osc_assessment_official_title
+
     attr_accessor :ssps
 
     class EnumAttributeValidator
@@ -80,16 +101,23 @@ module EmassClient
       {
         :'operation' => :'operation',
         :'hq_organization_name' => :'hqOrganizationName',
-        :'duns' => :'duns',
-        :'unique_entity_identifier' => :'uniqueEntityIdentifier',
-        :'cage_codes' => :'cageCodes',
+        :'uei' => :'uei',
+        :'cage_codes_in_scope' => :'cageCodesInScope',
         :'osc_name' => :'oscName',
         :'scope' => :'scope',
         :'scope_description' => :'scopeDescription',
         :'awarded_cmmc_level' => :'awardedCMMCLevel',
         :'expiration_date' => :'expirationDate',
-        :'certificate_id' => :'certificateId',
+        :'assessment_id' => :'assessmentId',
         :'model_version' => :'modelVersion',
+        :'highest_level_cage_code' => :'highestLevelCageCode',
+        :'certification_unique_id' => :'certificationUniqueId',
+        :'poam' => :'poam',
+        :'overall_score' => :'overallScore',
+        :'osc_assessment_official_last_name' => :'oscAssessmentOfficialLastName',
+        :'osc_assessment_official_first_name' => :'oscAssessmentOfficialFirstName',
+        :'osc_assessment_official_email' => :'oscAssessmentOfficialEmail',
+        :'osc_assessment_official_title' => :'oscAssessmentOfficialTitle',
         :'ssps' => :'ssps'
       }
     end
@@ -104,16 +132,23 @@ module EmassClient
       {
         :'operation' => :'String',
         :'hq_organization_name' => :'String',
-        :'duns' => :'String',
-        :'unique_entity_identifier' => :'String',
-        :'cage_codes' => :'String',
+        :'uei' => :'String',
+        :'cage_codes_in_scope' => :'String',
         :'osc_name' => :'String',
         :'scope' => :'String',
         :'scope_description' => :'String',
         :'awarded_cmmc_level' => :'String',
         :'expiration_date' => :'Integer',
-        :'certificate_id' => :'String',
+        :'assessment_id' => :'String',
         :'model_version' => :'String',
+        :'highest_level_cage_code' => :'String',
+        :'certification_unique_id' => :'String',
+        :'poam' => :'Boolean',
+        :'overall_score' => :'Integer',
+        :'osc_assessment_official_last_name' => :'String',
+        :'osc_assessment_official_first_name' => :'String',
+        :'osc_assessment_official_email' => :'String',
+        :'osc_assessment_official_title' => :'String',
         :'ssps' => :'Array<Ssps>'
       }
     end
@@ -123,16 +158,22 @@ module EmassClient
       Set.new([
         :'operation',
         :'hq_organization_name',
-        :'duns',
-        :'unique_entity_identifier',
-        :'cage_codes',
+        :'uei',
+        :'cage_codes_in_scope',
         :'osc_name',
         :'scope',
         :'scope_description',
         :'awarded_cmmc_level',
         :'expiration_date',
-        :'certificate_id',
+        :'assessment_id',
         :'model_version',
+        :'highest_level_cage_code',
+        :'certification_unique_id',
+        :'poam',
+        :'osc_assessment_official_last_name',
+        :'osc_assessment_official_first_name',
+        :'osc_assessment_official_email',
+        :'osc_assessment_official_title',
         :'ssps'
       ])
     end
@@ -160,16 +201,12 @@ module EmassClient
         self.hq_organization_name = attributes[:'hq_organization_name']
       end
 
-      if attributes.key?(:'duns')
-        self.duns = attributes[:'duns']
-      end
-
-      if attributes.key?(:'unique_entity_identifier')
-        self.unique_entity_identifier = attributes[:'unique_entity_identifier']
+      if attributes.key?(:'uei')
+        self.uei = attributes[:'uei']
       end
 
-      if attributes.key?(:'cage_codes')
-        self.cage_codes = attributes[:'cage_codes']
+      if attributes.key?(:'cage_codes_in_scope')
+        self.cage_codes_in_scope = attributes[:'cage_codes_in_scope']
       end
 
       if attributes.key?(:'osc_name')
@@ -192,14 +229,46 @@ module EmassClient
         self.expiration_date = attributes[:'expiration_date']
       end
 
-      if attributes.key?(:'certificate_id')
-        self.certificate_id = attributes[:'certificate_id']
+      if attributes.key?(:'assessment_id')
+        self.assessment_id = attributes[:'assessment_id']
       end
 
       if attributes.key?(:'model_version')
         self.model_version = attributes[:'model_version']
       end
 
+      if attributes.key?(:'highest_level_cage_code')
+        self.highest_level_cage_code = attributes[:'highest_level_cage_code']
+      end
+
+      if attributes.key?(:'certification_unique_id')
+        self.certification_unique_id = attributes[:'certification_unique_id']
+      end
+
+      if attributes.key?(:'poam')
+        self.poam = attributes[:'poam']
+      end
+
+      if attributes.key?(:'overall_score')
+        self.overall_score = attributes[:'overall_score']
+      end
+
+      if attributes.key?(:'osc_assessment_official_last_name')
+        self.osc_assessment_official_last_name = attributes[:'osc_assessment_official_last_name']
+      end
+
+      if attributes.key?(:'osc_assessment_official_first_name')
+        self.osc_assessment_official_first_name = attributes[:'osc_assessment_official_first_name']
+      end
+
+      if attributes.key?(:'osc_assessment_official_email')
+        self.osc_assessment_official_email = attributes[:'osc_assessment_official_email']
+      end
+
+      if attributes.key?(:'osc_assessment_official_title')
+        self.osc_assessment_official_title = attributes[:'osc_assessment_official_title']
+      end
+
       if attributes.key?(:'ssps')
         if (value = attributes[:'ssps']).is_a?(Array)
           self.ssps = value
@@ -239,16 +308,23 @@ module EmassClient
       self.class == o.class &&
           operation == o.operation &&
           hq_organization_name == o.hq_organization_name &&
-          duns == o.duns &&
-          unique_entity_identifier == o.unique_entity_identifier &&
-          cage_codes == o.cage_codes &&
+          uei == o.uei &&
+          cage_codes_in_scope == o.cage_codes_in_scope &&
           osc_name == o.osc_name &&
           scope == o.scope &&
           scope_description == o.scope_description &&
           awarded_cmmc_level == o.awarded_cmmc_level &&
           expiration_date == o.expiration_date &&
-          certificate_id == o.certificate_id &&
+          assessment_id == o.assessment_id &&
           model_version == o.model_version &&
+          highest_level_cage_code == o.highest_level_cage_code &&
+          certification_unique_id == o.certification_unique_id &&
+          poam == o.poam &&
+          overall_score == o.overall_score &&
+          osc_assessment_official_last_name == o.osc_assessment_official_last_name &&
+          osc_assessment_official_first_name == o.osc_assessment_official_first_name &&
+          osc_assessment_official_email == o.osc_assessment_official_email &&
+          osc_assessment_official_title == o.osc_assessment_official_title &&
           ssps == o.ssps
     end
 
@@ -261,7 +337,7 @@ module EmassClient
     # Calculates hash code according to all attributes.
     # @return [Integer] Hash code
     def hash
-      [operation, hq_organization_name, duns, unique_entity_identifier, cage_codes, osc_name, scope, scope_description, awarded_cmmc_level, expiration_date, certificate_id, model_version, ssps].hash
+      [operation, hq_organization_name, uei, cage_codes_in_scope, osc_name, scope, scope_description, awarded_cmmc_level, expiration_date, assessment_id, model_version, highest_level_cage_code, certification_unique_id, poam, overall_score, osc_assessment_official_last_name, osc_assessment_official_first_name, osc_assessment_official_email, osc_assessment_official_title, ssps].hash
     end
 
     # Builds the object from hash

data/lib/emass_client/models/cmmc_response_get.rb

@@ -3,10 +3,10 @@
 
 #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records.   <strong>Register External Application (that use the eMASS API)</strong></br> New users will need to [register](https://nisp.emass.apps.mil/Content/Help/jobaids/eMASS_OT_NewUser_Job_Aid.pdf) an API key with the eMASS development team prior to accessing the site for the first time. The eMASS REST API  requires a client certificate (SSL/TLS, DoD PKI only). Use the `Registration` endpoint to register the client certificate.</br></br>  Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key.  The API key must be provided in the request header for all endpoint calls (api-key). If the service receives an untrusted certificate or API key, a 401 error response code will be returned along with an error message.</br></br>  <strong>Available Request Headers</strong></br> <table>   <tr>     <th align=left>key</th>     <th align=left>Example Value</th>     <th align=left>Description</th>   </tr>   <tr>     <td>`api-key`</td>     <td>api-key-provided-by-emass</td>     <td>This API key must be provided in the request header for all endpoint calls</td>   </tr>   <tr>     <td>`user-uid`</td>     <td>USER.UID.KEY</td>     <td>This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls</td>   </tr>   <tr>     <td></td><td></td>     <td>       Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC     </td>   </tr> </table>  </br><strong>Approve API Client for Actionable Requests</strong></br> Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records.  To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: 
 
-The version of the OpenAPI document: v3.4
+The version of the OpenAPI document: v3.9
 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 6.1.1-SNAPSHOT
+OpenAPI Generator version: 7.0.0-SNAPSHOT
 
 =end
 

data/lib/emass_client/models/connectivity_ccsd.rb

@@ -3,10 +3,10 @@
 
 #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records.   <strong>Register External Application (that use the eMASS API)</strong></br> New users will need to [register](https://nisp.emass.apps.mil/Content/Help/jobaids/eMASS_OT_NewUser_Job_Aid.pdf) an API key with the eMASS development team prior to accessing the site for the first time. The eMASS REST API  requires a client certificate (SSL/TLS, DoD PKI only). Use the `Registration` endpoint to register the client certificate.</br></br>  Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key.  The API key must be provided in the request header for all endpoint calls (api-key). If the service receives an untrusted certificate or API key, a 401 error response code will be returned along with an error message.</br></br>  <strong>Available Request Headers</strong></br> <table>   <tr>     <th align=left>key</th>     <th align=left>Example Value</th>     <th align=left>Description</th>   </tr>   <tr>     <td>`api-key`</td>     <td>api-key-provided-by-emass</td>     <td>This API key must be provided in the request header for all endpoint calls</td>   </tr>   <tr>     <td>`user-uid`</td>     <td>USER.UID.KEY</td>     <td>This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls</td>   </tr>   <tr>     <td></td><td></td>     <td>       Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC     </td>   </tr> </table>  </br><strong>Approve API Client for Actionable Requests</strong></br> Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records.  To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: 
 
-The version of the OpenAPI document: v3.4
+The version of the OpenAPI document: v3.9
 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 6.1.1-SNAPSHOT
+OpenAPI Generator version: 7.0.0-SNAPSHOT
 
 =end
 

data/lib/emass_client/models/containers_resources_post.rb

@@ -3,10 +3,10 @@
 
 #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records.   <strong>Register External Application (that use the eMASS API)</strong></br> New users will need to [register](https://nisp.emass.apps.mil/Content/Help/jobaids/eMASS_OT_NewUser_Job_Aid.pdf) an API key with the eMASS development team prior to accessing the site for the first time. The eMASS REST API  requires a client certificate (SSL/TLS, DoD PKI only). Use the `Registration` endpoint to register the client certificate.</br></br>  Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key.  The API key must be provided in the request header for all endpoint calls (api-key). If the service receives an untrusted certificate or API key, a 401 error response code will be returned along with an error message.</br></br>  <strong>Available Request Headers</strong></br> <table>   <tr>     <th align=left>key</th>     <th align=left>Example Value</th>     <th align=left>Description</th>   </tr>   <tr>     <td>`api-key`</td>     <td>api-key-provided-by-emass</td>     <td>This API key must be provided in the request header for all endpoint calls</td>   </tr>   <tr>     <td>`user-uid`</td>     <td>USER.UID.KEY</td>     <td>This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls</td>   </tr>   <tr>     <td></td><td></td>     <td>       Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC     </td>   </tr> </table>  </br><strong>Approve API Client for Actionable Requests</strong></br> Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records.  To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: 
 
-The version of the OpenAPI document: v3.4
+The version of the OpenAPI document: v3.9
 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 6.1.1-SNAPSHOT
+OpenAPI Generator version: 7.0.0-SNAPSHOT
 
 =end
 

data/lib/emass_client/models/containers_response_post.rb

@@ -3,10 +3,10 @@
 
 #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records.   <strong>Register External Application (that use the eMASS API)</strong></br> New users will need to [register](https://nisp.emass.apps.mil/Content/Help/jobaids/eMASS_OT_NewUser_Job_Aid.pdf) an API key with the eMASS development team prior to accessing the site for the first time. The eMASS REST API  requires a client certificate (SSL/TLS, DoD PKI only). Use the `Registration` endpoint to register the client certificate.</br></br>  Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key.  The API key must be provided in the request header for all endpoint calls (api-key). If the service receives an untrusted certificate or API key, a 401 error response code will be returned along with an error message.</br></br>  <strong>Available Request Headers</strong></br> <table>   <tr>     <th align=left>key</th>     <th align=left>Example Value</th>     <th align=left>Description</th>   </tr>   <tr>     <td>`api-key`</td>     <td>api-key-provided-by-emass</td>     <td>This API key must be provided in the request header for all endpoint calls</td>   </tr>   <tr>     <td>`user-uid`</td>     <td>USER.UID.KEY</td>     <td>This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls</td>   </tr>   <tr>     <td></td><td></td>     <td>       Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC     </td>   </tr> </table>  </br><strong>Approve API Client for Actionable Requests</strong></br> Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records.  To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: 
 
-The version of the OpenAPI document: v3.4
+The version of the OpenAPI document: v3.9
 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 6.1.1-SNAPSHOT
+OpenAPI Generator version: 7.0.0-SNAPSHOT
 
 =end
 

data/lib/emass_client/models/controls_get.rb

@@ -3,10 +3,10 @@
 
 #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records.   <strong>Register External Application (that use the eMASS API)</strong></br> New users will need to [register](https://nisp.emass.apps.mil/Content/Help/jobaids/eMASS_OT_NewUser_Job_Aid.pdf) an API key with the eMASS development team prior to accessing the site for the first time. The eMASS REST API  requires a client certificate (SSL/TLS, DoD PKI only). Use the `Registration` endpoint to register the client certificate.</br></br>  Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key.  The API key must be provided in the request header for all endpoint calls (api-key). If the service receives an untrusted certificate or API key, a 401 error response code will be returned along with an error message.</br></br>  <strong>Available Request Headers</strong></br> <table>   <tr>     <th align=left>key</th>     <th align=left>Example Value</th>     <th align=left>Description</th>   </tr>   <tr>     <td>`api-key`</td>     <td>api-key-provided-by-emass</td>     <td>This API key must be provided in the request header for all endpoint calls</td>   </tr>   <tr>     <td>`user-uid`</td>     <td>USER.UID.KEY</td>     <td>This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls</td>   </tr>   <tr>     <td></td><td></td>     <td>       Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC     </td>   </tr> </table>  </br><strong>Approve API Client for Actionable Requests</strong></br> Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records.  To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: 
 
-The version of the OpenAPI document: v3.4
+The version of the OpenAPI document: v3.9
 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 6.1.1-SNAPSHOT
+OpenAPI Generator version: 7.0.0-SNAPSHOT
 
 =end
 

data/lib/emass_client/models/controls_put.rb

@@ -3,10 +3,10 @@
 
 #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records.   <strong>Register External Application (that use the eMASS API)</strong></br> New users will need to [register](https://nisp.emass.apps.mil/Content/Help/jobaids/eMASS_OT_NewUser_Job_Aid.pdf) an API key with the eMASS development team prior to accessing the site for the first time. The eMASS REST API  requires a client certificate (SSL/TLS, DoD PKI only). Use the `Registration` endpoint to register the client certificate.</br></br>  Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key.  The API key must be provided in the request header for all endpoint calls (api-key). If the service receives an untrusted certificate or API key, a 401 error response code will be returned along with an error message.</br></br>  <strong>Available Request Headers</strong></br> <table>   <tr>     <th align=left>key</th>     <th align=left>Example Value</th>     <th align=left>Description</th>   </tr>   <tr>     <td>`api-key`</td>     <td>api-key-provided-by-emass</td>     <td>This API key must be provided in the request header for all endpoint calls</td>   </tr>   <tr>     <td>`user-uid`</td>     <td>USER.UID.KEY</td>     <td>This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls</td>   </tr>   <tr>     <td></td><td></td>     <td>       Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC     </td>   </tr> </table>  </br><strong>Approve API Client for Actionable Requests</strong></br> Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records.  To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: 
 
-The version of the OpenAPI document: v3.4
+The version of the OpenAPI document: v3.9
 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 6.1.1-SNAPSHOT
+OpenAPI Generator version: 7.0.0-SNAPSHOT
 
 =end
 

data/lib/emass_client/models/controls_response_get.rb

@@ -3,10 +3,10 @@
 
 #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records.   <strong>Register External Application (that use the eMASS API)</strong></br> New users will need to [register](https://nisp.emass.apps.mil/Content/Help/jobaids/eMASS_OT_NewUser_Job_Aid.pdf) an API key with the eMASS development team prior to accessing the site for the first time. The eMASS REST API  requires a client certificate (SSL/TLS, DoD PKI only). Use the `Registration` endpoint to register the client certificate.</br></br>  Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key.  The API key must be provided in the request header for all endpoint calls (api-key). If the service receives an untrusted certificate or API key, a 401 error response code will be returned along with an error message.</br></br>  <strong>Available Request Headers</strong></br> <table>   <tr>     <th align=left>key</th>     <th align=left>Example Value</th>     <th align=left>Description</th>   </tr>   <tr>     <td>`api-key`</td>     <td>api-key-provided-by-emass</td>     <td>This API key must be provided in the request header for all endpoint calls</td>   </tr>   <tr>     <td>`user-uid`</td>     <td>USER.UID.KEY</td>     <td>This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls</td>   </tr>   <tr>     <td></td><td></td>     <td>       Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC     </td>   </tr> </table>  </br><strong>Approve API Client for Actionable Requests</strong></br> Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records.  To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: 
 
-The version of the OpenAPI document: v3.4
+The version of the OpenAPI document: v3.9
 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 6.1.1-SNAPSHOT
+OpenAPI Generator version: 7.0.0-SNAPSHOT
 
 =end
 

data/lib/emass_client/models/controls_response_put.rb

@@ -3,10 +3,10 @@
 
 #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records.   <strong>Register External Application (that use the eMASS API)</strong></br> New users will need to [register](https://nisp.emass.apps.mil/Content/Help/jobaids/eMASS_OT_NewUser_Job_Aid.pdf) an API key with the eMASS development team prior to accessing the site for the first time. The eMASS REST API  requires a client certificate (SSL/TLS, DoD PKI only). Use the `Registration` endpoint to register the client certificate.</br></br>  Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key.  The API key must be provided in the request header for all endpoint calls (api-key). If the service receives an untrusted certificate or API key, a 401 error response code will be returned along with an error message.</br></br>  <strong>Available Request Headers</strong></br> <table>   <tr>     <th align=left>key</th>     <th align=left>Example Value</th>     <th align=left>Description</th>   </tr>   <tr>     <td>`api-key`</td>     <td>api-key-provided-by-emass</td>     <td>This API key must be provided in the request header for all endpoint calls</td>   </tr>   <tr>     <td>`user-uid`</td>     <td>USER.UID.KEY</td>     <td>This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls</td>   </tr>   <tr>     <td></td><td></td>     <td>       Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC     </td>   </tr> </table>  </br><strong>Approve API Client for Actionable Requests</strong></br> Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records.  To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: 
 
-The version of the OpenAPI document: v3.4
+The version of the OpenAPI document: v3.9
 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 6.1.1-SNAPSHOT
+OpenAPI Generator version: 7.0.0-SNAPSHOT
 
 =end
 

data/lib/emass_client/models/definition_transitions.rb

@@ -3,10 +3,10 @@
 
 #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records.   <strong>Register External Application (that use the eMASS API)</strong></br> New users will need to [register](https://nisp.emass.apps.mil/Content/Help/jobaids/eMASS_OT_NewUser_Job_Aid.pdf) an API key with the eMASS development team prior to accessing the site for the first time. The eMASS REST API  requires a client certificate (SSL/TLS, DoD PKI only). Use the `Registration` endpoint to register the client certificate.</br></br>  Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key.  The API key must be provided in the request header for all endpoint calls (api-key). If the service receives an untrusted certificate or API key, a 401 error response code will be returned along with an error message.</br></br>  <strong>Available Request Headers</strong></br> <table>   <tr>     <th align=left>key</th>     <th align=left>Example Value</th>     <th align=left>Description</th>   </tr>   <tr>     <td>`api-key`</td>     <td>api-key-provided-by-emass</td>     <td>This API key must be provided in the request header for all endpoint calls</td>   </tr>   <tr>     <td>`user-uid`</td>     <td>USER.UID.KEY</td>     <td>This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls</td>   </tr>   <tr>     <td></td><td></td>     <td>       Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC     </td>   </tr> </table>  </br><strong>Approve API Client for Actionable Requests</strong></br> Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records.  To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: 
 
-The version of the OpenAPI document: v3.4
+The version of the OpenAPI document: v3.9
 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 6.1.1-SNAPSHOT
+OpenAPI Generator version: 7.0.0-SNAPSHOT
 
 =end