emass_client 3.4.0 → 3.9.1
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/README.md +23 -11
- data/lib/emass_client/api/artifacts_api.rb +7 -4
- data/lib/emass_client/api/artifacts_export_api.rb +2 -2
- data/lib/emass_client/api/cac_api.rb +2 -2
- data/lib/emass_client/api/{cloud_resources_api.rb → cloud_resource_results_api.rb} +8 -8
- data/lib/emass_client/api/cmmc_assessments_api.rb +2 -2
- data/lib/emass_client/api/{containers_api.rb → container_scan_results_api.rb} +8 -8
- data/lib/emass_client/api/controls_api.rb +2 -2
- data/lib/emass_client/api/dashboards_api.rb +868 -90
- data/lib/emass_client/api/milestones_api.rb +2 -2
- data/lib/emass_client/api/pac_api.rb +2 -2
- data/lib/emass_client/api/poam_api.rb +2 -2
- data/lib/emass_client/api/registration_api.rb +8 -19
- data/lib/emass_client/api/static_code_scans_api.rb +2 -2
- data/lib/emass_client/api/system_roles_api.rb +2 -2
- data/lib/emass_client/api/systems_api.rb +2 -2
- data/lib/emass_client/api/test_api.rb +2 -2
- data/lib/emass_client/api/test_results_api.rb +2 -2
- data/lib/emass_client/api/workflow_definitions_api.rb +2 -2
- data/lib/emass_client/api/workflow_instances_api.rb +2 -2
- data/lib/emass_client/api_client.rb +2 -2
- data/lib/emass_client/api_error.rb +3 -2
- data/lib/emass_client/configuration.rb +8 -8
- data/lib/emass_client/models/artifacts_get.rb +44 -68
- data/lib/emass_client/models/artifacts_request_delete_body_inner.rb +2 -2
- data/lib/emass_client/models/artifacts_response_del.rb +2 -2
- data/lib/emass_client/models/artifacts_response_del_data_inner.rb +2 -2
- data/lib/emass_client/models/artifacts_response_get.rb +2 -2
- data/lib/emass_client/models/artifacts_response_put_post.rb +2 -2
- data/lib/emass_client/models/artifacts_response_put_post_data_inner.rb +2 -2
- data/lib/emass_client/models/cac_get.rb +2 -2
- data/lib/emass_client/models/cac_response_get.rb +2 -2
- data/lib/emass_client/models/cac_response_post.rb +2 -2
- data/lib/emass_client/models/cac_response_post_data_inner.rb +2 -2
- data/lib/emass_client/models/cloud_resources_post.rb +2 -2
- data/lib/emass_client/models/cloud_resources_response_post.rb +2 -2
- data/lib/emass_client/models/cmmc_get.rb +111 -35
- data/lib/emass_client/models/cmmc_response_get.rb +2 -2
- data/lib/emass_client/models/connectivity_ccsd.rb +2 -2
- data/lib/emass_client/models/containers_resources_post.rb +2 -2
- data/lib/emass_client/models/containers_response_post.rb +2 -2
- data/lib/emass_client/models/controls_get.rb +2 -2
- data/lib/emass_client/models/controls_put.rb +2 -2
- data/lib/emass_client/models/controls_response_get.rb +2 -2
- data/lib/emass_client/models/controls_response_put.rb +2 -2
- data/lib/emass_client/models/definition_transitions.rb +2 -2
- data/lib/emass_client/models/instances_transitions.rb +2 -2
- data/lib/emass_client/models/milestone_response_get.rb +2 -2
- data/lib/emass_client/models/milestone_response_get_milestone.rb +2 -2
- data/lib/emass_client/models/milestone_response_post.rb +2 -2
- data/lib/emass_client/models/milestone_response_put.rb +2 -2
- data/lib/emass_client/models/milestones_get.rb +2 -2
- data/lib/emass_client/models/milestones_put_post_delete.rb +2 -2
- data/lib/emass_client/models/milestones_request_delete_body_inner.rb +2 -2
- data/lib/emass_client/models/milestones_required_post.rb +2 -2
- data/lib/emass_client/models/milestones_required_put.rb +2 -2
- data/lib/emass_client/models/pac_get.rb +2 -2
- data/lib/emass_client/models/pac_post.rb +2 -2
- data/lib/emass_client/models/pac_response_get.rb +2 -2
- data/lib/emass_client/models/pac_response_post.rb +2 -2
- data/lib/emass_client/models/poam_get.rb +2 -2
- data/lib/emass_client/models/poam_post_put_del.rb +2 -2
- data/lib/emass_client/models/poam_request_delete_body_inner.rb +2 -2
- data/lib/emass_client/models/poam_response_delete.rb +2 -2
- data/lib/emass_client/models/poam_response_get_poams.rb +2 -2
- data/lib/emass_client/models/poam_response_get_systems.rb +2 -2
- data/lib/emass_client/models/poam_response_post.rb +2 -2
- data/lib/emass_client/models/poam_response_put.rb +2 -2
- data/lib/emass_client/models/register.rb +2 -2
- data/lib/emass_client/models/register_data.rb +2 -2
- data/lib/emass_client/models/register_user_request_post_body.rb +2 -2
- data/lib/emass_client/models/response200.rb +2 -2
- data/lib/emass_client/models/response201.rb +2 -2
- data/lib/emass_client/models/response201_meta.rb +2 -2
- data/lib/emass_client/models/response400.rb +2 -2
- data/lib/emass_client/models/response400_meta.rb +2 -2
- data/lib/emass_client/models/response401.rb +2 -2
- data/lib/emass_client/models/response401_meta.rb +2 -2
- data/lib/emass_client/models/response403.rb +2 -2
- data/lib/emass_client/models/response403_meta.rb +2 -2
- data/lib/emass_client/models/response404.rb +2 -2
- data/lib/emass_client/models/response405.rb +2 -2
- data/lib/emass_client/models/response405_meta.rb +2 -2
- data/lib/emass_client/models/response411.rb +2 -2
- data/lib/emass_client/models/response411_meta.rb +2 -2
- data/lib/emass_client/models/response490.rb +2 -2
- data/lib/emass_client/models/response490_meta.rb +2 -2
- data/lib/emass_client/models/response500.rb +2 -2
- data/lib/emass_client/models/response500_meta.rb +2 -2
- data/lib/emass_client/models/role_category.rb +2 -2
- data/lib/emass_client/models/roles.rb +2 -2
- data/lib/emass_client/models/ssps.rb +2 -2
- data/lib/emass_client/models/stage.rb +2 -2
- data/lib/emass_client/models/static_code_application.rb +2 -2
- data/lib/emass_client/models/static_code_post.rb +2 -2
- data/lib/emass_client/models/static_code_request_post_body.rb +2 -2
- data/lib/emass_client/models/static_code_request_post_body_application.rb +2 -2
- data/lib/emass_client/models/static_code_response_post.rb +2 -2
- data/lib/emass_client/models/success200_response.rb +2 -2
- data/lib/emass_client/models/success200_response_data_inner.rb +2 -2
- data/lib/emass_client/models/system_response.rb +2 -2
- data/lib/emass_client/models/system_roles_category_response.rb +2 -2
- data/lib/emass_client/models/system_roles_response.rb +2 -2
- data/lib/emass_client/models/system_roles_response_data_inner.rb +2 -2
- data/lib/emass_client/models/systems.rb +399 -71
- data/lib/emass_client/models/systems_response.rb +2 -2
- data/lib/emass_client/models/test.rb +2 -2
- data/lib/emass_client/models/test_data.rb +2 -2
- data/lib/emass_client/models/test_results_get.rb +2 -2
- data/lib/emass_client/models/test_results_post.rb +2 -2
- data/lib/emass_client/models/test_results_response_get.rb +2 -2
- data/lib/emass_client/models/test_results_response_post.rb +2 -2
- data/lib/emass_client/models/users.rb +2 -2
- data/lib/emass_client/models/workflow_definition_get.rb +2 -2
- data/lib/emass_client/models/workflow_definition_response_get.rb +2 -2
- data/lib/emass_client/models/workflow_instance_get.rb +2 -2
- data/lib/emass_client/models/workflow_instance_response_get.rb +2 -2
- data/lib/emass_client/models/workflow_instances_get.rb +2 -2
- data/lib/emass_client/models/workflow_instances_response_get.rb +2 -2
- data/lib/emass_client/models/workflow_instances_response_get_pagination.rb +2 -2
- data/lib/emass_client/version.rb +3 -3
- data/lib/emass_client.rb +4 -4
- metadata +8 -31
checksums.yaml
CHANGED
@@ -1,7 +1,7 @@
|
|
1
1
|
---
|
2
2
|
SHA256:
|
3
|
-
metadata.gz:
|
4
|
-
data.tar.gz:
|
3
|
+
metadata.gz: 64771d58caf2ea704cd33e6a29e727ed02cce76c92ff25e8ec5955f20f7a51c3
|
4
|
+
data.tar.gz: aa0024fc83dd3e641560ddd2c6e9490dce85c8c1bb20ad794bd25d41f30cb12e
|
5
5
|
SHA512:
|
6
|
-
metadata.gz:
|
7
|
-
data.tar.gz:
|
6
|
+
metadata.gz: 2a0d19c90f8cc8d36dbec0b812a21309618b76bd7328f5924c324234ac265cb1c2a92fe7902da3b56bc2eac161251238773fbd6472fcaf7845558394724c5108
|
7
|
+
data.tar.gz: b6105ea2705a0ccc89f0d77a30e5dd648327351c12cc0aa1f00b7a10c5dc893ffbfe62e524bf7b5849d3e11d5b1b56369e1163d8fa5b43c0ce7292b34849c169
|
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.
|
57
|
-
- Package version: 3.
|
56
|
+
- API version: v3.9
|
57
|
+
- Package version: 3.9.1
|
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.
|
74
|
+
gem install ./emass_client-3.9.1.gem
|
75
75
|
```
|
76
76
|
|
77
|
-
(for development, run `gem install --dev ./emass_client-3.
|
77
|
+
(for development, run `gem install --dev ./emass_client-3.9.1.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.
|
83
|
+
gem 'emass_client', '~> 3.9.1'
|
84
84
|
|
85
85
|
### Install from Git
|
86
86
|
|
@@ -126,6 +126,7 @@ api_instance = EmassClient::ArtifactsApi.new
|
|
126
126
|
system_id = 35 # Integer | **System Id**: The unique system record identifier.
|
127
127
|
zipper = File.new('/path/to/some/file') # File |
|
128
128
|
opts = {
|
129
|
+
is_bulk: true, # Boolean | **Is Bulk**: If no value is specified, the default is false, and an individual artifact file is expected. When set to true, a .zip file is expected which can contain multiple artifact files\"
|
129
130
|
is_template: true, # Boolean |
|
130
131
|
type: 'Procedure', # String |
|
131
132
|
category: 'Implementation Guidance' # String |
|
@@ -155,10 +156,12 @@ Class | Method | HTTP request | Description
|
|
155
156
|
*EmassClient::CACApi* | [**add_system_cac**](docs/CACApi.md#add_system_cac) | **POST** /api/systems/{systemId}/approval/cac | Submit control to second role of CAC
|
156
157
|
*EmassClient::CACApi* | [**get_system_cac**](docs/CACApi.md#get_system_cac) | **GET** /api/systems/{systemId}/approval/cac | Get location of one or many controls in CAC
|
157
158
|
*EmassClient::CMMCAssessmentsApi* | [**get_cmmc_assessments**](docs/CMMCAssessmentsApi.md#get_cmmc_assessments) | **GET** /api/cmmc-assessments | Get CMMC assessment information
|
158
|
-
*EmassClient::
|
159
|
-
*EmassClient::
|
159
|
+
*EmassClient::CloudResourceResultsApi* | [**add_cloud_resources_by_system_id**](docs/CloudResourceResultsApi.md#add_cloud_resources_by_system_id) | **POST** /api/systems/{systemId}/cloud-resource-results | Add one or many cloud resources and their scan results
|
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
|
160
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
|
161
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
|
162
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
|
163
166
|
*EmassClient::DashboardsApi* | [**get_system_associations_details**](docs/DashboardsApi.md#get_system_associations_details) | **GET** /api/dashboards/system-associations-details | Get dashboard information
|
164
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
|
@@ -166,15 +169,23 @@ Class | Method | HTTP request | Description
|
|
166
169
|
*EmassClient::DashboardsApi* | [**get_system_hardware_summary**](docs/DashboardsApi.md#get_system_hardware_summary) | **GET** /api/dashboards/system-hardware-summary | Get dashboard information
|
167
170
|
*EmassClient::DashboardsApi* | [**get_system_poam_details**](docs/DashboardsApi.md#get_system_poam_details) | **GET** /api/dashboards/system-poam-details | Get dashboard information
|
168
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
|
169
174
|
*EmassClient::DashboardsApi* | [**get_system_privacy_summary**](docs/DashboardsApi.md#get_system_privacy_summary) | **GET** /api/dashboards/system-privacy-summary | Get dashboard information
|
170
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
|
171
178
|
*EmassClient::DashboardsApi* | [**get_system_status_details**](docs/DashboardsApi.md#get_system_status_details) | **GET** /api/dashboards/system-status-details | Get dashboard information
|
172
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
|
173
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
|
174
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
|
175
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
|
176
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
|
177
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
|
178
189
|
*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
|
179
190
|
*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
|
180
191
|
*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
|
@@ -305,6 +316,7 @@ Class | Method | HTTP request | Description
|
|
305
316
|
## Documentation for Authorization
|
306
317
|
|
307
318
|
|
319
|
+
Authentication schemes defined for the API:
|
308
320
|
### apiKey
|
309
321
|
|
310
322
|
|
@@ -312,17 +324,17 @@ Class | Method | HTTP request | Description
|
|
312
324
|
- **API key parameter name**: api-key
|
313
325
|
- **Location**: HTTP header
|
314
326
|
|
315
|
-
###
|
327
|
+
### userId
|
316
328
|
|
317
329
|
|
318
330
|
- **Type**: API key
|
319
|
-
- **API key parameter name**:
|
331
|
+
- **API key parameter name**: user-uid
|
320
332
|
- **Location**: HTTP header
|
321
333
|
|
322
|
-
###
|
334
|
+
### mockType
|
323
335
|
|
324
336
|
|
325
337
|
- **Type**: API key
|
326
|
-
- **API key parameter name**:
|
338
|
+
- **API key parameter name**: Prefer
|
327
339
|
- **Location**: HTTP header
|
328
340
|
|
@@ -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.
|
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:
|
9
|
+
OpenAPI Generator version: 7.0.0-SNAPSHOT
|
10
10
|
|
11
11
|
=end
|
12
12
|
|
@@ -20,10 +20,11 @@ module EmassClient
|
|
20
20
|
@api_client = api_client
|
21
21
|
end
|
22
22
|
# Add one or many artifacts in a system
|
23
|
-
# <strong>Information</strong><br> The
|
23
|
+
# <strong>Information</strong><br> The body of a request through the Artifacts POST endpoint accepts a single binary file. Two Artifact POST methods are currently accepted: individual and bulk. Filename uniqueness within an eMASS system will be enforced by the API for both methods. <br><br> For POST requests that should result in a single artifact, the request should include the file. <br><br> For POST requests that should result in the creation of many artifacts, the request should include a single file with the extension \".zip\" only and the parameter isBulk should be set to true. This .zip file should contain one or more files corresponding to existing artifacts or new artifacts that will be created upon successful receipt. <br><br> Upon successful receipt of one or many artifacts, if a file is matched via filename to an artifact existing within the application, the file associated with the artifact will be updated. If no artifact is matched via filename to the application, a new artifact will be created with the following default values. Any values not specified below will be null <ul> <li>isTemplate: false</li> <li>type: Other</li> <li>category: Evidence</li> </ul> To update values other than the file itself, please submit a PUT request.<br> <strong>Business Rules</strong><br> Artifact cannot be saved if the fields below exceed the following character limits: <ul> <li>Filename - 1,000 characters</li> <li>Name - 100 characters</li> <li>Description - 10,000 characters</li> <li>Reference Page Number - 50 characters</li> </ul> Artifact cannot be saved if the file does not have an allowable file extension/type: .docx,.doc,.txt,.rtf,.xfdl,.xml,.mht,.mh,tml,.html,.htm,.pdf,.mdb,.accdb,.ppt, .pptx,.xls,.xlsx,.csv,.log,.jpeg,.jpg,.tiff,.bmp,.tif,.png,.gif,.zip,.rar,.msg, .vsd,.vsw,.vdx,.z{#},.ckl,.avi,.vsdx Artifact version cannot be saved if an Artifact with the same file name already exist in the system. Artifact cannot be saved if the file size exceeds 30MB. Artifact cannot be saved if the following fields are missing data: <ul> <li>Filename</li> <li>Type</li> <li>Category</li> </ul> Artifact cannot be saved if the Last Review Date (`lastReviewedDate`) is set in the future.
|
24
24
|
# @param system_id [Integer] **System Id**: The unique system record identifier.
|
25
25
|
# @param zipper [File]
|
26
26
|
# @param [Hash] opts the optional parameters
|
27
|
+
# @option opts [Boolean] :is_bulk **Is Bulk**: If no value is specified, the default is false, and an individual artifact file is expected. When set to true, a .zip file is expected which can contain multiple artifact files\" (default to false)
|
27
28
|
# @option opts [Boolean] :is_template
|
28
29
|
# @option opts [String] :type
|
29
30
|
# @option opts [String] :category
|
@@ -34,10 +35,11 @@ module EmassClient
|
|
34
35
|
end
|
35
36
|
|
36
37
|
# Add one or many artifacts in a system
|
37
|
-
# <strong>Information</strong><br> The
|
38
|
+
# <strong>Information</strong><br> The body of a request through the Artifacts POST endpoint accepts a single binary file. Two Artifact POST methods are currently accepted: individual and bulk. Filename uniqueness within an eMASS system will be enforced by the API for both methods. <br><br> For POST requests that should result in a single artifact, the request should include the file. <br><br> For POST requests that should result in the creation of many artifacts, the request should include a single file with the extension \".zip\" only and the parameter isBulk should be set to true. This .zip file should contain one or more files corresponding to existing artifacts or new artifacts that will be created upon successful receipt. <br><br> Upon successful receipt of one or many artifacts, if a file is matched via filename to an artifact existing within the application, the file associated with the artifact will be updated. If no artifact is matched via filename to the application, a new artifact will be created with the following default values. Any values not specified below will be null <ul> <li>isTemplate: false</li> <li>type: Other</li> <li>category: Evidence</li> </ul> To update values other than the file itself, please submit a PUT request.<br> <strong>Business Rules</strong><br> Artifact cannot be saved if the fields below exceed the following character limits: <ul> <li>Filename - 1,000 characters</li> <li>Name - 100 characters</li> <li>Description - 10,000 characters</li> <li>Reference Page Number - 50 characters</li> </ul> Artifact cannot be saved if the file does not have an allowable file extension/type: .docx,.doc,.txt,.rtf,.xfdl,.xml,.mht,.mh,tml,.html,.htm,.pdf,.mdb,.accdb,.ppt, .pptx,.xls,.xlsx,.csv,.log,.jpeg,.jpg,.tiff,.bmp,.tif,.png,.gif,.zip,.rar,.msg, .vsd,.vsw,.vdx,.z{#},.ckl,.avi,.vsdx Artifact version cannot be saved if an Artifact with the same file name already exist in the system. Artifact cannot be saved if the file size exceeds 30MB. Artifact cannot be saved if the following fields are missing data: <ul> <li>Filename</li> <li>Type</li> <li>Category</li> </ul> Artifact cannot be saved if the Last Review Date (`lastReviewedDate`) is set in the future.
|
38
39
|
# @param system_id [Integer] **System Id**: The unique system record identifier.
|
39
40
|
# @param zipper [File]
|
40
41
|
# @param [Hash] opts the optional parameters
|
42
|
+
# @option opts [Boolean] :is_bulk **Is Bulk**: If no value is specified, the default is false, and an individual artifact file is expected. When set to true, a .zip file is expected which can contain multiple artifact files\" (default to false)
|
41
43
|
# @option opts [Boolean] :is_template
|
42
44
|
# @option opts [String] :type
|
43
45
|
# @option opts [String] :category
|
@@ -67,6 +69,7 @@ module EmassClient
|
|
67
69
|
|
68
70
|
# query parameters
|
69
71
|
query_params = opts[:query_params] || {}
|
72
|
+
query_params[:'isBulk'] = opts[:'is_bulk'] if !opts[:'is_bulk'].nil?
|
70
73
|
|
71
74
|
# header parameters
|
72
75
|
header_params = opts[:header_params] || {}
|
@@ -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.
|
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:
|
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.
|
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:
|
9
|
+
OpenAPI Generator version: 7.0.0-SNAPSHOT
|
10
10
|
|
11
11
|
=end
|
12
12
|
|
@@ -3,17 +3,17 @@
|
|
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.
|
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:
|
9
|
+
OpenAPI Generator version: 7.0.0-SNAPSHOT
|
10
10
|
|
11
11
|
=end
|
12
12
|
|
13
13
|
require 'cgi'
|
14
14
|
|
15
15
|
module EmassClient
|
16
|
-
class
|
16
|
+
class CloudResourceResultsApi
|
17
17
|
attr_accessor :api_client
|
18
18
|
|
19
19
|
def initialize(api_client = ApiClient.default)
|
@@ -38,15 +38,15 @@ module EmassClient
|
|
38
38
|
# @return [Array<(CloudResourcesResponsePost, Integer, Hash)>] CloudResourcesResponsePost data, response status code and response headers
|
39
39
|
def add_cloud_resources_by_system_id_with_http_info(system_id, request_body, opts = {})
|
40
40
|
if @api_client.config.debugging
|
41
|
-
@api_client.config.logger.debug 'Calling API:
|
41
|
+
@api_client.config.logger.debug 'Calling API: CloudResourceResultsApi.add_cloud_resources_by_system_id ...'
|
42
42
|
end
|
43
43
|
# verify the required parameter 'system_id' is set
|
44
44
|
if @api_client.config.client_side_validation && system_id.nil?
|
45
|
-
fail ArgumentError, "Missing the required parameter 'system_id' when calling
|
45
|
+
fail ArgumentError, "Missing the required parameter 'system_id' when calling CloudResourceResultsApi.add_cloud_resources_by_system_id"
|
46
46
|
end
|
47
47
|
# verify the required parameter 'request_body' is set
|
48
48
|
if @api_client.config.client_side_validation && request_body.nil?
|
49
|
-
fail ArgumentError, "Missing the required parameter 'request_body' when calling
|
49
|
+
fail ArgumentError, "Missing the required parameter 'request_body' when calling CloudResourceResultsApi.add_cloud_resources_by_system_id"
|
50
50
|
end
|
51
51
|
# resource path
|
52
52
|
local_var_path = '/api/systems/{systemId}/cloud-resource-results'.sub('{' + 'systemId' + '}', CGI.escape(system_id.to_s))
|
@@ -77,7 +77,7 @@ module EmassClient
|
|
77
77
|
auth_names = opts[:debug_auth_names] || ['apiKey', 'mockType', 'userId']
|
78
78
|
|
79
79
|
new_options = opts.merge(
|
80
|
-
:operation => :"
|
80
|
+
:operation => :"CloudResourceResultsApi.add_cloud_resources_by_system_id",
|
81
81
|
:header_params => header_params,
|
82
82
|
:query_params => query_params,
|
83
83
|
:form_params => form_params,
|
@@ -88,7 +88,7 @@ module EmassClient
|
|
88
88
|
|
89
89
|
data, status_code, headers = @api_client.call_api(:POST, local_var_path, new_options)
|
90
90
|
if @api_client.config.debugging
|
91
|
-
@api_client.config.logger.debug "API called:
|
91
|
+
@api_client.config.logger.debug "API called: CloudResourceResultsApi#add_cloud_resources_by_system_id\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}"
|
92
92
|
end
|
93
93
|
return data, status_code, headers
|
94
94
|
end
|
@@ -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.
|
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:
|
9
|
+
OpenAPI Generator version: 7.0.0-SNAPSHOT
|
10
10
|
|
11
11
|
=end
|
12
12
|
|
@@ -3,17 +3,17 @@
|
|
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.
|
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:
|
9
|
+
OpenAPI Generator version: 7.0.0-SNAPSHOT
|
10
10
|
|
11
11
|
=end
|
12
12
|
|
13
13
|
require 'cgi'
|
14
14
|
|
15
15
|
module EmassClient
|
16
|
-
class
|
16
|
+
class ContainerScanResultsApi
|
17
17
|
attr_accessor :api_client
|
18
18
|
|
19
19
|
def initialize(api_client = ApiClient.default)
|
@@ -38,15 +38,15 @@ module EmassClient
|
|
38
38
|
# @return [Array<(ContainersResponsePost, Integer, Hash)>] ContainersResponsePost data, response status code and response headers
|
39
39
|
def add_container_sans_by_system_id_with_http_info(system_id, request_body, opts = {})
|
40
40
|
if @api_client.config.debugging
|
41
|
-
@api_client.config.logger.debug 'Calling API:
|
41
|
+
@api_client.config.logger.debug 'Calling API: ContainerScanResultsApi.add_container_sans_by_system_id ...'
|
42
42
|
end
|
43
43
|
# verify the required parameter 'system_id' is set
|
44
44
|
if @api_client.config.client_side_validation && system_id.nil?
|
45
|
-
fail ArgumentError, "Missing the required parameter 'system_id' when calling
|
45
|
+
fail ArgumentError, "Missing the required parameter 'system_id' when calling ContainerScanResultsApi.add_container_sans_by_system_id"
|
46
46
|
end
|
47
47
|
# verify the required parameter 'request_body' is set
|
48
48
|
if @api_client.config.client_side_validation && request_body.nil?
|
49
|
-
fail ArgumentError, "Missing the required parameter 'request_body' when calling
|
49
|
+
fail ArgumentError, "Missing the required parameter 'request_body' when calling ContainerScanResultsApi.add_container_sans_by_system_id"
|
50
50
|
end
|
51
51
|
# resource path
|
52
52
|
local_var_path = '/api/systems/{systemId}/container-scan-results'.sub('{' + 'systemId' + '}', CGI.escape(system_id.to_s))
|
@@ -77,7 +77,7 @@ module EmassClient
|
|
77
77
|
auth_names = opts[:debug_auth_names] || ['apiKey', 'mockType', 'userId']
|
78
78
|
|
79
79
|
new_options = opts.merge(
|
80
|
-
:operation => :"
|
80
|
+
:operation => :"ContainerScanResultsApi.add_container_sans_by_system_id",
|
81
81
|
:header_params => header_params,
|
82
82
|
:query_params => query_params,
|
83
83
|
:form_params => form_params,
|
@@ -88,7 +88,7 @@ module EmassClient
|
|
88
88
|
|
89
89
|
data, status_code, headers = @api_client.call_api(:POST, local_var_path, new_options)
|
90
90
|
if @api_client.config.debugging
|
91
|
-
@api_client.config.logger.debug "API called:
|
91
|
+
@api_client.config.logger.debug "API called: ContainerScanResultsApi#add_container_sans_by_system_id\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}"
|
92
92
|
end
|
93
93
|
return data, status_code, headers
|
94
94
|
end
|
@@ -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.
|
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:
|
9
|
+
OpenAPI Generator version: 7.0.0-SNAPSHOT
|
10
10
|
|
11
11
|
=end
|
12
12
|
|