emass_client 3.4.1 → 3.9.1

Sign up to get free protection for your applications and to get access to all the features.
Files changed (124) hide show
  1. checksums.yaml +4 -4
  2. data/README.md +23 -11
  3. data/lib/emass_client/api/artifacts_api.rb +7 -4
  4. data/lib/emass_client/api/artifacts_export_api.rb +2 -2
  5. data/lib/emass_client/api/cac_api.rb +2 -2
  6. data/lib/emass_client/api/{cloud_resources_api.rb → cloud_resource_results_api.rb} +8 -8
  7. data/lib/emass_client/api/cmmc_assessments_api.rb +2 -2
  8. data/lib/emass_client/api/{containers_api.rb → container_scan_results_api.rb} +8 -8
  9. data/lib/emass_client/api/controls_api.rb +2 -2
  10. data/lib/emass_client/api/dashboards_api.rb +868 -90
  11. data/lib/emass_client/api/milestones_api.rb +2 -2
  12. data/lib/emass_client/api/pac_api.rb +2 -2
  13. data/lib/emass_client/api/poam_api.rb +2 -2
  14. data/lib/emass_client/api/registration_api.rb +2 -2
  15. data/lib/emass_client/api/static_code_scans_api.rb +2 -2
  16. data/lib/emass_client/api/system_roles_api.rb +2 -2
  17. data/lib/emass_client/api/systems_api.rb +2 -2
  18. data/lib/emass_client/api/test_api.rb +2 -2
  19. data/lib/emass_client/api/test_results_api.rb +2 -2
  20. data/lib/emass_client/api/workflow_definitions_api.rb +2 -2
  21. data/lib/emass_client/api/workflow_instances_api.rb +2 -2
  22. data/lib/emass_client/api_client.rb +2 -2
  23. data/lib/emass_client/api_error.rb +3 -2
  24. data/lib/emass_client/configuration.rb +8 -8
  25. data/lib/emass_client/models/artifacts_get.rb +44 -68
  26. data/lib/emass_client/models/artifacts_request_delete_body_inner.rb +2 -2
  27. data/lib/emass_client/models/artifacts_response_del.rb +2 -2
  28. data/lib/emass_client/models/artifacts_response_del_data_inner.rb +2 -2
  29. data/lib/emass_client/models/artifacts_response_get.rb +2 -2
  30. data/lib/emass_client/models/artifacts_response_put_post.rb +2 -2
  31. data/lib/emass_client/models/artifacts_response_put_post_data_inner.rb +2 -2
  32. data/lib/emass_client/models/cac_get.rb +2 -2
  33. data/lib/emass_client/models/cac_response_get.rb +2 -2
  34. data/lib/emass_client/models/cac_response_post.rb +2 -2
  35. data/lib/emass_client/models/cac_response_post_data_inner.rb +2 -2
  36. data/lib/emass_client/models/cloud_resources_post.rb +2 -2
  37. data/lib/emass_client/models/cloud_resources_response_post.rb +2 -2
  38. data/lib/emass_client/models/cmmc_get.rb +111 -35
  39. data/lib/emass_client/models/cmmc_response_get.rb +2 -2
  40. data/lib/emass_client/models/connectivity_ccsd.rb +2 -2
  41. data/lib/emass_client/models/containers_resources_post.rb +2 -2
  42. data/lib/emass_client/models/containers_response_post.rb +2 -2
  43. data/lib/emass_client/models/controls_get.rb +2 -2
  44. data/lib/emass_client/models/controls_put.rb +2 -2
  45. data/lib/emass_client/models/controls_response_get.rb +2 -2
  46. data/lib/emass_client/models/controls_response_put.rb +2 -2
  47. data/lib/emass_client/models/definition_transitions.rb +2 -2
  48. data/lib/emass_client/models/instances_transitions.rb +2 -2
  49. data/lib/emass_client/models/milestone_response_get.rb +2 -2
  50. data/lib/emass_client/models/milestone_response_get_milestone.rb +2 -2
  51. data/lib/emass_client/models/milestone_response_post.rb +2 -2
  52. data/lib/emass_client/models/milestone_response_put.rb +2 -2
  53. data/lib/emass_client/models/milestones_get.rb +2 -2
  54. data/lib/emass_client/models/milestones_put_post_delete.rb +2 -2
  55. data/lib/emass_client/models/milestones_request_delete_body_inner.rb +2 -2
  56. data/lib/emass_client/models/milestones_required_post.rb +2 -2
  57. data/lib/emass_client/models/milestones_required_put.rb +2 -2
  58. data/lib/emass_client/models/pac_get.rb +2 -2
  59. data/lib/emass_client/models/pac_post.rb +2 -2
  60. data/lib/emass_client/models/pac_response_get.rb +2 -2
  61. data/lib/emass_client/models/pac_response_post.rb +2 -2
  62. data/lib/emass_client/models/poam_get.rb +2 -2
  63. data/lib/emass_client/models/poam_post_put_del.rb +2 -2
  64. data/lib/emass_client/models/poam_request_delete_body_inner.rb +2 -2
  65. data/lib/emass_client/models/poam_response_delete.rb +2 -2
  66. data/lib/emass_client/models/poam_response_get_poams.rb +2 -2
  67. data/lib/emass_client/models/poam_response_get_systems.rb +2 -2
  68. data/lib/emass_client/models/poam_response_post.rb +2 -2
  69. data/lib/emass_client/models/poam_response_put.rb +2 -2
  70. data/lib/emass_client/models/register.rb +2 -2
  71. data/lib/emass_client/models/register_data.rb +2 -2
  72. data/lib/emass_client/models/register_user_request_post_body.rb +2 -2
  73. data/lib/emass_client/models/response200.rb +2 -2
  74. data/lib/emass_client/models/response201.rb +2 -2
  75. data/lib/emass_client/models/response201_meta.rb +2 -2
  76. data/lib/emass_client/models/response400.rb +2 -2
  77. data/lib/emass_client/models/response400_meta.rb +2 -2
  78. data/lib/emass_client/models/response401.rb +2 -2
  79. data/lib/emass_client/models/response401_meta.rb +2 -2
  80. data/lib/emass_client/models/response403.rb +2 -2
  81. data/lib/emass_client/models/response403_meta.rb +2 -2
  82. data/lib/emass_client/models/response404.rb +2 -2
  83. data/lib/emass_client/models/response405.rb +2 -2
  84. data/lib/emass_client/models/response405_meta.rb +2 -2
  85. data/lib/emass_client/models/response411.rb +2 -2
  86. data/lib/emass_client/models/response411_meta.rb +2 -2
  87. data/lib/emass_client/models/response490.rb +2 -2
  88. data/lib/emass_client/models/response490_meta.rb +2 -2
  89. data/lib/emass_client/models/response500.rb +2 -2
  90. data/lib/emass_client/models/response500_meta.rb +2 -2
  91. data/lib/emass_client/models/role_category.rb +2 -2
  92. data/lib/emass_client/models/roles.rb +2 -2
  93. data/lib/emass_client/models/ssps.rb +2 -2
  94. data/lib/emass_client/models/stage.rb +2 -2
  95. data/lib/emass_client/models/static_code_application.rb +2 -2
  96. data/lib/emass_client/models/static_code_post.rb +2 -2
  97. data/lib/emass_client/models/static_code_request_post_body.rb +2 -2
  98. data/lib/emass_client/models/static_code_request_post_body_application.rb +2 -2
  99. data/lib/emass_client/models/static_code_response_post.rb +2 -2
  100. data/lib/emass_client/models/success200_response.rb +2 -2
  101. data/lib/emass_client/models/success200_response_data_inner.rb +2 -2
  102. data/lib/emass_client/models/system_response.rb +2 -2
  103. data/lib/emass_client/models/system_roles_category_response.rb +2 -2
  104. data/lib/emass_client/models/system_roles_response.rb +2 -2
  105. data/lib/emass_client/models/system_roles_response_data_inner.rb +2 -2
  106. data/lib/emass_client/models/systems.rb +399 -71
  107. data/lib/emass_client/models/systems_response.rb +2 -2
  108. data/lib/emass_client/models/test.rb +2 -2
  109. data/lib/emass_client/models/test_data.rb +2 -2
  110. data/lib/emass_client/models/test_results_get.rb +2 -2
  111. data/lib/emass_client/models/test_results_post.rb +2 -2
  112. data/lib/emass_client/models/test_results_response_get.rb +2 -2
  113. data/lib/emass_client/models/test_results_response_post.rb +2 -2
  114. data/lib/emass_client/models/users.rb +2 -2
  115. data/lib/emass_client/models/workflow_definition_get.rb +2 -2
  116. data/lib/emass_client/models/workflow_definition_response_get.rb +2 -2
  117. data/lib/emass_client/models/workflow_instance_get.rb +2 -2
  118. data/lib/emass_client/models/workflow_instance_response_get.rb +2 -2
  119. data/lib/emass_client/models/workflow_instances_get.rb +2 -2
  120. data/lib/emass_client/models/workflow_instances_response_get.rb +2 -2
  121. data/lib/emass_client/models/workflow_instances_response_get_pagination.rb +2 -2
  122. data/lib/emass_client/version.rb +3 -3
  123. data/lib/emass_client.rb +4 -4
  124. metadata +5 -5
@@ -3,10 +3,10 @@
3
3
 
4
4
  #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:
5
5
 
6
- The version of the OpenAPI document: v3.4
6
+ The version of the OpenAPI document: v3.9
7
7
  Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 6.2.1-SNAPSHOT
9
+ OpenAPI Generator version: 7.0.0-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -3,10 +3,10 @@
3
3
 
4
4
  #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:
5
5
 
6
- The version of the OpenAPI document: v3.4
6
+ The version of the OpenAPI document: v3.9
7
7
  Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 6.2.1-SNAPSHOT
9
+ OpenAPI Generator version: 7.0.0-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -3,10 +3,10 @@
3
3
 
4
4
  #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:
5
5
 
6
- The version of the OpenAPI document: v3.4
6
+ The version of the OpenAPI document: v3.9
7
7
  Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 6.2.1-SNAPSHOT
9
+ OpenAPI Generator version: 7.0.0-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -3,10 +3,10 @@
3
3
 
4
4
  #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:
5
5
 
6
- The version of the OpenAPI document: v3.4
6
+ The version of the OpenAPI document: v3.9
7
7
  Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 6.2.1-SNAPSHOT
9
+ OpenAPI Generator version: 7.0.0-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -3,10 +3,10 @@
3
3
 
4
4
  #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:
5
5
 
6
- The version of the OpenAPI document: v3.4
6
+ The version of the OpenAPI document: v3.9
7
7
  Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 6.2.1-SNAPSHOT
9
+ OpenAPI Generator version: 7.0.0-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -3,10 +3,10 @@
3
3
 
4
4
  #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:
5
5
 
6
- The version of the OpenAPI document: v3.4
6
+ The version of the OpenAPI document: v3.9
7
7
  Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 6.2.1-SNAPSHOT
9
+ OpenAPI Generator version: 7.0.0-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -3,10 +3,10 @@
3
3
 
4
4
  #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:
5
5
 
6
- The version of the OpenAPI document: v3.4
6
+ The version of the OpenAPI document: v3.9
7
7
  Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 6.2.1-SNAPSHOT
9
+ OpenAPI Generator version: 7.0.0-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -3,10 +3,10 @@
3
3
 
4
4
  #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:
5
5
 
6
- The version of the OpenAPI document: v3.4
6
+ The version of the OpenAPI document: v3.9
7
7
  Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 6.2.1-SNAPSHOT
9
+ OpenAPI Generator version: 7.0.0-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -21,14 +21,11 @@ module EmassClient
21
21
  # [Read-Only] The name of the DIB Company.
22
22
  attr_accessor :hq_organization_name
23
23
 
24
- # [Read-Only] The Data Universal Numbering System (DUNS) number.
25
- attr_accessor :duns
26
-
27
24
  # [Read-Only] The Unique Entity Identifier assigned to the DIB Company.
28
- attr_accessor :unique_entity_identifier
25
+ attr_accessor :uei
29
26
 
30
27
  # [Read-Only] The five position code(s) associated with the Organization Seeking Certification (OSC).
31
- attr_accessor :cage_codes
28
+ attr_accessor :cage_codes_in_scope
32
29
 
33
30
  # [Read-Only] The name of the Organization Seeking Certification.
34
31
  attr_accessor :osc_name
@@ -46,11 +43,35 @@ module EmassClient
46
43
  attr_accessor :expiration_date
47
44
 
48
45
  # [Read-Only] Unique identifier for the assessment/certificate.
49
- attr_accessor :certificate_id
46
+ attr_accessor :assessment_id
50
47
 
51
48
  # [Read-Only] Version of the CMMC Model used as part of the assessment.
52
49
  attr_accessor :model_version
53
50
 
51
+ # [Read-Only] Identifies the highest-level CAGE Code associated with a given organization.
52
+ attr_accessor :highest_level_cage_code
53
+
54
+ # [Read-Only] Identifies the unique ID that is associated with a given CMMC certification for an organization.
55
+ attr_accessor :certification_unique_id
56
+
57
+ # [Read-Only] Identifies whether any security requirements received a POA&M during the assessment.
58
+ attr_accessor :poam
59
+
60
+ # [Read-Only] Identifies the overall calculated score for the assessment based on the assigned values to each applicable security requirement.
61
+ attr_accessor :overall_score
62
+
63
+ # [Read-Only] Last name of the company official contracting with the C3PAO for the assessment.
64
+ attr_accessor :osc_assessment_official_last_name
65
+
66
+ # [Read-Only] First name of the company official contracting with the C3PAO for the assessment.
67
+ attr_accessor :osc_assessment_official_first_name
68
+
69
+ # [Read-Only] Email of the company official contracting with the C3PAO for the assessment.
70
+ attr_accessor :osc_assessment_official_email
71
+
72
+ # [Read-Only] Title of the company official contracting with the C3PAO for the assessment.
73
+ attr_accessor :osc_assessment_official_title
74
+
54
75
  attr_accessor :ssps
55
76
 
56
77
  class EnumAttributeValidator
@@ -80,16 +101,23 @@ module EmassClient
80
101
  {
81
102
  :'operation' => :'operation',
82
103
  :'hq_organization_name' => :'hqOrganizationName',
83
- :'duns' => :'duns',
84
- :'unique_entity_identifier' => :'uniqueEntityIdentifier',
85
- :'cage_codes' => :'cageCodes',
104
+ :'uei' => :'uei',
105
+ :'cage_codes_in_scope' => :'cageCodesInScope',
86
106
  :'osc_name' => :'oscName',
87
107
  :'scope' => :'scope',
88
108
  :'scope_description' => :'scopeDescription',
89
109
  :'awarded_cmmc_level' => :'awardedCMMCLevel',
90
110
  :'expiration_date' => :'expirationDate',
91
- :'certificate_id' => :'certificateId',
111
+ :'assessment_id' => :'assessmentId',
92
112
  :'model_version' => :'modelVersion',
113
+ :'highest_level_cage_code' => :'highestLevelCageCode',
114
+ :'certification_unique_id' => :'certificationUniqueId',
115
+ :'poam' => :'poam',
116
+ :'overall_score' => :'overallScore',
117
+ :'osc_assessment_official_last_name' => :'oscAssessmentOfficialLastName',
118
+ :'osc_assessment_official_first_name' => :'oscAssessmentOfficialFirstName',
119
+ :'osc_assessment_official_email' => :'oscAssessmentOfficialEmail',
120
+ :'osc_assessment_official_title' => :'oscAssessmentOfficialTitle',
93
121
  :'ssps' => :'ssps'
94
122
  }
95
123
  end
@@ -104,16 +132,23 @@ module EmassClient
104
132
  {
105
133
  :'operation' => :'String',
106
134
  :'hq_organization_name' => :'String',
107
- :'duns' => :'String',
108
- :'unique_entity_identifier' => :'String',
109
- :'cage_codes' => :'String',
135
+ :'uei' => :'String',
136
+ :'cage_codes_in_scope' => :'String',
110
137
  :'osc_name' => :'String',
111
138
  :'scope' => :'String',
112
139
  :'scope_description' => :'String',
113
140
  :'awarded_cmmc_level' => :'String',
114
141
  :'expiration_date' => :'Integer',
115
- :'certificate_id' => :'String',
142
+ :'assessment_id' => :'String',
116
143
  :'model_version' => :'String',
144
+ :'highest_level_cage_code' => :'String',
145
+ :'certification_unique_id' => :'String',
146
+ :'poam' => :'Boolean',
147
+ :'overall_score' => :'Integer',
148
+ :'osc_assessment_official_last_name' => :'String',
149
+ :'osc_assessment_official_first_name' => :'String',
150
+ :'osc_assessment_official_email' => :'String',
151
+ :'osc_assessment_official_title' => :'String',
117
152
  :'ssps' => :'Array<Ssps>'
118
153
  }
119
154
  end
@@ -123,16 +158,22 @@ module EmassClient
123
158
  Set.new([
124
159
  :'operation',
125
160
  :'hq_organization_name',
126
- :'duns',
127
- :'unique_entity_identifier',
128
- :'cage_codes',
161
+ :'uei',
162
+ :'cage_codes_in_scope',
129
163
  :'osc_name',
130
164
  :'scope',
131
165
  :'scope_description',
132
166
  :'awarded_cmmc_level',
133
167
  :'expiration_date',
134
- :'certificate_id',
168
+ :'assessment_id',
135
169
  :'model_version',
170
+ :'highest_level_cage_code',
171
+ :'certification_unique_id',
172
+ :'poam',
173
+ :'osc_assessment_official_last_name',
174
+ :'osc_assessment_official_first_name',
175
+ :'osc_assessment_official_email',
176
+ :'osc_assessment_official_title',
136
177
  :'ssps'
137
178
  ])
138
179
  end
@@ -160,16 +201,12 @@ module EmassClient
160
201
  self.hq_organization_name = attributes[:'hq_organization_name']
161
202
  end
162
203
 
163
- if attributes.key?(:'duns')
164
- self.duns = attributes[:'duns']
165
- end
166
-
167
- if attributes.key?(:'unique_entity_identifier')
168
- self.unique_entity_identifier = attributes[:'unique_entity_identifier']
204
+ if attributes.key?(:'uei')
205
+ self.uei = attributes[:'uei']
169
206
  end
170
207
 
171
- if attributes.key?(:'cage_codes')
172
- self.cage_codes = attributes[:'cage_codes']
208
+ if attributes.key?(:'cage_codes_in_scope')
209
+ self.cage_codes_in_scope = attributes[:'cage_codes_in_scope']
173
210
  end
174
211
 
175
212
  if attributes.key?(:'osc_name')
@@ -192,14 +229,46 @@ module EmassClient
192
229
  self.expiration_date = attributes[:'expiration_date']
193
230
  end
194
231
 
195
- if attributes.key?(:'certificate_id')
196
- self.certificate_id = attributes[:'certificate_id']
232
+ if attributes.key?(:'assessment_id')
233
+ self.assessment_id = attributes[:'assessment_id']
197
234
  end
198
235
 
199
236
  if attributes.key?(:'model_version')
200
237
  self.model_version = attributes[:'model_version']
201
238
  end
202
239
 
240
+ if attributes.key?(:'highest_level_cage_code')
241
+ self.highest_level_cage_code = attributes[:'highest_level_cage_code']
242
+ end
243
+
244
+ if attributes.key?(:'certification_unique_id')
245
+ self.certification_unique_id = attributes[:'certification_unique_id']
246
+ end
247
+
248
+ if attributes.key?(:'poam')
249
+ self.poam = attributes[:'poam']
250
+ end
251
+
252
+ if attributes.key?(:'overall_score')
253
+ self.overall_score = attributes[:'overall_score']
254
+ end
255
+
256
+ if attributes.key?(:'osc_assessment_official_last_name')
257
+ self.osc_assessment_official_last_name = attributes[:'osc_assessment_official_last_name']
258
+ end
259
+
260
+ if attributes.key?(:'osc_assessment_official_first_name')
261
+ self.osc_assessment_official_first_name = attributes[:'osc_assessment_official_first_name']
262
+ end
263
+
264
+ if attributes.key?(:'osc_assessment_official_email')
265
+ self.osc_assessment_official_email = attributes[:'osc_assessment_official_email']
266
+ end
267
+
268
+ if attributes.key?(:'osc_assessment_official_title')
269
+ self.osc_assessment_official_title = attributes[:'osc_assessment_official_title']
270
+ end
271
+
203
272
  if attributes.key?(:'ssps')
204
273
  if (value = attributes[:'ssps']).is_a?(Array)
205
274
  self.ssps = value
@@ -239,16 +308,23 @@ module EmassClient
239
308
  self.class == o.class &&
240
309
  operation == o.operation &&
241
310
  hq_organization_name == o.hq_organization_name &&
242
- duns == o.duns &&
243
- unique_entity_identifier == o.unique_entity_identifier &&
244
- cage_codes == o.cage_codes &&
311
+ uei == o.uei &&
312
+ cage_codes_in_scope == o.cage_codes_in_scope &&
245
313
  osc_name == o.osc_name &&
246
314
  scope == o.scope &&
247
315
  scope_description == o.scope_description &&
248
316
  awarded_cmmc_level == o.awarded_cmmc_level &&
249
317
  expiration_date == o.expiration_date &&
250
- certificate_id == o.certificate_id &&
318
+ assessment_id == o.assessment_id &&
251
319
  model_version == o.model_version &&
320
+ highest_level_cage_code == o.highest_level_cage_code &&
321
+ certification_unique_id == o.certification_unique_id &&
322
+ poam == o.poam &&
323
+ overall_score == o.overall_score &&
324
+ osc_assessment_official_last_name == o.osc_assessment_official_last_name &&
325
+ osc_assessment_official_first_name == o.osc_assessment_official_first_name &&
326
+ osc_assessment_official_email == o.osc_assessment_official_email &&
327
+ osc_assessment_official_title == o.osc_assessment_official_title &&
252
328
  ssps == o.ssps
253
329
  end
254
330
 
@@ -261,7 +337,7 @@ module EmassClient
261
337
  # Calculates hash code according to all attributes.
262
338
  # @return [Integer] Hash code
263
339
  def hash
264
- [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
340
+ [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
265
341
  end
266
342
 
267
343
  # Builds the object from hash
@@ -3,10 +3,10 @@
3
3
 
4
4
  #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:
5
5
 
6
- The version of the OpenAPI document: v3.4
6
+ The version of the OpenAPI document: v3.9
7
7
  Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 6.2.1-SNAPSHOT
9
+ OpenAPI Generator version: 7.0.0-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -3,10 +3,10 @@
3
3
 
4
4
  #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:
5
5
 
6
- The version of the OpenAPI document: v3.4
6
+ The version of the OpenAPI document: v3.9
7
7
  Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 6.2.1-SNAPSHOT
9
+ OpenAPI Generator version: 7.0.0-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -3,10 +3,10 @@
3
3
 
4
4
  #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:
5
5
 
6
- The version of the OpenAPI document: v3.4
6
+ The version of the OpenAPI document: v3.9
7
7
  Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 6.2.1-SNAPSHOT
9
+ OpenAPI Generator version: 7.0.0-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -3,10 +3,10 @@
3
3
 
4
4
  #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:
5
5
 
6
- The version of the OpenAPI document: v3.4
6
+ The version of the OpenAPI document: v3.9
7
7
  Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 6.2.1-SNAPSHOT
9
+ OpenAPI Generator version: 7.0.0-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -3,10 +3,10 @@
3
3
 
4
4
  #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:
5
5
 
6
- The version of the OpenAPI document: v3.4
6
+ The version of the OpenAPI document: v3.9
7
7
  Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 6.2.1-SNAPSHOT
9
+ OpenAPI Generator version: 7.0.0-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -3,10 +3,10 @@
3
3
 
4
4
  #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:
5
5
 
6
- The version of the OpenAPI document: v3.4
6
+ The version of the OpenAPI document: v3.9
7
7
  Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 6.2.1-SNAPSHOT
9
+ OpenAPI Generator version: 7.0.0-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -3,10 +3,10 @@
3
3
 
4
4
  #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:
5
5
 
6
- The version of the OpenAPI document: v3.4
6
+ The version of the OpenAPI document: v3.9
7
7
  Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 6.2.1-SNAPSHOT
9
+ OpenAPI Generator version: 7.0.0-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -3,10 +3,10 @@
3
3
 
4
4
  #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:
5
5
 
6
- The version of the OpenAPI document: v3.4
6
+ The version of the OpenAPI document: v3.9
7
7
  Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 6.2.1-SNAPSHOT
9
+ OpenAPI Generator version: 7.0.0-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -3,10 +3,10 @@
3
3
 
4
4
  #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:
5
5
 
6
- The version of the OpenAPI document: v3.4
6
+ The version of the OpenAPI document: v3.9
7
7
  Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 6.2.1-SNAPSHOT
9
+ OpenAPI Generator version: 7.0.0-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -3,10 +3,10 @@
3
3
 
4
4
  #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:
5
5
 
6
- The version of the OpenAPI document: v3.4
6
+ The version of the OpenAPI document: v3.9
7
7
  Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 6.2.1-SNAPSHOT
9
+ OpenAPI Generator version: 7.0.0-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -3,10 +3,10 @@
3
3
 
4
4
  #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:
5
5
 
6
- The version of the OpenAPI document: v3.4
6
+ The version of the OpenAPI document: v3.9
7
7
  Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 6.2.1-SNAPSHOT
9
+ OpenAPI Generator version: 7.0.0-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -3,10 +3,10 @@
3
3
 
4
4
  #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:
5
5
 
6
- The version of the OpenAPI document: v3.4
6
+ The version of the OpenAPI document: v3.9
7
7
  Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 6.2.1-SNAPSHOT
9
+ OpenAPI Generator version: 7.0.0-SNAPSHOT
10
10
 
11
11
  =end
12
12