emass_client 3.9.1 → 3.9.10

Sign up to get free protection for your applications and to get access to all the features.
Files changed (127) hide show
  1. checksums.yaml +4 -4
  2. data/README.md +37 -31
  3. data/lib/emass_client/api/artifacts_api.rb +1 -1
  4. data/lib/emass_client/api/artifacts_export_api.rb +1 -1
  5. data/lib/emass_client/api/cac_api.rb +1 -1
  6. data/lib/emass_client/api/cloud_resource_results_api.rb +1 -1
  7. data/lib/emass_client/api/cmmc_assessments_api.rb +1 -1
  8. data/lib/emass_client/api/container_scan_results_api.rb +1 -1
  9. data/lib/emass_client/api/controls_api.rb +1 -1
  10. data/lib/emass_client/api/dashboards_api.rb +272 -53
  11. data/lib/emass_client/api/milestones_api.rb +1 -1
  12. data/lib/emass_client/api/pac_api.rb +1 -1
  13. data/lib/emass_client/api/poam_api.rb +1 -1
  14. data/lib/emass_client/api/registration_api.rb +1 -1
  15. data/lib/emass_client/api/static_code_scans_api.rb +1 -1
  16. data/lib/emass_client/api/system_roles_api.rb +1 -1
  17. data/lib/emass_client/api/systems_api.rb +1 -1
  18. data/lib/emass_client/api/test_api.rb +1 -1
  19. data/lib/emass_client/api/test_results_api.rb +1 -1
  20. data/lib/emass_client/api/workflow_definitions_api.rb +1 -1
  21. data/lib/emass_client/api/workflow_instances_api.rb +1 -1
  22. data/lib/emass_client/api_client.rb +1 -1
  23. data/lib/emass_client/api_error.rb +1 -1
  24. data/lib/emass_client/configuration.rb +1 -1
  25. data/lib/emass_client/models/artifacts_get.rb +1 -1
  26. data/lib/emass_client/models/artifacts_request_delete_body_inner.rb +1 -1
  27. data/lib/emass_client/models/artifacts_response_del.rb +1 -1
  28. data/lib/emass_client/models/artifacts_response_del_data_inner.rb +1 -1
  29. data/lib/emass_client/models/artifacts_response_get.rb +1 -1
  30. data/lib/emass_client/models/artifacts_response_put_post.rb +1 -1
  31. data/lib/emass_client/models/artifacts_response_put_post_data_inner.rb +1 -1
  32. data/lib/emass_client/models/cac_get.rb +1 -1
  33. data/lib/emass_client/models/cac_response_get.rb +1 -1
  34. data/lib/emass_client/models/cac_response_post.rb +1 -1
  35. data/lib/emass_client/models/cac_response_post_data_inner.rb +1 -1
  36. data/lib/emass_client/models/cloud_resources_post.rb +1 -1
  37. data/lib/emass_client/models/cloud_resources_response_post.rb +1 -1
  38. data/lib/emass_client/models/cmmc_get.rb +1 -1
  39. data/lib/emass_client/models/cmmc_response_get.rb +1 -1
  40. data/lib/emass_client/models/connectivity_ccsd.rb +1 -1
  41. data/lib/emass_client/models/containers_resources_post.rb +1 -1
  42. data/lib/emass_client/models/containers_response_post.rb +1 -1
  43. data/lib/emass_client/models/controls_get.rb +1 -1
  44. data/lib/emass_client/models/controls_put.rb +1 -1
  45. data/lib/emass_client/models/controls_response_get.rb +1 -1
  46. data/lib/emass_client/models/controls_response_put.rb +1 -1
  47. data/lib/emass_client/models/dashboard_mock_response.rb +239 -0
  48. data/lib/emass_client/models/dashboard_mock_response_pagination.rb +264 -0
  49. data/lib/emass_client/models/definition_transitions.rb +1 -1
  50. data/lib/emass_client/models/instances_transitions.rb +1 -1
  51. data/lib/emass_client/models/milestone_response_get.rb +1 -1
  52. data/lib/emass_client/models/milestone_response_get_milestone.rb +1 -1
  53. data/lib/emass_client/models/milestone_response_post.rb +1 -1
  54. data/lib/emass_client/models/milestone_response_put.rb +1 -1
  55. data/lib/emass_client/models/milestones_get.rb +1 -1
  56. data/lib/emass_client/models/milestones_put_post_delete.rb +1 -1
  57. data/lib/emass_client/models/milestones_request_delete_body_inner.rb +1 -1
  58. data/lib/emass_client/models/milestones_required_post.rb +1 -1
  59. data/lib/emass_client/models/milestones_required_put.rb +1 -1
  60. data/lib/emass_client/models/mock_object.rb +343 -0
  61. data/lib/emass_client/models/pac_get.rb +1 -1
  62. data/lib/emass_client/models/pac_post.rb +1 -1
  63. data/lib/emass_client/models/pac_response_get.rb +1 -1
  64. data/lib/emass_client/models/pac_response_post.rb +1 -1
  65. data/lib/emass_client/models/poam_get.rb +1 -1
  66. data/lib/emass_client/models/poam_post_put_del.rb +1 -1
  67. data/lib/emass_client/models/poam_request_delete_body_inner.rb +1 -1
  68. data/lib/emass_client/models/poam_response_delete.rb +1 -1
  69. data/lib/emass_client/models/poam_response_get_poams.rb +1 -1
  70. data/lib/emass_client/models/poam_response_get_systems.rb +1 -1
  71. data/lib/emass_client/models/poam_response_post.rb +1 -1
  72. data/lib/emass_client/models/poam_response_put.rb +1 -1
  73. data/lib/emass_client/models/register.rb +1 -1
  74. data/lib/emass_client/models/register_data.rb +1 -1
  75. data/lib/emass_client/models/register_user_request_post_body.rb +1 -1
  76. data/lib/emass_client/models/response200.rb +1 -1
  77. data/lib/emass_client/models/response201.rb +1 -1
  78. data/lib/emass_client/models/response201_meta.rb +1 -1
  79. data/lib/emass_client/models/response400.rb +1 -1
  80. data/lib/emass_client/models/response400_meta.rb +1 -1
  81. data/lib/emass_client/models/response401.rb +1 -1
  82. data/lib/emass_client/models/response401_meta.rb +1 -1
  83. data/lib/emass_client/models/response403.rb +1 -1
  84. data/lib/emass_client/models/response403_meta.rb +1 -1
  85. data/lib/emass_client/models/response404.rb +1 -1
  86. data/lib/emass_client/models/response405.rb +1 -1
  87. data/lib/emass_client/models/response405_meta.rb +1 -1
  88. data/lib/emass_client/models/response411.rb +1 -1
  89. data/lib/emass_client/models/response411_meta.rb +1 -1
  90. data/lib/emass_client/models/response490.rb +1 -1
  91. data/lib/emass_client/models/response490_meta.rb +1 -1
  92. data/lib/emass_client/models/response500.rb +1 -1
  93. data/lib/emass_client/models/response500_meta.rb +1 -1
  94. data/lib/emass_client/models/role_category.rb +1 -1
  95. data/lib/emass_client/models/roles.rb +1 -1
  96. data/lib/emass_client/models/ssps.rb +1 -1
  97. data/lib/emass_client/models/stage.rb +1 -1
  98. data/lib/emass_client/models/static_code_application.rb +1 -1
  99. data/lib/emass_client/models/static_code_post.rb +1 -1
  100. data/lib/emass_client/models/static_code_request_post_body.rb +1 -1
  101. data/lib/emass_client/models/static_code_request_post_body_application.rb +1 -1
  102. data/lib/emass_client/models/static_code_response_post.rb +1 -1
  103. data/lib/emass_client/models/success200_response.rb +1 -1
  104. data/lib/emass_client/models/success200_response_data_inner.rb +1 -1
  105. data/lib/emass_client/models/system_response.rb +1 -1
  106. data/lib/emass_client/models/system_roles_category_response.rb +1 -1
  107. data/lib/emass_client/models/system_roles_response.rb +1 -1
  108. data/lib/emass_client/models/system_roles_response_data_inner.rb +1 -1
  109. data/lib/emass_client/models/systems.rb +24 -2
  110. data/lib/emass_client/models/systems_response.rb +1 -1
  111. data/lib/emass_client/models/test.rb +1 -1
  112. data/lib/emass_client/models/test_data.rb +1 -1
  113. data/lib/emass_client/models/test_results_get.rb +1 -1
  114. data/lib/emass_client/models/test_results_post.rb +1 -1
  115. data/lib/emass_client/models/test_results_response_get.rb +1 -1
  116. data/lib/emass_client/models/test_results_response_post.rb +1 -1
  117. data/lib/emass_client/models/users.rb +1 -1
  118. data/lib/emass_client/models/workflow_definition_get.rb +1 -1
  119. data/lib/emass_client/models/workflow_definition_response_get.rb +1 -1
  120. data/lib/emass_client/models/workflow_instance_get.rb +1 -1
  121. data/lib/emass_client/models/workflow_instance_response_get.rb +3 -5
  122. data/lib/emass_client/models/workflow_instances_get.rb +1 -1
  123. data/lib/emass_client/models/workflow_instances_response_get.rb +1 -1
  124. data/lib/emass_client/models/workflow_instances_response_get_pagination.rb +1 -1
  125. data/lib/emass_client/version.rb +2 -2
  126. data/lib/emass_client.rb +4 -1
  127. metadata +5 -2
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 64771d58caf2ea704cd33e6a29e727ed02cce76c92ff25e8ec5955f20f7a51c3
4
- data.tar.gz: aa0024fc83dd3e641560ddd2c6e9490dce85c8c1bb20ad794bd25d41f30cb12e
3
+ metadata.gz: 780452a743966f10e9558dfb9a1bc89ea009a771e4ad74afc03239b5086fd6a9
4
+ data.tar.gz: 3ae10b7a997fa4fd7c2273be063e5209bad7478230a1323e43226ebf9c3491fb
5
5
  SHA512:
6
- metadata.gz: 2a0d19c90f8cc8d36dbec0b812a21309618b76bd7328f5924c324234ac265cb1c2a92fe7902da3b56bc2eac161251238773fbd6472fcaf7845558394724c5108
7
- data.tar.gz: b6105ea2705a0ccc89f0d77a30e5dd648327351c12cc0aa1f00b7a10c5dc893ffbfe62e524bf7b5849d3e11d5b1b56369e1163d8fa5b43c0ce7292b34849c169
6
+ metadata.gz: 50ba9fc5115e270b1b3968b74cf0ee2a277431498a01082d1fd885ddfbad04a10c1e62146a704d5eb71e99f222d6d88ecd13f353c95344cd69270eb4e462a55d
7
+ data.tar.gz: 9ec3e29775427276931a44723ed351565996585eff72ece3c6552b080737eeb467a039342b25039d3bdff081b2230e6f530fd273952113d5d01487ebdd17eb0d
data/README.md CHANGED
@@ -53,8 +53,8 @@ To establish an account with eMASS and/or acquire an api-key/user-uid, contact o
53
53
 
54
54
  This SDK is automatically generated by the [OpenAPI Generator](https://openapi-generator.tech) project:
55
55
 
56
- - API version: v3.9
57
- - Package version: 3.9.1
56
+ - API version: v3.10
57
+ - Package version: 3.9.10
58
58
  - Build package: org.openapitools.codegen.languages.RubyClientCodegen
59
59
  For more information, please visit [https://www.dcsa.mil/is/emass/](https://www.dcsa.mil/is/emass/)
60
60
 
@@ -71,16 +71,16 @@ gem build emass_client.gemspec
71
71
  Then either install the gem locally:
72
72
 
73
73
  ```shell
74
- gem install ./emass_client-3.9.1.gem
74
+ gem install ./emass_client-3.9.10.gem
75
75
  ```
76
76
 
77
- (for development, run `gem install --dev ./emass_client-3.9.1.gem` to install the development dependencies)
77
+ (for development, run `gem install --dev ./emass_client-3.9.10.gem` to install the development dependencies)
78
78
 
79
79
  or publish the gem to a gem hosting service, e.g. [RubyGems](https://rubygems.org/).
80
80
 
81
81
  Finally add this to the Gemfile:
82
82
 
83
- gem 'emass_client', '~> 3.9.1'
83
+ gem 'emass_client', '~> 3.9.10'
84
84
 
85
85
  ### Install from Git
86
86
 
@@ -160,32 +160,35 @@ Class | Method | HTTP request | Description
160
160
  *EmassClient::ContainerScanResultsApi* | [**add_container_sans_by_system_id**](docs/ContainerScanResultsApi.md#add_container_sans_by_system_id) | **POST** /api/systems/{systemId}/container-scan-results | Add one or many containers and their scan results
161
161
  *EmassClient::ControlsApi* | [**get_system_controls**](docs/ControlsApi.md#get_system_controls) | **GET** /api/systems/{systemId}/controls | Get control information in a system for one or many controls
162
162
  *EmassClient::ControlsApi* | [**update_control_by_system_id**](docs/ControlsApi.md#update_control_by_system_id) | **PUT** /api/systems/{systemId}/controls | Update control information in a system for one or many controls
163
- *EmassClient::DashboardsApi* | [**get_system_artifacts_details**](docs/DashboardsApi.md#get_system_artifacts_details) | **GET** /api/dashboards/system-artifacts-details | Get dashboard information
164
- *EmassClient::DashboardsApi* | [**get_system_artifacts_summary**](docs/DashboardsApi.md#get_system_artifacts_summary) | **GET** /api/dashboards/system-artifacts-summary | Get dashboard information
165
- *EmassClient::DashboardsApi* | [**get_system_assessment_procedures_details**](docs/DashboardsApi.md#get_system_assessment_procedures_details) | **GET** /api/dashboards/system-assessment-procedures-details | Get dashboard information
166
- *EmassClient::DashboardsApi* | [**get_system_associations_details**](docs/DashboardsApi.md#get_system_associations_details) | **GET** /api/dashboards/system-associations-details | Get dashboard information
167
- *EmassClient::DashboardsApi* | [**get_system_control_compliance_summary**](docs/DashboardsApi.md#get_system_control_compliance_summary) | **GET** /api/dashboards/system-control-compliance-summary | Get dashboard information
168
- *EmassClient::DashboardsApi* | [**get_system_hardware_details**](docs/DashboardsApi.md#get_system_hardware_details) | **GET** /api/dashboards/system-hardware-details | Get dashboard information
169
- *EmassClient::DashboardsApi* | [**get_system_hardware_summary**](docs/DashboardsApi.md#get_system_hardware_summary) | **GET** /api/dashboards/system-hardware-summary | Get dashboard information
170
- *EmassClient::DashboardsApi* | [**get_system_poam_details**](docs/DashboardsApi.md#get_system_poam_details) | **GET** /api/dashboards/system-poam-details | Get dashboard information
171
- *EmassClient::DashboardsApi* | [**get_system_poam_summary**](docs/DashboardsApi.md#get_system_poam_summary) | **GET** /api/dashboards/system-poam-summary | Get dashboard information
172
- *EmassClient::DashboardsApi* | [**get_system_ports_protocols_details**](docs/DashboardsApi.md#get_system_ports_protocols_details) | **GET** /api/dashboards/system-ports-protocols-details | Get dashboard information
173
- *EmassClient::DashboardsApi* | [**get_system_ports_protocols_summary**](docs/DashboardsApi.md#get_system_ports_protocols_summary) | **GET** /api/dashboards/system-ports-protocols-summary | Get dashboard information
174
- *EmassClient::DashboardsApi* | [**get_system_privacy_summary**](docs/DashboardsApi.md#get_system_privacy_summary) | **GET** /api/dashboards/system-privacy-summary | Get dashboard information
175
- *EmassClient::DashboardsApi* | [**get_system_security_control_details**](docs/DashboardsApi.md#get_system_security_control_details) | **GET** /api/dashboards/system-security-controls-details | Get dashboard information
176
- *EmassClient::DashboardsApi* | [**get_system_sensor_hardware_details**](docs/DashboardsApi.md#get_system_sensor_hardware_details) | **GET** /api/dashboards/system-sensor-hardware-details | Get dashboard information
177
- *EmassClient::DashboardsApi* | [**get_system_sensor_hardware_summary**](docs/DashboardsApi.md#get_system_sensor_hardware_summary) | **GET** /api/dashboards/system-sensor-hardware-summary | Get dashboard information
178
- *EmassClient::DashboardsApi* | [**get_system_status_details**](docs/DashboardsApi.md#get_system_status_details) | **GET** /api/dashboards/system-status-details | Get dashboard information
179
- *EmassClient::DashboardsApi* | [**get_user_system_assignments_details**](docs/DashboardsApi.md#get_user_system_assignments_details) | **GET** /api/dashboards/user-system-assignments-details | Get dashboard information
180
- *EmassClient::DashboardsApi* | [**get_va_omb_fsma_saop_summary**](docs/DashboardsApi.md#get_va_omb_fsma_saop_summary) | **GET** /api/dashboards/va-omb-fisma-saop-summary | Get dashboard information
181
- *EmassClient::DashboardsApi* | [**get_va_system_a2_summary**](docs/DashboardsApi.md#get_va_system_a2_summary) | **GET** /api/dashboards/va-system-a2-summary | Get dashboard information
182
- *EmassClient::DashboardsApi* | [**get_va_system_aa_summary**](docs/DashboardsApi.md#get_va_system_aa_summary) | **GET** /api/dashboards/va-system-aa-summary | Get dashboard information
183
- *EmassClient::DashboardsApi* | [**get_va_system_fisma_invetory_crypto_summary**](docs/DashboardsApi.md#get_va_system_fisma_invetory_crypto_summary) | **GET** /api/dashboards/va-system-fisma-inventory-crypto-summary | Get dashboard information
184
- *EmassClient::DashboardsApi* | [**get_va_system_fisma_invetory_summary**](docs/DashboardsApi.md#get_va_system_fisma_invetory_summary) | **GET** /api/dashboards/va-system-fisma-inventory-summary | Get dashboard information
185
- *EmassClient::DashboardsApi* | [**get_va_system_pl109_reporting_summary**](docs/DashboardsApi.md#get_va_system_pl109_reporting_summary) | **GET** /api/dashboards/va-system-pl-109-reporting-summary | Get dashboard information
186
- *EmassClient::DashboardsApi* | [**get_va_system_threat_architecture_details**](docs/DashboardsApi.md#get_va_system_threat_architecture_details) | **GET** /api/dashboards/va-system-threat-architecture-details | Get dashboard information
187
- *EmassClient::DashboardsApi* | [**get_va_system_threat_risk_summary**](docs/DashboardsApi.md#get_va_system_threat_risk_summary) | **GET** /api/dashboards/va-system-threat-risks-summary | Get dashboard information
188
- *EmassClient::DashboardsApi* | [**get_va_system_threat_source_details**](docs/DashboardsApi.md#get_va_system_threat_source_details) | **GET** /api/dashboards/va-system-threat-sources-details | Get dashboard information
163
+ *EmassClient::DashboardsApi* | [**get_system_artifacts_details**](docs/DashboardsApi.md#get_system_artifacts_details) | **GET** /api/dashboards/system-artifacts-details | System Artifacts Details
164
+ *EmassClient::DashboardsApi* | [**get_system_artifacts_summary**](docs/DashboardsApi.md#get_system_artifacts_summary) | **GET** /api/dashboards/system-artifacts-summary | System Artifacts Summary
165
+ *EmassClient::DashboardsApi* | [**get_system_assessment_procedures_details**](docs/DashboardsApi.md#get_system_assessment_procedures_details) | **GET** /api/dashboards/system-assessment-procedures-details | System Assessment Procedures Details
166
+ *EmassClient::DashboardsApi* | [**get_system_associations_details**](docs/DashboardsApi.md#get_system_associations_details) | **GET** /api/dashboards/system-associations-details | System Associations Details
167
+ *EmassClient::DashboardsApi* | [**get_system_common_integration_status_summary**](docs/DashboardsApi.md#get_system_common_integration_status_summary) | **GET** /api/dashboards/system-conmon-integration-status-summary | System CONMON Integration Status
168
+ *EmassClient::DashboardsApi* | [**get_system_control_compliance_summary**](docs/DashboardsApi.md#get_system_control_compliance_summary) | **GET** /api/dashboards/system-control-compliance-summary | System Control Compliance Summary
169
+ *EmassClient::DashboardsApi* | [**get_system_hardware_details**](docs/DashboardsApi.md#get_system_hardware_details) | **GET** /api/dashboards/system-hardware-details | System Hardware Details
170
+ *EmassClient::DashboardsApi* | [**get_system_hardware_summary**](docs/DashboardsApi.md#get_system_hardware_summary) | **GET** /api/dashboards/system-hardware-summary | System Hardware Summary
171
+ *EmassClient::DashboardsApi* | [**get_system_poam_details**](docs/DashboardsApi.md#get_system_poam_details) | **GET** /api/dashboards/system-poam-details | System POA&M Details
172
+ *EmassClient::DashboardsApi* | [**get_system_poam_summary**](docs/DashboardsApi.md#get_system_poam_summary) | **GET** /api/dashboards/system-poam-summary | System POA&M Summary
173
+ *EmassClient::DashboardsApi* | [**get_system_ports_protocols_details**](docs/DashboardsApi.md#get_system_ports_protocols_details) | **GET** /api/dashboards/system-ports-protocols-details | System Ports/Protocols Details
174
+ *EmassClient::DashboardsApi* | [**get_system_ports_protocols_summary**](docs/DashboardsApi.md#get_system_ports_protocols_summary) | **GET** /api/dashboards/system-ports-protocols-summary | System Ports/Protocols Summary
175
+ *EmassClient::DashboardsApi* | [**get_system_privacy_summary**](docs/DashboardsApi.md#get_system_privacy_summary) | **GET** /api/dashboards/system-privacy-summary | System Privacy Summary
176
+ *EmassClient::DashboardsApi* | [**get_system_security_control_details**](docs/DashboardsApi.md#get_system_security_control_details) | **GET** /api/dashboards/system-security-controls-details | System Control Compliance Details
177
+ *EmassClient::DashboardsApi* | [**get_system_sensor_hardware_details**](docs/DashboardsApi.md#get_system_sensor_hardware_details) | **GET** /api/dashboards/system-sensor-hardware-details | System Sensor Hardware Details
178
+ *EmassClient::DashboardsApi* | [**get_system_sensor_hardware_summary**](docs/DashboardsApi.md#get_system_sensor_hardware_summary) | **GET** /api/dashboards/system-sensor-hardware-summary | System Sensor Hardware Summary
179
+ *EmassClient::DashboardsApi* | [**get_system_software_details**](docs/DashboardsApi.md#get_system_software_details) | **GET** /api/dashboards/system-software-details | System Software Details
180
+ *EmassClient::DashboardsApi* | [**get_system_software_summary**](docs/DashboardsApi.md#get_system_software_summary) | **GET** /api/dashboards/system-software-summary | System Software Summary
181
+ *EmassClient::DashboardsApi* | [**get_system_status_details**](docs/DashboardsApi.md#get_system_status_details) | **GET** /api/dashboards/system-status-details | System Status Details
182
+ *EmassClient::DashboardsApi* | [**get_user_system_assignments_details**](docs/DashboardsApi.md#get_user_system_assignments_details) | **GET** /api/dashboards/user-system-assignments-details | User System Assignments Details
183
+ *EmassClient::DashboardsApi* | [**get_va_omb_fsma_saop_summary**](docs/DashboardsApi.md#get_va_omb_fsma_saop_summary) | **GET** /api/dashboards/va-omb-fisma-saop-summary | VA OMB FISMA SAOP Summary
184
+ *EmassClient::DashboardsApi* | [**get_va_system_a2_summary**](docs/DashboardsApi.md#get_va_system_a2_summary) | **GET** /api/dashboards/va-system-a2-summary | VA System A2.0 Summary
185
+ *EmassClient::DashboardsApi* | [**get_va_system_aa_summary**](docs/DashboardsApi.md#get_va_system_aa_summary) | **GET** /api/dashboards/va-system-aa-summary | VA System A&A Summary
186
+ *EmassClient::DashboardsApi* | [**get_va_system_fisma_invetory_crypto_summary**](docs/DashboardsApi.md#get_va_system_fisma_invetory_crypto_summary) | **GET** /api/dashboards/va-system-fisma-inventory-crypto-summary | VA System FISMA Inventory Crypto Summary
187
+ *EmassClient::DashboardsApi* | [**get_va_system_fisma_invetory_summary**](docs/DashboardsApi.md#get_va_system_fisma_invetory_summary) | **GET** /api/dashboards/va-system-fisma-inventory-summary | VA System FISMA Inventory Summary
188
+ *EmassClient::DashboardsApi* | [**get_va_system_pl109_reporting_summary**](docs/DashboardsApi.md#get_va_system_pl109_reporting_summary) | **GET** /api/dashboards/va-system-pl-109-reporting-summary | VA System P.L. 109 Reporting Summary
189
+ *EmassClient::DashboardsApi* | [**get_va_system_threat_architecture_details**](docs/DashboardsApi.md#get_va_system_threat_architecture_details) | **GET** /api/dashboards/va-system-threat-architecture-details | VA System Threat Architecture Details
190
+ *EmassClient::DashboardsApi* | [**get_va_system_threat_risk_summary**](docs/DashboardsApi.md#get_va_system_threat_risk_summary) | **GET** /api/dashboards/va-system-threat-risks-summary | VA System Threat Risks Summary
191
+ *EmassClient::DashboardsApi* | [**get_va_system_threat_source_details**](docs/DashboardsApi.md#get_va_system_threat_source_details) | **GET** /api/dashboards/va-system-threat-sources-details | VA System Threat Sources Details
189
192
  *EmassClient::MilestonesApi* | [**add_milestone_by_system_id_and_poam_id**](docs/MilestonesApi.md#add_milestone_by_system_id_and_poam_id) | **POST** /api/systems/{systemId}/poams/{poamId}/milestones | Add milestones to one or many POA&M items in a system
190
193
  *EmassClient::MilestonesApi* | [**delete_milestone**](docs/MilestonesApi.md#delete_milestone) | **DELETE** /api/systems/{systemId}/poams/{poamId}/milestones | Remove milestones in a system for one or many POA&M items
191
194
  *EmassClient::MilestonesApi* | [**get_system_milestones_by_poam_id**](docs/MilestonesApi.md#get_system_milestones_by_poam_id) | **GET** /api/systems/{systemId}/poams/{poamId}/milestones | Get milestones in one or many POA&M items in a system
@@ -236,6 +239,8 @@ Class | Method | HTTP request | Description
236
239
  - [EmassClient::ControlsPut](docs/ControlsPut.md)
237
240
  - [EmassClient::ControlsResponseGet](docs/ControlsResponseGet.md)
238
241
  - [EmassClient::ControlsResponsePut](docs/ControlsResponsePut.md)
242
+ - [EmassClient::DashboardMockResponse](docs/DashboardMockResponse.md)
243
+ - [EmassClient::DashboardMockResponsePagination](docs/DashboardMockResponsePagination.md)
239
244
  - [EmassClient::DefinitionTransitions](docs/DefinitionTransitions.md)
240
245
  - [EmassClient::InstancesTransitions](docs/InstancesTransitions.md)
241
246
  - [EmassClient::MilestoneResponseGet](docs/MilestoneResponseGet.md)
@@ -247,6 +252,7 @@ Class | Method | HTTP request | Description
247
252
  - [EmassClient::MilestonesRequestDeleteBodyInner](docs/MilestonesRequestDeleteBodyInner.md)
248
253
  - [EmassClient::MilestonesRequiredPost](docs/MilestonesRequiredPost.md)
249
254
  - [EmassClient::MilestonesRequiredPut](docs/MilestonesRequiredPut.md)
255
+ - [EmassClient::MockObject](docs/MockObject.md)
250
256
  - [EmassClient::PacGet](docs/PacGet.md)
251
257
  - [EmassClient::PacPost](docs/PacPost.md)
252
258
  - [EmassClient::PacResponseGet](docs/PacResponseGet.md)
data/lib/emass_client/api/artifacts_api.rb CHANGED
@@ -3,7 +3,7 @@
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.9
6
+ The version of the OpenAPI document: v3.10
7
7
  Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 7.0.0-SNAPSHOT
data/lib/emass_client/api/artifacts_export_api.rb CHANGED
@@ -3,7 +3,7 @@
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.9
6
+ The version of the OpenAPI document: v3.10
7
7
  Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 7.0.0-SNAPSHOT
data/lib/emass_client/api/cac_api.rb CHANGED
@@ -3,7 +3,7 @@
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.9
6
+ The version of the OpenAPI document: v3.10
7
7
  Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 7.0.0-SNAPSHOT
data/lib/emass_client/api/cloud_resource_results_api.rb CHANGED
@@ -3,7 +3,7 @@
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.9
6
+ The version of the OpenAPI document: v3.10
7
7
  Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 7.0.0-SNAPSHOT
data/lib/emass_client/api/cmmc_assessments_api.rb CHANGED
@@ -3,7 +3,7 @@
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.9
6
+ The version of the OpenAPI document: v3.10
7
7
  Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 7.0.0-SNAPSHOT
data/lib/emass_client/api/container_scan_results_api.rb CHANGED
@@ -3,7 +3,7 @@
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.9
6
+ The version of the OpenAPI document: v3.10
7
7
  Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 7.0.0-SNAPSHOT
data/lib/emass_client/api/controls_api.rb CHANGED
@@ -3,7 +3,7 @@
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.9
6
+ The version of the OpenAPI document: v3.10
7
7
  Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 7.0.0-SNAPSHOT