diff --git a/src/ruby_client/.gitlab-ci.yml b/src/ruby_client/.gitlab-ci.yml new file mode 100644 index 00000000..3d57c5b3 --- /dev/null +++ b/src/ruby_client/.gitlab-ci.yml @@ -0,0 +1,26 @@ +.ruby: &ruby + variables: + LANG: "C.UTF-8" + before_script: + - ruby -v + - bundle config set --local deployment true + - bundle install -j $(nproc) + parallel: + matrix: + - RUBY_VERSION: ['2.3', '2.4', '2.5', '2.6', '2.7', '3.0'] + image: "ruby:$RUBY_VERSION" + cache: + paths: + - vendor/ruby + key: 'ruby-$RUBY_VERSION' + +gem: + extends: .ruby + script: + - bundle exec rspec + - bundle exec rake build + - bundle exec rake install + artifacts: + paths: + - pkg/*.gem + diff --git a/src/ruby_client/.openapi-generator/FILES b/src/ruby_client/.openapi-generator/FILES index 25bc6cad..4e5fa894 100644 --- a/src/ruby_client/.openapi-generator/FILES +++ b/src/ruby_client/.openapi-generator/FILES @@ -1,4 +1,5 @@ .gitignore +.gitlab-ci.yml .openapi-generator-ignore .rspec .rubocop.yml @@ -35,6 +36,7 @@ docs/ControlsGet.md docs/ControlsPut.md docs/ControlsResponseGet.md docs/ControlsResponsePut.md +docs/DashboardsApi.md docs/DefinitionTransitions.md docs/InstancesTransitions.md docs/MilestoneResponseGet.md @@ -131,6 +133,7 @@ lib/emass_client/api/cloud_resources_api.rb lib/emass_client/api/cmmc_assessments_api.rb lib/emass_client/api/containers_api.rb lib/emass_client/api/controls_api.rb +lib/emass_client/api/dashboards_api.rb lib/emass_client/api/milestones_api.rb lib/emass_client/api/pac_api.rb lib/emass_client/api/poam_api.rb @@ -250,6 +253,7 @@ spec/api/cloud_resources_api_spec.rb spec/api/cmmc_assessments_api_spec.rb spec/api/containers_api_spec.rb spec/api/controls_api_spec.rb +spec/api/dashboards_api_spec.rb spec/api/milestones_api_spec.rb spec/api/pac_api_spec.rb spec/api/poam_api_spec.rb diff --git a/src/ruby_client/.openapi-generator/VERSION b/src/ruby_client/.openapi-generator/VERSION index 89648de3..7b7e20b5 100644 --- a/src/ruby_client/.openapi-generator/VERSION +++ b/src/ruby_client/.openapi-generator/VERSION @@ -1 +1 @@ -6.0.1-SNAPSHOT \ No newline at end of file +6.1.1-SNAPSHOT \ No newline at end of file diff --git a/src/ruby_client/.travis.yml b/src/ruby_client/.travis.yml index 318d4b7c..b594e00d 100644 --- a/src/ruby_client/.travis.yml +++ b/src/ruby_client/.travis.yml @@ -11,4 +11,4 @@ script: - bundle install --path vendor/bundle - bundle exec rspec - gem build emass_client.gemspec - - gem install ./emass_client-1.0.6.gem + - gem install ./emass_client-3.4.0.gem diff --git a/src/ruby_client/README.md b/src/ruby_client/README.md index df245be7..96ce669d 100644 --- a/src/ruby_client/README.md +++ b/src/ruby_client/README.md @@ -53,8 +53,8 @@ To establish an account with eMASS and/or acquire an api-key/user-uid, contact o This SDK is automatically generated by the [OpenAPI Generator](https://openapi-generator.tech) project: -- API version: v3.3 -- Package version: 1.0.6 +- API version: v3.4 +- Package version: 3.4.0 - Build package: org.openapitools.codegen.languages.RubyClientCodegen For more information, please visit [https://www.dcsa.mil/is/emass/](https://www.dcsa.mil/is/emass/) @@ -71,16 +71,16 @@ gem build emass_client.gemspec Then either install the gem locally: ```shell -gem install ./emass_client-1.0.6.gem +gem install ./emass_client-3.4.0.gem ``` -(for development, run `gem install --dev ./emass_client-1.0.6.gem` to install the development dependencies) +(for development, run `gem install --dev ./emass_client-3.4.0.gem` to install the development dependencies) or publish the gem to a gem hosting service, e.g. [RubyGems](https://rubygems.org/). Finally add this to the Gemfile: - gem 'emass_client', '~> 1.0.6' + gem 'emass_client', '~> 3.4.0' ### Install from Git @@ -159,6 +159,22 @@ Class | Method | HTTP request | Description *EmassClient::ContainersApi* | [**add_container_sans_by_system_id**](docs/ContainersApi.md#add_container_sans_by_system_id) | **POST** /api/systems/{systemId}/container-scan-results | Add one or many containers and their scan results *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 *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 +*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 +*EmassClient::DashboardsApi* | [**get_system_associations_details**](docs/DashboardsApi.md#get_system_associations_details) | **GET** /api/dashboards/system-associations-details | Get dashboard information +*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 +*EmassClient::DashboardsApi* | [**get_system_hardware_details**](docs/DashboardsApi.md#get_system_hardware_details) | **GET** /api/dashboards/system-hardware-details | Get dashboard information +*EmassClient::DashboardsApi* | [**get_system_hardware_summary**](docs/DashboardsApi.md#get_system_hardware_summary) | **GET** /api/dashboards/system-hardware-summary | Get dashboard information +*EmassClient::DashboardsApi* | [**get_system_poam_details**](docs/DashboardsApi.md#get_system_poam_details) | **GET** /api/dashboards/system-poam-details | Get dashboard information +*EmassClient::DashboardsApi* | [**get_system_poam_summary**](docs/DashboardsApi.md#get_system_poam_summary) | **GET** /api/dashboards/system-poam-summary | Get dashboard information +*EmassClient::DashboardsApi* | [**get_system_privacy_summary**](docs/DashboardsApi.md#get_system_privacy_summary) | **GET** /api/dashboards/system-privacy-summary | Get dashboard information +*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 +*EmassClient::DashboardsApi* | [**get_system_status_details**](docs/DashboardsApi.md#get_system_status_details) | **GET** /api/dashboards/system-status-details | Get dashboard information +*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 +*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 +*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 +*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 +*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 +*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 *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 *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 *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 diff --git a/src/ruby_client/docs/DashboardsApi.md b/src/ruby_client/docs/DashboardsApi.md new file mode 100644 index 00000000..ef04e57e --- /dev/null +++ b/src/ruby_client/docs/DashboardsApi.md @@ -0,0 +1,1415 @@ +# EmassClient::DashboardsApi + +All URIs are relative to *http://localhost:4010* + +| Method | HTTP request | Description | +| ------ | ------------ | ----------- | +| [**get_system_assessment_procedures_details**](DashboardsApi.md#get_system_assessment_procedures_details) | **GET** /api/dashboards/system-assessment-procedures-details | Get dashboard information | +| [**get_system_associations_details**](DashboardsApi.md#get_system_associations_details) | **GET** /api/dashboards/system-associations-details | Get dashboard information | +| [**get_system_control_compliance_summary**](DashboardsApi.md#get_system_control_compliance_summary) | **GET** /api/dashboards/system-control-compliance-summary | Get dashboard information | +| [**get_system_hardware_details**](DashboardsApi.md#get_system_hardware_details) | **GET** /api/dashboards/system-hardware-details | Get dashboard information | +| [**get_system_hardware_summary**](DashboardsApi.md#get_system_hardware_summary) | **GET** /api/dashboards/system-hardware-summary | Get dashboard information | +| [**get_system_poam_details**](DashboardsApi.md#get_system_poam_details) | **GET** /api/dashboards/system-poam-details | Get dashboard information | +| [**get_system_poam_summary**](DashboardsApi.md#get_system_poam_summary) | **GET** /api/dashboards/system-poam-summary | Get dashboard information | +| [**get_system_privacy_summary**](DashboardsApi.md#get_system_privacy_summary) | **GET** /api/dashboards/system-privacy-summary | Get dashboard information | +| [**get_system_security_control_details**](DashboardsApi.md#get_system_security_control_details) | **GET** /api/dashboards/system-security-controls-details | Get dashboard information | +| [**get_system_status_details**](DashboardsApi.md#get_system_status_details) | **GET** /api/dashboards/system-status-details | Get dashboard information | +| [**get_user_system_assignments_details**](DashboardsApi.md#get_user_system_assignments_details) | **GET** /api/dashboards/user-system-assignments-details | Get dashboard information | +| [**get_va_omb_fsma_saop_summary**](DashboardsApi.md#get_va_omb_fsma_saop_summary) | **GET** /api/dashboards/va-omb-fisma-saop-summary | Get dashboard information | +| [**get_va_system_a2_summary**](DashboardsApi.md#get_va_system_a2_summary) | **GET** /api/dashboards/va-system-a2-summary | Get dashboard information | +| [**get_va_system_aa_summary**](DashboardsApi.md#get_va_system_aa_summary) | **GET** /api/dashboards/va-system-aa-summary | Get dashboard information | +| [**get_va_system_fisma_invetory_summary**](DashboardsApi.md#get_va_system_fisma_invetory_summary) | **GET** /api/dashboards/va-system-fisma-inventory-summary | Get dashboard information | +| [**get_va_system_pl109_reporting_summary**](DashboardsApi.md#get_va_system_pl109_reporting_summary) | **GET** /api/dashboards/va-system-pl-109-reporting-summary | Get dashboard information | + + +## get_system_assessment_procedures_details + +> Object get_system_assessment_procedures_details(org_id, opts) + +Get dashboard information + +Get systems assessement procdures details dashboard information. + +### Examples + +```ruby +require 'time' +require 'emass_client' +# setup authorization +EmassClient.configure do |config| + # Configure API key authorization: apiKey + config.api_key['apiKey'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['apiKey'] = 'Bearer' + + # Configure API key authorization: mockType + config.api_key['mockType'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['mockType'] = 'Bearer' + + # Configure API key authorization: userId + config.api_key['userId'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['userId'] = 'Bearer' +end + +api_instance = EmassClient::DashboardsApi.new +org_id = 1 # Integer | **Organization Id**: The unique organization identifier. +opts = { + page_index: 56, # Integer | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + page_size: 56 # Integer | **Page Size**: If no value is specified, the default returns 20000 per page. +} + +begin + # Get dashboard information + result = api_instance.get_system_assessment_procedures_details(org_id, opts) + p result +rescue EmassClient::ApiError => e + puts "Error when calling DashboardsApi->get_system_assessment_procedures_details: #{e}" +end +``` + +#### Using the get_system_assessment_procedures_details_with_http_info variant + +This returns an Array which contains the response data, status code and headers. + +> get_system_assessment_procedures_details_with_http_info(org_id, opts) + +```ruby +begin + # Get dashboard information + data, status_code, headers = api_instance.get_system_assessment_procedures_details_with_http_info(org_id, opts) + p status_code # => 2xx + p headers # => { ... } + p data # => Object +rescue EmassClient::ApiError => e + puts "Error when calling DashboardsApi->get_system_assessment_procedures_details_with_http_info: #{e}" +end +``` + +### Parameters + +| Name | Type | Description | Notes | +| ---- | ---- | ----------- | ----- | +| **org_id** | **Integer** | **Organization Id**: The unique organization identifier. | | +| **page_index** | **Integer** | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. | [optional][default to 0] | +| **page_size** | **Integer** | **Page Size**: If no value is specified, the default returns 20000 per page. | [optional][default to 20000] | + +### Return type + +**Object** + +### Authorization + +[apiKey](../README.md#apiKey), [mockType](../README.md#mockType), [userId](../README.md#userId) + +### HTTP request headers + +- **Content-Type**: Not defined +- **Accept**: application/json + + +## get_system_associations_details + +> Object get_system_associations_details(org_id, opts) + +Get dashboard information + +Get system associations details dashboard information. + +### Examples + +```ruby +require 'time' +require 'emass_client' +# setup authorization +EmassClient.configure do |config| + # Configure API key authorization: apiKey + config.api_key['apiKey'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['apiKey'] = 'Bearer' + + # Configure API key authorization: mockType + config.api_key['mockType'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['mockType'] = 'Bearer' + + # Configure API key authorization: userId + config.api_key['userId'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['userId'] = 'Bearer' +end + +api_instance = EmassClient::DashboardsApi.new +org_id = 1 # Integer | **Organization Id**: The unique organization identifier. +opts = { + page_index: 56, # Integer | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + page_size: 56 # Integer | **Page Size**: If no value is specified, the default returns 20000 per page. +} + +begin + # Get dashboard information + result = api_instance.get_system_associations_details(org_id, opts) + p result +rescue EmassClient::ApiError => e + puts "Error when calling DashboardsApi->get_system_associations_details: #{e}" +end +``` + +#### Using the get_system_associations_details_with_http_info variant + +This returns an Array which contains the response data, status code and headers. + +> get_system_associations_details_with_http_info(org_id, opts) + +```ruby +begin + # Get dashboard information + data, status_code, headers = api_instance.get_system_associations_details_with_http_info(org_id, opts) + p status_code # => 2xx + p headers # => { ... } + p data # => Object +rescue EmassClient::ApiError => e + puts "Error when calling DashboardsApi->get_system_associations_details_with_http_info: #{e}" +end +``` + +### Parameters + +| Name | Type | Description | Notes | +| ---- | ---- | ----------- | ----- | +| **org_id** | **Integer** | **Organization Id**: The unique organization identifier. | | +| **page_index** | **Integer** | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. | [optional][default to 0] | +| **page_size** | **Integer** | **Page Size**: If no value is specified, the default returns 20000 per page. | [optional][default to 20000] | + +### Return type + +**Object** + +### Authorization + +[apiKey](../README.md#apiKey), [mockType](../README.md#mockType), [userId](../README.md#userId) + +### HTTP request headers + +- **Content-Type**: Not defined +- **Accept**: application/json + + +## get_system_control_compliance_summary + +> Object get_system_control_compliance_summary(org_id, opts) + +Get dashboard information + +Get systems control compliance summary dashboard information. + +### Examples + +```ruby +require 'time' +require 'emass_client' +# setup authorization +EmassClient.configure do |config| + # Configure API key authorization: apiKey + config.api_key['apiKey'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['apiKey'] = 'Bearer' + + # Configure API key authorization: mockType + config.api_key['mockType'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['mockType'] = 'Bearer' + + # Configure API key authorization: userId + config.api_key['userId'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['userId'] = 'Bearer' +end + +api_instance = EmassClient::DashboardsApi.new +org_id = 1 # Integer | **Organization Id**: The unique organization identifier. +opts = { + page_index: 56, # Integer | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + page_size: 56 # Integer | **Page Size**: If no value is specified, the default returns 20000 per page. +} + +begin + # Get dashboard information + result = api_instance.get_system_control_compliance_summary(org_id, opts) + p result +rescue EmassClient::ApiError => e + puts "Error when calling DashboardsApi->get_system_control_compliance_summary: #{e}" +end +``` + +#### Using the get_system_control_compliance_summary_with_http_info variant + +This returns an Array which contains the response data, status code and headers. + +> get_system_control_compliance_summary_with_http_info(org_id, opts) + +```ruby +begin + # Get dashboard information + data, status_code, headers = api_instance.get_system_control_compliance_summary_with_http_info(org_id, opts) + p status_code # => 2xx + p headers # => { ... } + p data # => Object +rescue EmassClient::ApiError => e + puts "Error when calling DashboardsApi->get_system_control_compliance_summary_with_http_info: #{e}" +end +``` + +### Parameters + +| Name | Type | Description | Notes | +| ---- | ---- | ----------- | ----- | +| **org_id** | **Integer** | **Organization Id**: The unique organization identifier. | | +| **page_index** | **Integer** | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. | [optional][default to 0] | +| **page_size** | **Integer** | **Page Size**: If no value is specified, the default returns 20000 per page. | [optional][default to 20000] | + +### Return type + +**Object** + +### Authorization + +[apiKey](../README.md#apiKey), [mockType](../README.md#mockType), [userId](../README.md#userId) + +### HTTP request headers + +- **Content-Type**: Not defined +- **Accept**: application/json + + +## get_system_hardware_details + +> Object get_system_hardware_details(org_id, opts) + +Get dashboard information + +Get system hardware details dashboard information. + +### Examples + +```ruby +require 'time' +require 'emass_client' +# setup authorization +EmassClient.configure do |config| + # Configure API key authorization: apiKey + config.api_key['apiKey'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['apiKey'] = 'Bearer' + + # Configure API key authorization: mockType + config.api_key['mockType'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['mockType'] = 'Bearer' + + # Configure API key authorization: userId + config.api_key['userId'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['userId'] = 'Bearer' +end + +api_instance = EmassClient::DashboardsApi.new +org_id = 1 # Integer | **Organization Id**: The unique organization identifier. +opts = { + page_index: 56, # Integer | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + page_size: 56 # Integer | **Page Size**: If no value is specified, the default returns 20000 per page. +} + +begin + # Get dashboard information + result = api_instance.get_system_hardware_details(org_id, opts) + p result +rescue EmassClient::ApiError => e + puts "Error when calling DashboardsApi->get_system_hardware_details: #{e}" +end +``` + +#### Using the get_system_hardware_details_with_http_info variant + +This returns an Array which contains the response data, status code and headers. + +> get_system_hardware_details_with_http_info(org_id, opts) + +```ruby +begin + # Get dashboard information + data, status_code, headers = api_instance.get_system_hardware_details_with_http_info(org_id, opts) + p status_code # => 2xx + p headers # => { ... } + p data # => Object +rescue EmassClient::ApiError => e + puts "Error when calling DashboardsApi->get_system_hardware_details_with_http_info: #{e}" +end +``` + +### Parameters + +| Name | Type | Description | Notes | +| ---- | ---- | ----------- | ----- | +| **org_id** | **Integer** | **Organization Id**: The unique organization identifier. | | +| **page_index** | **Integer** | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. | [optional][default to 0] | +| **page_size** | **Integer** | **Page Size**: If no value is specified, the default returns 20000 per page. | [optional][default to 20000] | + +### Return type + +**Object** + +### Authorization + +[apiKey](../README.md#apiKey), [mockType](../README.md#mockType), [userId](../README.md#userId) + +### HTTP request headers + +- **Content-Type**: Not defined +- **Accept**: application/json + + +## get_system_hardware_summary + +> Object get_system_hardware_summary(org_id, opts) + +Get dashboard information + +Get system hardware summary dashboard information. + +### Examples + +```ruby +require 'time' +require 'emass_client' +# setup authorization +EmassClient.configure do |config| + # Configure API key authorization: apiKey + config.api_key['apiKey'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['apiKey'] = 'Bearer' + + # Configure API key authorization: mockType + config.api_key['mockType'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['mockType'] = 'Bearer' + + # Configure API key authorization: userId + config.api_key['userId'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['userId'] = 'Bearer' +end + +api_instance = EmassClient::DashboardsApi.new +org_id = 1 # Integer | **Organization Id**: The unique organization identifier. +opts = { + page_index: 56, # Integer | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + page_size: 56 # Integer | **Page Size**: If no value is specified, the default returns 20000 per page. +} + +begin + # Get dashboard information + result = api_instance.get_system_hardware_summary(org_id, opts) + p result +rescue EmassClient::ApiError => e + puts "Error when calling DashboardsApi->get_system_hardware_summary: #{e}" +end +``` + +#### Using the get_system_hardware_summary_with_http_info variant + +This returns an Array which contains the response data, status code and headers. + +> get_system_hardware_summary_with_http_info(org_id, opts) + +```ruby +begin + # Get dashboard information + data, status_code, headers = api_instance.get_system_hardware_summary_with_http_info(org_id, opts) + p status_code # => 2xx + p headers # => { ... } + p data # => Object +rescue EmassClient::ApiError => e + puts "Error when calling DashboardsApi->get_system_hardware_summary_with_http_info: #{e}" +end +``` + +### Parameters + +| Name | Type | Description | Notes | +| ---- | ---- | ----------- | ----- | +| **org_id** | **Integer** | **Organization Id**: The unique organization identifier. | | +| **page_index** | **Integer** | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. | [optional][default to 0] | +| **page_size** | **Integer** | **Page Size**: If no value is specified, the default returns 20000 per page. | [optional][default to 20000] | + +### Return type + +**Object** + +### Authorization + +[apiKey](../README.md#apiKey), [mockType](../README.md#mockType), [userId](../README.md#userId) + +### HTTP request headers + +- **Content-Type**: Not defined +- **Accept**: application/json + + +## get_system_poam_details + +> Object get_system_poam_details(org_id, opts) + +Get dashboard information + +Get system POA&Ms details dashboard information. + +### Examples + +```ruby +require 'time' +require 'emass_client' +# setup authorization +EmassClient.configure do |config| + # Configure API key authorization: apiKey + config.api_key['apiKey'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['apiKey'] = 'Bearer' + + # Configure API key authorization: mockType + config.api_key['mockType'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['mockType'] = 'Bearer' + + # Configure API key authorization: userId + config.api_key['userId'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['userId'] = 'Bearer' +end + +api_instance = EmassClient::DashboardsApi.new +org_id = 1 # Integer | **Organization Id**: The unique organization identifier. +opts = { + page_index: 56, # Integer | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + page_size: 56 # Integer | **Page Size**: If no value is specified, the default returns 20000 per page. +} + +begin + # Get dashboard information + result = api_instance.get_system_poam_details(org_id, opts) + p result +rescue EmassClient::ApiError => e + puts "Error when calling DashboardsApi->get_system_poam_details: #{e}" +end +``` + +#### Using the get_system_poam_details_with_http_info variant + +This returns an Array which contains the response data, status code and headers. + +> get_system_poam_details_with_http_info(org_id, opts) + +```ruby +begin + # Get dashboard information + data, status_code, headers = api_instance.get_system_poam_details_with_http_info(org_id, opts) + p status_code # => 2xx + p headers # => { ... } + p data # => Object +rescue EmassClient::ApiError => e + puts "Error when calling DashboardsApi->get_system_poam_details_with_http_info: #{e}" +end +``` + +### Parameters + +| Name | Type | Description | Notes | +| ---- | ---- | ----------- | ----- | +| **org_id** | **Integer** | **Organization Id**: The unique organization identifier. | | +| **page_index** | **Integer** | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. | [optional][default to 0] | +| **page_size** | **Integer** | **Page Size**: If no value is specified, the default returns 20000 per page. | [optional][default to 20000] | + +### Return type + +**Object** + +### Authorization + +[apiKey](../README.md#apiKey), [mockType](../README.md#mockType), [userId](../README.md#userId) + +### HTTP request headers + +- **Content-Type**: Not defined +- **Accept**: application/json + + +## get_system_poam_summary + +> Object get_system_poam_summary(org_id, opts) + +Get dashboard information + +Get systems POA&Ms summary dashboard information. + +### Examples + +```ruby +require 'time' +require 'emass_client' +# setup authorization +EmassClient.configure do |config| + # Configure API key authorization: apiKey + config.api_key['apiKey'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['apiKey'] = 'Bearer' + + # Configure API key authorization: mockType + config.api_key['mockType'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['mockType'] = 'Bearer' + + # Configure API key authorization: userId + config.api_key['userId'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['userId'] = 'Bearer' +end + +api_instance = EmassClient::DashboardsApi.new +org_id = 1 # Integer | **Organization Id**: The unique organization identifier. +opts = { + page_index: 56, # Integer | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + page_size: 56 # Integer | **Page Size**: If no value is specified, the default returns 20000 per page. +} + +begin + # Get dashboard information + result = api_instance.get_system_poam_summary(org_id, opts) + p result +rescue EmassClient::ApiError => e + puts "Error when calling DashboardsApi->get_system_poam_summary: #{e}" +end +``` + +#### Using the get_system_poam_summary_with_http_info variant + +This returns an Array which contains the response data, status code and headers. + +> get_system_poam_summary_with_http_info(org_id, opts) + +```ruby +begin + # Get dashboard information + data, status_code, headers = api_instance.get_system_poam_summary_with_http_info(org_id, opts) + p status_code # => 2xx + p headers # => { ... } + p data # => Object +rescue EmassClient::ApiError => e + puts "Error when calling DashboardsApi->get_system_poam_summary_with_http_info: #{e}" +end +``` + +### Parameters + +| Name | Type | Description | Notes | +| ---- | ---- | ----------- | ----- | +| **org_id** | **Integer** | **Organization Id**: The unique organization identifier. | | +| **page_index** | **Integer** | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. | [optional][default to 0] | +| **page_size** | **Integer** | **Page Size**: If no value is specified, the default returns 20000 per page. | [optional][default to 20000] | + +### Return type + +**Object** + +### Authorization + +[apiKey](../README.md#apiKey), [mockType](../README.md#mockType), [userId](../README.md#userId) + +### HTTP request headers + +- **Content-Type**: Not defined +- **Accept**: application/json + + +## get_system_privacy_summary + +> Object get_system_privacy_summary(org_id, opts) + +Get dashboard information + +Get user system privacy summary dashboard information. + +### Examples + +```ruby +require 'time' +require 'emass_client' +# setup authorization +EmassClient.configure do |config| + # Configure API key authorization: apiKey + config.api_key['apiKey'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['apiKey'] = 'Bearer' + + # Configure API key authorization: mockType + config.api_key['mockType'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['mockType'] = 'Bearer' + + # Configure API key authorization: userId + config.api_key['userId'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['userId'] = 'Bearer' +end + +api_instance = EmassClient::DashboardsApi.new +org_id = 1 # Integer | **Organization Id**: The unique organization identifier. +opts = { + page_index: 56, # Integer | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + page_size: 56 # Integer | **Page Size**: If no value is specified, the default returns 20000 per page. +} + +begin + # Get dashboard information + result = api_instance.get_system_privacy_summary(org_id, opts) + p result +rescue EmassClient::ApiError => e + puts "Error when calling DashboardsApi->get_system_privacy_summary: #{e}" +end +``` + +#### Using the get_system_privacy_summary_with_http_info variant + +This returns an Array which contains the response data, status code and headers. + +> get_system_privacy_summary_with_http_info(org_id, opts) + +```ruby +begin + # Get dashboard information + data, status_code, headers = api_instance.get_system_privacy_summary_with_http_info(org_id, opts) + p status_code # => 2xx + p headers # => { ... } + p data # => Object +rescue EmassClient::ApiError => e + puts "Error when calling DashboardsApi->get_system_privacy_summary_with_http_info: #{e}" +end +``` + +### Parameters + +| Name | Type | Description | Notes | +| ---- | ---- | ----------- | ----- | +| **org_id** | **Integer** | **Organization Id**: The unique organization identifier. | | +| **page_index** | **Integer** | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. | [optional][default to 0] | +| **page_size** | **Integer** | **Page Size**: If no value is specified, the default returns 20000 per page. | [optional][default to 20000] | + +### Return type + +**Object** + +### Authorization + +[apiKey](../README.md#apiKey), [mockType](../README.md#mockType), [userId](../README.md#userId) + +### HTTP request headers + +- **Content-Type**: Not defined +- **Accept**: application/json + + +## get_system_security_control_details + +> Object get_system_security_control_details(org_id, opts) + +Get dashboard information + +Get systems security control details dashboard information. + +### Examples + +```ruby +require 'time' +require 'emass_client' +# setup authorization +EmassClient.configure do |config| + # Configure API key authorization: apiKey + config.api_key['apiKey'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['apiKey'] = 'Bearer' + + # Configure API key authorization: mockType + config.api_key['mockType'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['mockType'] = 'Bearer' + + # Configure API key authorization: userId + config.api_key['userId'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['userId'] = 'Bearer' +end + +api_instance = EmassClient::DashboardsApi.new +org_id = 1 # Integer | **Organization Id**: The unique organization identifier. +opts = { + page_index: 56, # Integer | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + page_size: 56 # Integer | **Page Size**: If no value is specified, the default returns 20000 per page. +} + +begin + # Get dashboard information + result = api_instance.get_system_security_control_details(org_id, opts) + p result +rescue EmassClient::ApiError => e + puts "Error when calling DashboardsApi->get_system_security_control_details: #{e}" +end +``` + +#### Using the get_system_security_control_details_with_http_info variant + +This returns an Array which contains the response data, status code and headers. + +> get_system_security_control_details_with_http_info(org_id, opts) + +```ruby +begin + # Get dashboard information + data, status_code, headers = api_instance.get_system_security_control_details_with_http_info(org_id, opts) + p status_code # => 2xx + p headers # => { ... } + p data # => Object +rescue EmassClient::ApiError => e + puts "Error when calling DashboardsApi->get_system_security_control_details_with_http_info: #{e}" +end +``` + +### Parameters + +| Name | Type | Description | Notes | +| ---- | ---- | ----------- | ----- | +| **org_id** | **Integer** | **Organization Id**: The unique organization identifier. | | +| **page_index** | **Integer** | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. | [optional][default to 0] | +| **page_size** | **Integer** | **Page Size**: If no value is specified, the default returns 20000 per page. | [optional][default to 20000] | + +### Return type + +**Object** + +### Authorization + +[apiKey](../README.md#apiKey), [mockType](../README.md#mockType), [userId](../README.md#userId) + +### HTTP request headers + +- **Content-Type**: Not defined +- **Accept**: application/json + + +## get_system_status_details + +> Object get_system_status_details(org_id, opts) + +Get dashboard information + +Get systems status detail dashboard information. + +### Examples + +```ruby +require 'time' +require 'emass_client' +# setup authorization +EmassClient.configure do |config| + # Configure API key authorization: apiKey + config.api_key['apiKey'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['apiKey'] = 'Bearer' + + # Configure API key authorization: mockType + config.api_key['mockType'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['mockType'] = 'Bearer' + + # Configure API key authorization: userId + config.api_key['userId'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['userId'] = 'Bearer' +end + +api_instance = EmassClient::DashboardsApi.new +org_id = 1 # Integer | **Organization Id**: The unique organization identifier. +opts = { + page_index: 56, # Integer | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + page_size: 56 # Integer | **Page Size**: If no value is specified, the default returns 20000 per page. +} + +begin + # Get dashboard information + result = api_instance.get_system_status_details(org_id, opts) + p result +rescue EmassClient::ApiError => e + puts "Error when calling DashboardsApi->get_system_status_details: #{e}" +end +``` + +#### Using the get_system_status_details_with_http_info variant + +This returns an Array which contains the response data, status code and headers. + +> get_system_status_details_with_http_info(org_id, opts) + +```ruby +begin + # Get dashboard information + data, status_code, headers = api_instance.get_system_status_details_with_http_info(org_id, opts) + p status_code # => 2xx + p headers # => { ... } + p data # => Object +rescue EmassClient::ApiError => e + puts "Error when calling DashboardsApi->get_system_status_details_with_http_info: #{e}" +end +``` + +### Parameters + +| Name | Type | Description | Notes | +| ---- | ---- | ----------- | ----- | +| **org_id** | **Integer** | **Organization Id**: The unique organization identifier. | | +| **page_index** | **Integer** | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. | [optional][default to 0] | +| **page_size** | **Integer** | **Page Size**: If no value is specified, the default returns 20000 per page. | [optional][default to 20000] | + +### Return type + +**Object** + +### Authorization + +[apiKey](../README.md#apiKey), [mockType](../README.md#mockType), [userId](../README.md#userId) + +### HTTP request headers + +- **Content-Type**: Not defined +- **Accept**: application/json + + +## get_user_system_assignments_details + +> Object get_user_system_assignments_details(org_id, opts) + +Get dashboard information + +Get user system assignments details dashboard information. + +### Examples + +```ruby +require 'time' +require 'emass_client' +# setup authorization +EmassClient.configure do |config| + # Configure API key authorization: apiKey + config.api_key['apiKey'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['apiKey'] = 'Bearer' + + # Configure API key authorization: mockType + config.api_key['mockType'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['mockType'] = 'Bearer' + + # Configure API key authorization: userId + config.api_key['userId'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['userId'] = 'Bearer' +end + +api_instance = EmassClient::DashboardsApi.new +org_id = 1 # Integer | **Organization Id**: The unique organization identifier. +opts = { + page_index: 56, # Integer | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + page_size: 56 # Integer | **Page Size**: If no value is specified, the default returns 20000 per page. +} + +begin + # Get dashboard information + result = api_instance.get_user_system_assignments_details(org_id, opts) + p result +rescue EmassClient::ApiError => e + puts "Error when calling DashboardsApi->get_user_system_assignments_details: #{e}" +end +``` + +#### Using the get_user_system_assignments_details_with_http_info variant + +This returns an Array which contains the response data, status code and headers. + +> get_user_system_assignments_details_with_http_info(org_id, opts) + +```ruby +begin + # Get dashboard information + data, status_code, headers = api_instance.get_user_system_assignments_details_with_http_info(org_id, opts) + p status_code # => 2xx + p headers # => { ... } + p data # => Object +rescue EmassClient::ApiError => e + puts "Error when calling DashboardsApi->get_user_system_assignments_details_with_http_info: #{e}" +end +``` + +### Parameters + +| Name | Type | Description | Notes | +| ---- | ---- | ----------- | ----- | +| **org_id** | **Integer** | **Organization Id**: The unique organization identifier. | | +| **page_index** | **Integer** | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. | [optional][default to 0] | +| **page_size** | **Integer** | **Page Size**: If no value is specified, the default returns 20000 per page. | [optional][default to 20000] | + +### Return type + +**Object** + +### Authorization + +[apiKey](../README.md#apiKey), [mockType](../README.md#mockType), [userId](../README.md#userId) + +### HTTP request headers + +- **Content-Type**: Not defined +- **Accept**: application/json + + +## get_va_omb_fsma_saop_summary + +> Object get_va_omb_fsma_saop_summary(org_id, opts) + +Get dashboard information + +Get VA OMB-FISMA SAOP summary dashboard information. + +### Examples + +```ruby +require 'time' +require 'emass_client' +# setup authorization +EmassClient.configure do |config| + # Configure API key authorization: apiKey + config.api_key['apiKey'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['apiKey'] = 'Bearer' + + # Configure API key authorization: mockType + config.api_key['mockType'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['mockType'] = 'Bearer' + + # Configure API key authorization: userId + config.api_key['userId'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['userId'] = 'Bearer' +end + +api_instance = EmassClient::DashboardsApi.new +org_id = 1 # Integer | **Organization Id**: The unique organization identifier. +opts = { + page_index: 56, # Integer | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + page_size: 56 # Integer | **Page Size**: If no value is specified, the default returns 20000 per page. +} + +begin + # Get dashboard information + result = api_instance.get_va_omb_fsma_saop_summary(org_id, opts) + p result +rescue EmassClient::ApiError => e + puts "Error when calling DashboardsApi->get_va_omb_fsma_saop_summary: #{e}" +end +``` + +#### Using the get_va_omb_fsma_saop_summary_with_http_info variant + +This returns an Array which contains the response data, status code and headers. + +> get_va_omb_fsma_saop_summary_with_http_info(org_id, opts) + +```ruby +begin + # Get dashboard information + data, status_code, headers = api_instance.get_va_omb_fsma_saop_summary_with_http_info(org_id, opts) + p status_code # => 2xx + p headers # => { ... } + p data # => Object +rescue EmassClient::ApiError => e + puts "Error when calling DashboardsApi->get_va_omb_fsma_saop_summary_with_http_info: #{e}" +end +``` + +### Parameters + +| Name | Type | Description | Notes | +| ---- | ---- | ----------- | ----- | +| **org_id** | **Integer** | **Organization Id**: The unique organization identifier. | | +| **page_index** | **Integer** | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. | [optional][default to 0] | +| **page_size** | **Integer** | **Page Size**: If no value is specified, the default returns 20000 per page. | [optional][default to 20000] | + +### Return type + +**Object** + +### Authorization + +[apiKey](../README.md#apiKey), [mockType](../README.md#mockType), [userId](../README.md#userId) + +### HTTP request headers + +- **Content-Type**: Not defined +- **Accept**: application/json + + +## get_va_system_a2_summary + +> Object get_va_system_a2_summary(org_id, opts) + +Get dashboard information + +Get VA system A2.0 summary dashboard information. + +### Examples + +```ruby +require 'time' +require 'emass_client' +# setup authorization +EmassClient.configure do |config| + # Configure API key authorization: apiKey + config.api_key['apiKey'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['apiKey'] = 'Bearer' + + # Configure API key authorization: mockType + config.api_key['mockType'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['mockType'] = 'Bearer' + + # Configure API key authorization: userId + config.api_key['userId'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['userId'] = 'Bearer' +end + +api_instance = EmassClient::DashboardsApi.new +org_id = 1 # Integer | **Organization Id**: The unique organization identifier. +opts = { + page_index: 56, # Integer | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + page_size: 56 # Integer | **Page Size**: If no value is specified, the default returns 20000 per page. +} + +begin + # Get dashboard information + result = api_instance.get_va_system_a2_summary(org_id, opts) + p result +rescue EmassClient::ApiError => e + puts "Error when calling DashboardsApi->get_va_system_a2_summary: #{e}" +end +``` + +#### Using the get_va_system_a2_summary_with_http_info variant + +This returns an Array which contains the response data, status code and headers. + +> get_va_system_a2_summary_with_http_info(org_id, opts) + +```ruby +begin + # Get dashboard information + data, status_code, headers = api_instance.get_va_system_a2_summary_with_http_info(org_id, opts) + p status_code # => 2xx + p headers # => { ... } + p data # => Object +rescue EmassClient::ApiError => e + puts "Error when calling DashboardsApi->get_va_system_a2_summary_with_http_info: #{e}" +end +``` + +### Parameters + +| Name | Type | Description | Notes | +| ---- | ---- | ----------- | ----- | +| **org_id** | **Integer** | **Organization Id**: The unique organization identifier. | | +| **page_index** | **Integer** | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. | [optional][default to 0] | +| **page_size** | **Integer** | **Page Size**: If no value is specified, the default returns 20000 per page. | [optional][default to 20000] | + +### Return type + +**Object** + +### Authorization + +[apiKey](../README.md#apiKey), [mockType](../README.md#mockType), [userId](../README.md#userId) + +### HTTP request headers + +- **Content-Type**: Not defined +- **Accept**: application/json + + +## get_va_system_aa_summary + +> Object get_va_system_aa_summary(org_id, opts) + +Get dashboard information + +Get VA system A&A summary dashboard information. + +### Examples + +```ruby +require 'time' +require 'emass_client' +# setup authorization +EmassClient.configure do |config| + # Configure API key authorization: apiKey + config.api_key['apiKey'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['apiKey'] = 'Bearer' + + # Configure API key authorization: mockType + config.api_key['mockType'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['mockType'] = 'Bearer' + + # Configure API key authorization: userId + config.api_key['userId'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['userId'] = 'Bearer' +end + +api_instance = EmassClient::DashboardsApi.new +org_id = 1 # Integer | **Organization Id**: The unique organization identifier. +opts = { + page_index: 56, # Integer | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + page_size: 56 # Integer | **Page Size**: If no value is specified, the default returns 20000 per page. +} + +begin + # Get dashboard information + result = api_instance.get_va_system_aa_summary(org_id, opts) + p result +rescue EmassClient::ApiError => e + puts "Error when calling DashboardsApi->get_va_system_aa_summary: #{e}" +end +``` + +#### Using the get_va_system_aa_summary_with_http_info variant + +This returns an Array which contains the response data, status code and headers. + +> get_va_system_aa_summary_with_http_info(org_id, opts) + +```ruby +begin + # Get dashboard information + data, status_code, headers = api_instance.get_va_system_aa_summary_with_http_info(org_id, opts) + p status_code # => 2xx + p headers # => { ... } + p data # => Object +rescue EmassClient::ApiError => e + puts "Error when calling DashboardsApi->get_va_system_aa_summary_with_http_info: #{e}" +end +``` + +### Parameters + +| Name | Type | Description | Notes | +| ---- | ---- | ----------- | ----- | +| **org_id** | **Integer** | **Organization Id**: The unique organization identifier. | | +| **page_index** | **Integer** | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. | [optional][default to 0] | +| **page_size** | **Integer** | **Page Size**: If no value is specified, the default returns 20000 per page. | [optional][default to 20000] | + +### Return type + +**Object** + +### Authorization + +[apiKey](../README.md#apiKey), [mockType](../README.md#mockType), [userId](../README.md#userId) + +### HTTP request headers + +- **Content-Type**: Not defined +- **Accept**: application/json + + +## get_va_system_fisma_invetory_summary + +> Object get_va_system_fisma_invetory_summary(org_id, opts) + +Get dashboard information + +Get VA system FISMA inventory summary dashboard information. + +### Examples + +```ruby +require 'time' +require 'emass_client' +# setup authorization +EmassClient.configure do |config| + # Configure API key authorization: apiKey + config.api_key['apiKey'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['apiKey'] = 'Bearer' + + # Configure API key authorization: mockType + config.api_key['mockType'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['mockType'] = 'Bearer' + + # Configure API key authorization: userId + config.api_key['userId'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['userId'] = 'Bearer' +end + +api_instance = EmassClient::DashboardsApi.new +org_id = 1 # Integer | **Organization Id**: The unique organization identifier. +opts = { + page_index: 56, # Integer | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + page_size: 56 # Integer | **Page Size**: If no value is specified, the default returns 20000 per page. +} + +begin + # Get dashboard information + result = api_instance.get_va_system_fisma_invetory_summary(org_id, opts) + p result +rescue EmassClient::ApiError => e + puts "Error when calling DashboardsApi->get_va_system_fisma_invetory_summary: #{e}" +end +``` + +#### Using the get_va_system_fisma_invetory_summary_with_http_info variant + +This returns an Array which contains the response data, status code and headers. + +> get_va_system_fisma_invetory_summary_with_http_info(org_id, opts) + +```ruby +begin + # Get dashboard information + data, status_code, headers = api_instance.get_va_system_fisma_invetory_summary_with_http_info(org_id, opts) + p status_code # => 2xx + p headers # => { ... } + p data # => Object +rescue EmassClient::ApiError => e + puts "Error when calling DashboardsApi->get_va_system_fisma_invetory_summary_with_http_info: #{e}" +end +``` + +### Parameters + +| Name | Type | Description | Notes | +| ---- | ---- | ----------- | ----- | +| **org_id** | **Integer** | **Organization Id**: The unique organization identifier. | | +| **page_index** | **Integer** | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. | [optional][default to 0] | +| **page_size** | **Integer** | **Page Size**: If no value is specified, the default returns 20000 per page. | [optional][default to 20000] | + +### Return type + +**Object** + +### Authorization + +[apiKey](../README.md#apiKey), [mockType](../README.md#mockType), [userId](../README.md#userId) + +### HTTP request headers + +- **Content-Type**: Not defined +- **Accept**: application/json + + +## get_va_system_pl109_reporting_summary + +> Object get_va_system_pl109_reporting_summary(org_id, opts) + +Get dashboard information + +Get VA system P.L. 109 reporting summary dashboard information. + +### Examples + +```ruby +require 'time' +require 'emass_client' +# setup authorization +EmassClient.configure do |config| + # Configure API key authorization: apiKey + config.api_key['apiKey'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['apiKey'] = 'Bearer' + + # Configure API key authorization: mockType + config.api_key['mockType'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['mockType'] = 'Bearer' + + # Configure API key authorization: userId + config.api_key['userId'] = 'YOUR API KEY' + # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil) + # config.api_key_prefix['userId'] = 'Bearer' +end + +api_instance = EmassClient::DashboardsApi.new +org_id = 1 # Integer | **Organization Id**: The unique organization identifier. +opts = { + page_index: 56, # Integer | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + page_size: 56 # Integer | **Page Size**: If no value is specified, the default returns 20000 per page. +} + +begin + # Get dashboard information + result = api_instance.get_va_system_pl109_reporting_summary(org_id, opts) + p result +rescue EmassClient::ApiError => e + puts "Error when calling DashboardsApi->get_va_system_pl109_reporting_summary: #{e}" +end +``` + +#### Using the get_va_system_pl109_reporting_summary_with_http_info variant + +This returns an Array which contains the response data, status code and headers. + +> get_va_system_pl109_reporting_summary_with_http_info(org_id, opts) + +```ruby +begin + # Get dashboard information + data, status_code, headers = api_instance.get_va_system_pl109_reporting_summary_with_http_info(org_id, opts) + p status_code # => 2xx + p headers # => { ... } + p data # => Object +rescue EmassClient::ApiError => e + puts "Error when calling DashboardsApi->get_va_system_pl109_reporting_summary_with_http_info: #{e}" +end +``` + +### Parameters + +| Name | Type | Description | Notes | +| ---- | ---- | ----------- | ----- | +| **org_id** | **Integer** | **Organization Id**: The unique organization identifier. | | +| **page_index** | **Integer** | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. | [optional][default to 0] | +| **page_size** | **Integer** | **Page Size**: If no value is specified, the default returns 20000 per page. | [optional][default to 20000] | + +### Return type + +**Object** + +### Authorization + +[apiKey](../README.md#apiKey), [mockType](../README.md#mockType), [userId](../README.md#userId) + +### HTTP request headers + +- **Content-Type**: Not defined +- **Accept**: application/json + diff --git a/src/ruby_client/docs/WorkflowInstancesApi.md b/src/ruby_client/docs/WorkflowInstancesApi.md index 84e62a05..b79810d0 100644 --- a/src/ruby_client/docs/WorkflowInstancesApi.md +++ b/src/ruby_client/docs/WorkflowInstancesApi.md @@ -42,7 +42,7 @@ end api_instance = EmassClient::WorkflowInstancesApi.new opts = { include_comments: true, # Boolean | **Include Comments**: If no value is specified, the default returns true to not include transition comments. Note: Corresponds to the Comments textbox that is required at most workflow transitions. Does not include other text input fields such as Terms / Conditions for Authorization. - page_index: 56, # Integer | **Page Index**: If no value is specified, the default returns true to not include transition comments. + page_index: 56, # Integer | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. **Note:** Pages contain 1000 workflow instances. since_date: '1638764040', # String | **Date**: Filter on authorization/assessment date (Unix date format). Note: Filters off the lastEditedDate field. Note: The authorization/assessment decisions on completed workflows can be edited for up to 30 days after the initial decision is made. status: 'active' # String | **Status**: Filter by status. If no value is specified, the default returns all to include both active and inactive workflows. Note: Any workflows at a current stage of Complete or Cancelled are inactive. Ongoing workflows currently at other stages are active. } @@ -79,7 +79,7 @@ end | Name | Type | Description | Notes | | ---- | ---- | ----------- | ----- | | **include_comments** | **Boolean** | **Include Comments**: If no value is specified, the default returns true to not include transition comments. Note: Corresponds to the Comments textbox that is required at most workflow transitions. Does not include other text input fields such as Terms / Conditions for Authorization. | [optional][default to true] | -| **page_index** | **Integer** | **Page Index**: If no value is specified, the default returns true to not include transition comments. | [optional][default to 0] | +| **page_index** | **Integer** | **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. **Note:** Pages contain 1000 workflow instances. | [optional][default to 0] | | **since_date** | **String** | **Date**: Filter on authorization/assessment date (Unix date format). Note: Filters off the lastEditedDate field. Note: The authorization/assessment decisions on completed workflows can be edited for up to 30 days after the initial decision is made. | [optional] | | **status** | **String** | **Status**: Filter by status. If no value is specified, the default returns all to include both active and inactive workflows. Note: Any workflows at a current stage of Complete or Cancelled are inactive. Ongoing workflows currently at other stages are active. | [optional][default to 'all'] | diff --git a/src/ruby_client/emass_client.gemspec b/src/ruby_client/emass_client.gemspec index d08c0db0..1decc7b2 100644 --- a/src/ruby_client/emass_client.gemspec +++ b/src/ruby_client/emass_client.gemspec @@ -5,10 +5,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client.rb b/src/ruby_client/lib/emass_client.rb index aa6c8750..ca9a0eb3 100644 --- a/src/ruby_client/lib/emass_client.rb +++ b/src/ruby_client/lib/emass_client.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end @@ -123,6 +123,7 @@ require 'emass_client/api/cloud_resources_api' require 'emass_client/api/containers_api' require 'emass_client/api/controls_api' +require 'emass_client/api/dashboards_api' require 'emass_client/api/milestones_api' require 'emass_client/api/pac_api' require 'emass_client/api/poam_api' diff --git a/src/ruby_client/lib/emass_client/api/artifacts_api.rb b/src/ruby_client/lib/emass_client/api/artifacts_api.rb index a40617e7..6743189a 100644 --- a/src/ruby_client/lib/emass_client/api/artifacts_api.rb +++ b/src/ruby_client/lib/emass_client/api/artifacts_api.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/api/artifacts_export_api.rb b/src/ruby_client/lib/emass_client/api/artifacts_export_api.rb index 0501dd61..be2cc3b9 100644 --- a/src/ruby_client/lib/emass_client/api/artifacts_export_api.rb +++ b/src/ruby_client/lib/emass_client/api/artifacts_export_api.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/api/cac_api.rb b/src/ruby_client/lib/emass_client/api/cac_api.rb index 8b4102e4..e158a3e3 100644 --- a/src/ruby_client/lib/emass_client/api/cac_api.rb +++ b/src/ruby_client/lib/emass_client/api/cac_api.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/api/cloud_resources_api.rb b/src/ruby_client/lib/emass_client/api/cloud_resources_api.rb index 6f527e86..f215d394 100644 --- a/src/ruby_client/lib/emass_client/api/cloud_resources_api.rb +++ b/src/ruby_client/lib/emass_client/api/cloud_resources_api.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/api/cmmc_assessments_api.rb b/src/ruby_client/lib/emass_client/api/cmmc_assessments_api.rb index 1436142a..998fe86a 100644 --- a/src/ruby_client/lib/emass_client/api/cmmc_assessments_api.rb +++ b/src/ruby_client/lib/emass_client/api/cmmc_assessments_api.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/api/containers_api.rb b/src/ruby_client/lib/emass_client/api/containers_api.rb index 9acca438..0a62e38d 100644 --- a/src/ruby_client/lib/emass_client/api/containers_api.rb +++ b/src/ruby_client/lib/emass_client/api/containers_api.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/api/controls_api.rb b/src/ruby_client/lib/emass_client/api/controls_api.rb index 048203f5..71aef4af 100644 --- a/src/ruby_client/lib/emass_client/api/controls_api.rb +++ b/src/ruby_client/lib/emass_client/api/controls_api.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/api/dashboards_api.rb b/src/ruby_client/lib/emass_client/api/dashboards_api.rb new file mode 100644 index 00000000..8334146d --- /dev/null +++ b/src/ruby_client/lib/emass_client/api/dashboards_api.rb @@ -0,0 +1,1142 @@ +=begin +#Enterprise Mission Assurance Support Service (eMASS) + +#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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: + +The version of the OpenAPI document: v3.4 +Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil +Generated by: https://openapi-generator.tech +OpenAPI Generator version: 6.1.1-SNAPSHOT + +=end + +require 'cgi' + +module EmassClient + class DashboardsApi + attr_accessor :api_client + + def initialize(api_client = ApiClient.default) + @api_client = api_client + end + # Get dashboard information + # Get systems assessement procdures details dashboard information. + # @param org_id [Integer] **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. (default to 0) + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. (default to 20000) + # @return [Object] + def get_system_assessment_procedures_details(org_id, opts = {}) + data, _status_code, _headers = get_system_assessment_procedures_details_with_http_info(org_id, opts) + data + end + + # Get dashboard information + # Get systems assessement procdures details dashboard information. + # @param org_id [Integer] **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. (default to 0) + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. (default to 20000) + # @return [Array<(Object, Integer, Hash)>] Object data, response status code and response headers + def get_system_assessment_procedures_details_with_http_info(org_id, opts = {}) + if @api_client.config.debugging + @api_client.config.logger.debug 'Calling API: DashboardsApi.get_system_assessment_procedures_details ...' + end + # verify the required parameter 'org_id' is set + if @api_client.config.client_side_validation && org_id.nil? + fail ArgumentError, "Missing the required parameter 'org_id' when calling DashboardsApi.get_system_assessment_procedures_details" + end + # resource path + local_var_path = '/api/dashboards/system-assessment-procedures-details' + + # query parameters + query_params = opts[:query_params] || {} + query_params[:'orgId'] = org_id + query_params[:'pageIndex'] = opts[:'page_index'] if !opts[:'page_index'].nil? + query_params[:'pageSize'] = opts[:'page_size'] if !opts[:'page_size'].nil? + + # header parameters + header_params = opts[:header_params] || {} + # HTTP header 'Accept' (if needed) + header_params['Accept'] = @api_client.select_header_accept(['application/json']) + + # form parameters + form_params = opts[:form_params] || {} + + # http body (model) + post_body = opts[:debug_body] + + # return_type + return_type = opts[:debug_return_type] || 'Object' + + # auth_names + auth_names = opts[:debug_auth_names] || ['apiKey', 'mockType', 'userId'] + + new_options = opts.merge( + :operation => :"DashboardsApi.get_system_assessment_procedures_details", + :header_params => header_params, + :query_params => query_params, + :form_params => form_params, + :body => post_body, + :auth_names => auth_names, + :return_type => return_type + ) + + data, status_code, headers = @api_client.call_api(:GET, local_var_path, new_options) + if @api_client.config.debugging + @api_client.config.logger.debug "API called: DashboardsApi#get_system_assessment_procedures_details\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + end + return data, status_code, headers + end + + # Get dashboard information + # Get system associations details dashboard information. + # @param org_id [Integer] **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. (default to 0) + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. (default to 20000) + # @return [Object] + def get_system_associations_details(org_id, opts = {}) + data, _status_code, _headers = get_system_associations_details_with_http_info(org_id, opts) + data + end + + # Get dashboard information + # Get system associations details dashboard information. + # @param org_id [Integer] **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. (default to 0) + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. (default to 20000) + # @return [Array<(Object, Integer, Hash)>] Object data, response status code and response headers + def get_system_associations_details_with_http_info(org_id, opts = {}) + if @api_client.config.debugging + @api_client.config.logger.debug 'Calling API: DashboardsApi.get_system_associations_details ...' + end + # verify the required parameter 'org_id' is set + if @api_client.config.client_side_validation && org_id.nil? + fail ArgumentError, "Missing the required parameter 'org_id' when calling DashboardsApi.get_system_associations_details" + end + # resource path + local_var_path = '/api/dashboards/system-associations-details' + + # query parameters + query_params = opts[:query_params] || {} + query_params[:'orgId'] = org_id + query_params[:'pageIndex'] = opts[:'page_index'] if !opts[:'page_index'].nil? + query_params[:'pageSize'] = opts[:'page_size'] if !opts[:'page_size'].nil? + + # header parameters + header_params = opts[:header_params] || {} + # HTTP header 'Accept' (if needed) + header_params['Accept'] = @api_client.select_header_accept(['application/json']) + + # form parameters + form_params = opts[:form_params] || {} + + # http body (model) + post_body = opts[:debug_body] + + # return_type + return_type = opts[:debug_return_type] || 'Object' + + # auth_names + auth_names = opts[:debug_auth_names] || ['apiKey', 'mockType', 'userId'] + + new_options = opts.merge( + :operation => :"DashboardsApi.get_system_associations_details", + :header_params => header_params, + :query_params => query_params, + :form_params => form_params, + :body => post_body, + :auth_names => auth_names, + :return_type => return_type + ) + + data, status_code, headers = @api_client.call_api(:GET, local_var_path, new_options) + if @api_client.config.debugging + @api_client.config.logger.debug "API called: DashboardsApi#get_system_associations_details\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + end + return data, status_code, headers + end + + # Get dashboard information + # Get systems control compliance summary dashboard information. + # @param org_id [Integer] **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. (default to 0) + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. (default to 20000) + # @return [Object] + def get_system_control_compliance_summary(org_id, opts = {}) + data, _status_code, _headers = get_system_control_compliance_summary_with_http_info(org_id, opts) + data + end + + # Get dashboard information + # Get systems control compliance summary dashboard information. + # @param org_id [Integer] **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. (default to 0) + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. (default to 20000) + # @return [Array<(Object, Integer, Hash)>] Object data, response status code and response headers + def get_system_control_compliance_summary_with_http_info(org_id, opts = {}) + if @api_client.config.debugging + @api_client.config.logger.debug 'Calling API: DashboardsApi.get_system_control_compliance_summary ...' + end + # verify the required parameter 'org_id' is set + if @api_client.config.client_side_validation && org_id.nil? + fail ArgumentError, "Missing the required parameter 'org_id' when calling DashboardsApi.get_system_control_compliance_summary" + end + # resource path + local_var_path = '/api/dashboards/system-control-compliance-summary' + + # query parameters + query_params = opts[:query_params] || {} + query_params[:'orgId'] = org_id + query_params[:'pageIndex'] = opts[:'page_index'] if !opts[:'page_index'].nil? + query_params[:'pageSize'] = opts[:'page_size'] if !opts[:'page_size'].nil? + + # header parameters + header_params = opts[:header_params] || {} + # HTTP header 'Accept' (if needed) + header_params['Accept'] = @api_client.select_header_accept(['application/json']) + + # form parameters + form_params = opts[:form_params] || {} + + # http body (model) + post_body = opts[:debug_body] + + # return_type + return_type = opts[:debug_return_type] || 'Object' + + # auth_names + auth_names = opts[:debug_auth_names] || ['apiKey', 'mockType', 'userId'] + + new_options = opts.merge( + :operation => :"DashboardsApi.get_system_control_compliance_summary", + :header_params => header_params, + :query_params => query_params, + :form_params => form_params, + :body => post_body, + :auth_names => auth_names, + :return_type => return_type + ) + + data, status_code, headers = @api_client.call_api(:GET, local_var_path, new_options) + if @api_client.config.debugging + @api_client.config.logger.debug "API called: DashboardsApi#get_system_control_compliance_summary\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + end + return data, status_code, headers + end + + # Get dashboard information + # Get system hardware details dashboard information. + # @param org_id [Integer] **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. (default to 0) + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. (default to 20000) + # @return [Object] + def get_system_hardware_details(org_id, opts = {}) + data, _status_code, _headers = get_system_hardware_details_with_http_info(org_id, opts) + data + end + + # Get dashboard information + # Get system hardware details dashboard information. + # @param org_id [Integer] **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. (default to 0) + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. (default to 20000) + # @return [Array<(Object, Integer, Hash)>] Object data, response status code and response headers + def get_system_hardware_details_with_http_info(org_id, opts = {}) + if @api_client.config.debugging + @api_client.config.logger.debug 'Calling API: DashboardsApi.get_system_hardware_details ...' + end + # verify the required parameter 'org_id' is set + if @api_client.config.client_side_validation && org_id.nil? + fail ArgumentError, "Missing the required parameter 'org_id' when calling DashboardsApi.get_system_hardware_details" + end + # resource path + local_var_path = '/api/dashboards/system-hardware-details' + + # query parameters + query_params = opts[:query_params] || {} + query_params[:'orgId'] = org_id + query_params[:'pageIndex'] = opts[:'page_index'] if !opts[:'page_index'].nil? + query_params[:'pageSize'] = opts[:'page_size'] if !opts[:'page_size'].nil? + + # header parameters + header_params = opts[:header_params] || {} + # HTTP header 'Accept' (if needed) + header_params['Accept'] = @api_client.select_header_accept(['application/json']) + + # form parameters + form_params = opts[:form_params] || {} + + # http body (model) + post_body = opts[:debug_body] + + # return_type + return_type = opts[:debug_return_type] || 'Object' + + # auth_names + auth_names = opts[:debug_auth_names] || ['apiKey', 'mockType', 'userId'] + + new_options = opts.merge( + :operation => :"DashboardsApi.get_system_hardware_details", + :header_params => header_params, + :query_params => query_params, + :form_params => form_params, + :body => post_body, + :auth_names => auth_names, + :return_type => return_type + ) + + data, status_code, headers = @api_client.call_api(:GET, local_var_path, new_options) + if @api_client.config.debugging + @api_client.config.logger.debug "API called: DashboardsApi#get_system_hardware_details\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + end + return data, status_code, headers + end + + # Get dashboard information + # Get system hardware summary dashboard information. + # @param org_id [Integer] **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. (default to 0) + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. (default to 20000) + # @return [Object] + def get_system_hardware_summary(org_id, opts = {}) + data, _status_code, _headers = get_system_hardware_summary_with_http_info(org_id, opts) + data + end + + # Get dashboard information + # Get system hardware summary dashboard information. + # @param org_id [Integer] **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. (default to 0) + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. (default to 20000) + # @return [Array<(Object, Integer, Hash)>] Object data, response status code and response headers + def get_system_hardware_summary_with_http_info(org_id, opts = {}) + if @api_client.config.debugging + @api_client.config.logger.debug 'Calling API: DashboardsApi.get_system_hardware_summary ...' + end + # verify the required parameter 'org_id' is set + if @api_client.config.client_side_validation && org_id.nil? + fail ArgumentError, "Missing the required parameter 'org_id' when calling DashboardsApi.get_system_hardware_summary" + end + # resource path + local_var_path = '/api/dashboards/system-hardware-summary' + + # query parameters + query_params = opts[:query_params] || {} + query_params[:'orgId'] = org_id + query_params[:'pageIndex'] = opts[:'page_index'] if !opts[:'page_index'].nil? + query_params[:'pageSize'] = opts[:'page_size'] if !opts[:'page_size'].nil? + + # header parameters + header_params = opts[:header_params] || {} + # HTTP header 'Accept' (if needed) + header_params['Accept'] = @api_client.select_header_accept(['application/json']) + + # form parameters + form_params = opts[:form_params] || {} + + # http body (model) + post_body = opts[:debug_body] + + # return_type + return_type = opts[:debug_return_type] || 'Object' + + # auth_names + auth_names = opts[:debug_auth_names] || ['apiKey', 'mockType', 'userId'] + + new_options = opts.merge( + :operation => :"DashboardsApi.get_system_hardware_summary", + :header_params => header_params, + :query_params => query_params, + :form_params => form_params, + :body => post_body, + :auth_names => auth_names, + :return_type => return_type + ) + + data, status_code, headers = @api_client.call_api(:GET, local_var_path, new_options) + if @api_client.config.debugging + @api_client.config.logger.debug "API called: DashboardsApi#get_system_hardware_summary\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + end + return data, status_code, headers + end + + # Get dashboard information + # Get system POA&Ms details dashboard information. + # @param org_id [Integer] **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. (default to 0) + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. (default to 20000) + # @return [Object] + def get_system_poam_details(org_id, opts = {}) + data, _status_code, _headers = get_system_poam_details_with_http_info(org_id, opts) + data + end + + # Get dashboard information + # Get system POA&Ms details dashboard information. + # @param org_id [Integer] **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. (default to 0) + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. (default to 20000) + # @return [Array<(Object, Integer, Hash)>] Object data, response status code and response headers + def get_system_poam_details_with_http_info(org_id, opts = {}) + if @api_client.config.debugging + @api_client.config.logger.debug 'Calling API: DashboardsApi.get_system_poam_details ...' + end + # verify the required parameter 'org_id' is set + if @api_client.config.client_side_validation && org_id.nil? + fail ArgumentError, "Missing the required parameter 'org_id' when calling DashboardsApi.get_system_poam_details" + end + # resource path + local_var_path = '/api/dashboards/system-poam-details' + + # query parameters + query_params = opts[:query_params] || {} + query_params[:'orgId'] = org_id + query_params[:'pageIndex'] = opts[:'page_index'] if !opts[:'page_index'].nil? + query_params[:'pageSize'] = opts[:'page_size'] if !opts[:'page_size'].nil? + + # header parameters + header_params = opts[:header_params] || {} + # HTTP header 'Accept' (if needed) + header_params['Accept'] = @api_client.select_header_accept(['application/json']) + + # form parameters + form_params = opts[:form_params] || {} + + # http body (model) + post_body = opts[:debug_body] + + # return_type + return_type = opts[:debug_return_type] || 'Object' + + # auth_names + auth_names = opts[:debug_auth_names] || ['apiKey', 'mockType', 'userId'] + + new_options = opts.merge( + :operation => :"DashboardsApi.get_system_poam_details", + :header_params => header_params, + :query_params => query_params, + :form_params => form_params, + :body => post_body, + :auth_names => auth_names, + :return_type => return_type + ) + + data, status_code, headers = @api_client.call_api(:GET, local_var_path, new_options) + if @api_client.config.debugging + @api_client.config.logger.debug "API called: DashboardsApi#get_system_poam_details\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + end + return data, status_code, headers + end + + # Get dashboard information + # Get systems POA&Ms summary dashboard information. + # @param org_id [Integer] **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. (default to 0) + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. (default to 20000) + # @return [Object] + def get_system_poam_summary(org_id, opts = {}) + data, _status_code, _headers = get_system_poam_summary_with_http_info(org_id, opts) + data + end + + # Get dashboard information + # Get systems POA&Ms summary dashboard information. + # @param org_id [Integer] **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. (default to 0) + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. (default to 20000) + # @return [Array<(Object, Integer, Hash)>] Object data, response status code and response headers + def get_system_poam_summary_with_http_info(org_id, opts = {}) + if @api_client.config.debugging + @api_client.config.logger.debug 'Calling API: DashboardsApi.get_system_poam_summary ...' + end + # verify the required parameter 'org_id' is set + if @api_client.config.client_side_validation && org_id.nil? + fail ArgumentError, "Missing the required parameter 'org_id' when calling DashboardsApi.get_system_poam_summary" + end + # resource path + local_var_path = '/api/dashboards/system-poam-summary' + + # query parameters + query_params = opts[:query_params] || {} + query_params[:'orgId'] = org_id + query_params[:'pageIndex'] = opts[:'page_index'] if !opts[:'page_index'].nil? + query_params[:'pageSize'] = opts[:'page_size'] if !opts[:'page_size'].nil? + + # header parameters + header_params = opts[:header_params] || {} + # HTTP header 'Accept' (if needed) + header_params['Accept'] = @api_client.select_header_accept(['application/json']) + + # form parameters + form_params = opts[:form_params] || {} + + # http body (model) + post_body = opts[:debug_body] + + # return_type + return_type = opts[:debug_return_type] || 'Object' + + # auth_names + auth_names = opts[:debug_auth_names] || ['apiKey', 'mockType', 'userId'] + + new_options = opts.merge( + :operation => :"DashboardsApi.get_system_poam_summary", + :header_params => header_params, + :query_params => query_params, + :form_params => form_params, + :body => post_body, + :auth_names => auth_names, + :return_type => return_type + ) + + data, status_code, headers = @api_client.call_api(:GET, local_var_path, new_options) + if @api_client.config.debugging + @api_client.config.logger.debug "API called: DashboardsApi#get_system_poam_summary\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + end + return data, status_code, headers + end + + # Get dashboard information + # Get user system privacy summary dashboard information. + # @param org_id [Integer] **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. (default to 0) + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. (default to 20000) + # @return [Object] + def get_system_privacy_summary(org_id, opts = {}) + data, _status_code, _headers = get_system_privacy_summary_with_http_info(org_id, opts) + data + end + + # Get dashboard information + # Get user system privacy summary dashboard information. + # @param org_id [Integer] **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. (default to 0) + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. (default to 20000) + # @return [Array<(Object, Integer, Hash)>] Object data, response status code and response headers + def get_system_privacy_summary_with_http_info(org_id, opts = {}) + if @api_client.config.debugging + @api_client.config.logger.debug 'Calling API: DashboardsApi.get_system_privacy_summary ...' + end + # verify the required parameter 'org_id' is set + if @api_client.config.client_side_validation && org_id.nil? + fail ArgumentError, "Missing the required parameter 'org_id' when calling DashboardsApi.get_system_privacy_summary" + end + # resource path + local_var_path = '/api/dashboards/system-privacy-summary' + + # query parameters + query_params = opts[:query_params] || {} + query_params[:'orgId'] = org_id + query_params[:'pageIndex'] = opts[:'page_index'] if !opts[:'page_index'].nil? + query_params[:'pageSize'] = opts[:'page_size'] if !opts[:'page_size'].nil? + + # header parameters + header_params = opts[:header_params] || {} + # HTTP header 'Accept' (if needed) + header_params['Accept'] = @api_client.select_header_accept(['application/json']) + + # form parameters + form_params = opts[:form_params] || {} + + # http body (model) + post_body = opts[:debug_body] + + # return_type + return_type = opts[:debug_return_type] || 'Object' + + # auth_names + auth_names = opts[:debug_auth_names] || ['apiKey', 'mockType', 'userId'] + + new_options = opts.merge( + :operation => :"DashboardsApi.get_system_privacy_summary", + :header_params => header_params, + :query_params => query_params, + :form_params => form_params, + :body => post_body, + :auth_names => auth_names, + :return_type => return_type + ) + + data, status_code, headers = @api_client.call_api(:GET, local_var_path, new_options) + if @api_client.config.debugging + @api_client.config.logger.debug "API called: DashboardsApi#get_system_privacy_summary\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + end + return data, status_code, headers + end + + # Get dashboard information + # Get systems security control details dashboard information. + # @param org_id [Integer] **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. (default to 0) + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. (default to 20000) + # @return [Object] + def get_system_security_control_details(org_id, opts = {}) + data, _status_code, _headers = get_system_security_control_details_with_http_info(org_id, opts) + data + end + + # Get dashboard information + # Get systems security control details dashboard information. + # @param org_id [Integer] **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. (default to 0) + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. (default to 20000) + # @return [Array<(Object, Integer, Hash)>] Object data, response status code and response headers + def get_system_security_control_details_with_http_info(org_id, opts = {}) + if @api_client.config.debugging + @api_client.config.logger.debug 'Calling API: DashboardsApi.get_system_security_control_details ...' + end + # verify the required parameter 'org_id' is set + if @api_client.config.client_side_validation && org_id.nil? + fail ArgumentError, "Missing the required parameter 'org_id' when calling DashboardsApi.get_system_security_control_details" + end + # resource path + local_var_path = '/api/dashboards/system-security-controls-details' + + # query parameters + query_params = opts[:query_params] || {} + query_params[:'orgId'] = org_id + query_params[:'pageIndex'] = opts[:'page_index'] if !opts[:'page_index'].nil? + query_params[:'pageSize'] = opts[:'page_size'] if !opts[:'page_size'].nil? + + # header parameters + header_params = opts[:header_params] || {} + # HTTP header 'Accept' (if needed) + header_params['Accept'] = @api_client.select_header_accept(['application/json']) + + # form parameters + form_params = opts[:form_params] || {} + + # http body (model) + post_body = opts[:debug_body] + + # return_type + return_type = opts[:debug_return_type] || 'Object' + + # auth_names + auth_names = opts[:debug_auth_names] || ['apiKey', 'mockType', 'userId'] + + new_options = opts.merge( + :operation => :"DashboardsApi.get_system_security_control_details", + :header_params => header_params, + :query_params => query_params, + :form_params => form_params, + :body => post_body, + :auth_names => auth_names, + :return_type => return_type + ) + + data, status_code, headers = @api_client.call_api(:GET, local_var_path, new_options) + if @api_client.config.debugging + @api_client.config.logger.debug "API called: DashboardsApi#get_system_security_control_details\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + end + return data, status_code, headers + end + + # Get dashboard information + # Get systems status detail dashboard information. + # @param org_id [Integer] **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. (default to 0) + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. (default to 20000) + # @return [Object] + def get_system_status_details(org_id, opts = {}) + data, _status_code, _headers = get_system_status_details_with_http_info(org_id, opts) + data + end + + # Get dashboard information + # Get systems status detail dashboard information. + # @param org_id [Integer] **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. (default to 0) + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. (default to 20000) + # @return [Array<(Object, Integer, Hash)>] Object data, response status code and response headers + def get_system_status_details_with_http_info(org_id, opts = {}) + if @api_client.config.debugging + @api_client.config.logger.debug 'Calling API: DashboardsApi.get_system_status_details ...' + end + # verify the required parameter 'org_id' is set + if @api_client.config.client_side_validation && org_id.nil? + fail ArgumentError, "Missing the required parameter 'org_id' when calling DashboardsApi.get_system_status_details" + end + # resource path + local_var_path = '/api/dashboards/system-status-details' + + # query parameters + query_params = opts[:query_params] || {} + query_params[:'orgId'] = org_id + query_params[:'pageIndex'] = opts[:'page_index'] if !opts[:'page_index'].nil? + query_params[:'pageSize'] = opts[:'page_size'] if !opts[:'page_size'].nil? + + # header parameters + header_params = opts[:header_params] || {} + # HTTP header 'Accept' (if needed) + header_params['Accept'] = @api_client.select_header_accept(['application/json']) + + # form parameters + form_params = opts[:form_params] || {} + + # http body (model) + post_body = opts[:debug_body] + + # return_type + return_type = opts[:debug_return_type] || 'Object' + + # auth_names + auth_names = opts[:debug_auth_names] || ['apiKey', 'mockType', 'userId'] + + new_options = opts.merge( + :operation => :"DashboardsApi.get_system_status_details", + :header_params => header_params, + :query_params => query_params, + :form_params => form_params, + :body => post_body, + :auth_names => auth_names, + :return_type => return_type + ) + + data, status_code, headers = @api_client.call_api(:GET, local_var_path, new_options) + if @api_client.config.debugging + @api_client.config.logger.debug "API called: DashboardsApi#get_system_status_details\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + end + return data, status_code, headers + end + + # Get dashboard information + # Get user system assignments details dashboard information. + # @param org_id [Integer] **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. (default to 0) + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. (default to 20000) + # @return [Object] + def get_user_system_assignments_details(org_id, opts = {}) + data, _status_code, _headers = get_user_system_assignments_details_with_http_info(org_id, opts) + data + end + + # Get dashboard information + # Get user system assignments details dashboard information. + # @param org_id [Integer] **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. (default to 0) + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. (default to 20000) + # @return [Array<(Object, Integer, Hash)>] Object data, response status code and response headers + def get_user_system_assignments_details_with_http_info(org_id, opts = {}) + if @api_client.config.debugging + @api_client.config.logger.debug 'Calling API: DashboardsApi.get_user_system_assignments_details ...' + end + # verify the required parameter 'org_id' is set + if @api_client.config.client_side_validation && org_id.nil? + fail ArgumentError, "Missing the required parameter 'org_id' when calling DashboardsApi.get_user_system_assignments_details" + end + # resource path + local_var_path = '/api/dashboards/user-system-assignments-details' + + # query parameters + query_params = opts[:query_params] || {} + query_params[:'orgId'] = org_id + query_params[:'pageIndex'] = opts[:'page_index'] if !opts[:'page_index'].nil? + query_params[:'pageSize'] = opts[:'page_size'] if !opts[:'page_size'].nil? + + # header parameters + header_params = opts[:header_params] || {} + # HTTP header 'Accept' (if needed) + header_params['Accept'] = @api_client.select_header_accept(['application/json']) + + # form parameters + form_params = opts[:form_params] || {} + + # http body (model) + post_body = opts[:debug_body] + + # return_type + return_type = opts[:debug_return_type] || 'Object' + + # auth_names + auth_names = opts[:debug_auth_names] || ['apiKey', 'mockType', 'userId'] + + new_options = opts.merge( + :operation => :"DashboardsApi.get_user_system_assignments_details", + :header_params => header_params, + :query_params => query_params, + :form_params => form_params, + :body => post_body, + :auth_names => auth_names, + :return_type => return_type + ) + + data, status_code, headers = @api_client.call_api(:GET, local_var_path, new_options) + if @api_client.config.debugging + @api_client.config.logger.debug "API called: DashboardsApi#get_user_system_assignments_details\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + end + return data, status_code, headers + end + + # Get dashboard information + # Get VA OMB-FISMA SAOP summary dashboard information. + # @param org_id [Integer] **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. (default to 0) + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. (default to 20000) + # @return [Object] + def get_va_omb_fsma_saop_summary(org_id, opts = {}) + data, _status_code, _headers = get_va_omb_fsma_saop_summary_with_http_info(org_id, opts) + data + end + + # Get dashboard information + # Get VA OMB-FISMA SAOP summary dashboard information. + # @param org_id [Integer] **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. (default to 0) + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. (default to 20000) + # @return [Array<(Object, Integer, Hash)>] Object data, response status code and response headers + def get_va_omb_fsma_saop_summary_with_http_info(org_id, opts = {}) + if @api_client.config.debugging + @api_client.config.logger.debug 'Calling API: DashboardsApi.get_va_omb_fsma_saop_summary ...' + end + # verify the required parameter 'org_id' is set + if @api_client.config.client_side_validation && org_id.nil? + fail ArgumentError, "Missing the required parameter 'org_id' when calling DashboardsApi.get_va_omb_fsma_saop_summary" + end + # resource path + local_var_path = '/api/dashboards/va-omb-fisma-saop-summary' + + # query parameters + query_params = opts[:query_params] || {} + query_params[:'orgId'] = org_id + query_params[:'pageIndex'] = opts[:'page_index'] if !opts[:'page_index'].nil? + query_params[:'pageSize'] = opts[:'page_size'] if !opts[:'page_size'].nil? + + # header parameters + header_params = opts[:header_params] || {} + # HTTP header 'Accept' (if needed) + header_params['Accept'] = @api_client.select_header_accept(['application/json']) + + # form parameters + form_params = opts[:form_params] || {} + + # http body (model) + post_body = opts[:debug_body] + + # return_type + return_type = opts[:debug_return_type] || 'Object' + + # auth_names + auth_names = opts[:debug_auth_names] || ['apiKey', 'mockType', 'userId'] + + new_options = opts.merge( + :operation => :"DashboardsApi.get_va_omb_fsma_saop_summary", + :header_params => header_params, + :query_params => query_params, + :form_params => form_params, + :body => post_body, + :auth_names => auth_names, + :return_type => return_type + ) + + data, status_code, headers = @api_client.call_api(:GET, local_var_path, new_options) + if @api_client.config.debugging + @api_client.config.logger.debug "API called: DashboardsApi#get_va_omb_fsma_saop_summary\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + end + return data, status_code, headers + end + + # Get dashboard information + # Get VA system A2.0 summary dashboard information. + # @param org_id [Integer] **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. (default to 0) + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. (default to 20000) + # @return [Object] + def get_va_system_a2_summary(org_id, opts = {}) + data, _status_code, _headers = get_va_system_a2_summary_with_http_info(org_id, opts) + data + end + + # Get dashboard information + # Get VA system A2.0 summary dashboard information. + # @param org_id [Integer] **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. (default to 0) + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. (default to 20000) + # @return [Array<(Object, Integer, Hash)>] Object data, response status code and response headers + def get_va_system_a2_summary_with_http_info(org_id, opts = {}) + if @api_client.config.debugging + @api_client.config.logger.debug 'Calling API: DashboardsApi.get_va_system_a2_summary ...' + end + # verify the required parameter 'org_id' is set + if @api_client.config.client_side_validation && org_id.nil? + fail ArgumentError, "Missing the required parameter 'org_id' when calling DashboardsApi.get_va_system_a2_summary" + end + # resource path + local_var_path = '/api/dashboards/va-system-a2-summary' + + # query parameters + query_params = opts[:query_params] || {} + query_params[:'orgId'] = org_id + query_params[:'pageIndex'] = opts[:'page_index'] if !opts[:'page_index'].nil? + query_params[:'pageSize'] = opts[:'page_size'] if !opts[:'page_size'].nil? + + # header parameters + header_params = opts[:header_params] || {} + # HTTP header 'Accept' (if needed) + header_params['Accept'] = @api_client.select_header_accept(['application/json']) + + # form parameters + form_params = opts[:form_params] || {} + + # http body (model) + post_body = opts[:debug_body] + + # return_type + return_type = opts[:debug_return_type] || 'Object' + + # auth_names + auth_names = opts[:debug_auth_names] || ['apiKey', 'mockType', 'userId'] + + new_options = opts.merge( + :operation => :"DashboardsApi.get_va_system_a2_summary", + :header_params => header_params, + :query_params => query_params, + :form_params => form_params, + :body => post_body, + :auth_names => auth_names, + :return_type => return_type + ) + + data, status_code, headers = @api_client.call_api(:GET, local_var_path, new_options) + if @api_client.config.debugging + @api_client.config.logger.debug "API called: DashboardsApi#get_va_system_a2_summary\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + end + return data, status_code, headers + end + + # Get dashboard information + # Get VA system A&A summary dashboard information. + # @param org_id [Integer] **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. (default to 0) + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. (default to 20000) + # @return [Object] + def get_va_system_aa_summary(org_id, opts = {}) + data, _status_code, _headers = get_va_system_aa_summary_with_http_info(org_id, opts) + data + end + + # Get dashboard information + # Get VA system A&A summary dashboard information. + # @param org_id [Integer] **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. (default to 0) + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. (default to 20000) + # @return [Array<(Object, Integer, Hash)>] Object data, response status code and response headers + def get_va_system_aa_summary_with_http_info(org_id, opts = {}) + if @api_client.config.debugging + @api_client.config.logger.debug 'Calling API: DashboardsApi.get_va_system_aa_summary ...' + end + # verify the required parameter 'org_id' is set + if @api_client.config.client_side_validation && org_id.nil? + fail ArgumentError, "Missing the required parameter 'org_id' when calling DashboardsApi.get_va_system_aa_summary" + end + # resource path + local_var_path = '/api/dashboards/va-system-aa-summary' + + # query parameters + query_params = opts[:query_params] || {} + query_params[:'orgId'] = org_id + query_params[:'pageIndex'] = opts[:'page_index'] if !opts[:'page_index'].nil? + query_params[:'pageSize'] = opts[:'page_size'] if !opts[:'page_size'].nil? + + # header parameters + header_params = opts[:header_params] || {} + # HTTP header 'Accept' (if needed) + header_params['Accept'] = @api_client.select_header_accept(['application/json']) + + # form parameters + form_params = opts[:form_params] || {} + + # http body (model) + post_body = opts[:debug_body] + + # return_type + return_type = opts[:debug_return_type] || 'Object' + + # auth_names + auth_names = opts[:debug_auth_names] || ['apiKey', 'mockType', 'userId'] + + new_options = opts.merge( + :operation => :"DashboardsApi.get_va_system_aa_summary", + :header_params => header_params, + :query_params => query_params, + :form_params => form_params, + :body => post_body, + :auth_names => auth_names, + :return_type => return_type + ) + + data, status_code, headers = @api_client.call_api(:GET, local_var_path, new_options) + if @api_client.config.debugging + @api_client.config.logger.debug "API called: DashboardsApi#get_va_system_aa_summary\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + end + return data, status_code, headers + end + + # Get dashboard information + # Get VA system FISMA inventory summary dashboard information. + # @param org_id [Integer] **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. (default to 0) + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. (default to 20000) + # @return [Object] + def get_va_system_fisma_invetory_summary(org_id, opts = {}) + data, _status_code, _headers = get_va_system_fisma_invetory_summary_with_http_info(org_id, opts) + data + end + + # Get dashboard information + # Get VA system FISMA inventory summary dashboard information. + # @param org_id [Integer] **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. (default to 0) + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. (default to 20000) + # @return [Array<(Object, Integer, Hash)>] Object data, response status code and response headers + def get_va_system_fisma_invetory_summary_with_http_info(org_id, opts = {}) + if @api_client.config.debugging + @api_client.config.logger.debug 'Calling API: DashboardsApi.get_va_system_fisma_invetory_summary ...' + end + # verify the required parameter 'org_id' is set + if @api_client.config.client_side_validation && org_id.nil? + fail ArgumentError, "Missing the required parameter 'org_id' when calling DashboardsApi.get_va_system_fisma_invetory_summary" + end + # resource path + local_var_path = '/api/dashboards/va-system-fisma-inventory-summary' + + # query parameters + query_params = opts[:query_params] || {} + query_params[:'orgId'] = org_id + query_params[:'pageIndex'] = opts[:'page_index'] if !opts[:'page_index'].nil? + query_params[:'pageSize'] = opts[:'page_size'] if !opts[:'page_size'].nil? + + # header parameters + header_params = opts[:header_params] || {} + # HTTP header 'Accept' (if needed) + header_params['Accept'] = @api_client.select_header_accept(['application/json']) + + # form parameters + form_params = opts[:form_params] || {} + + # http body (model) + post_body = opts[:debug_body] + + # return_type + return_type = opts[:debug_return_type] || 'Object' + + # auth_names + auth_names = opts[:debug_auth_names] || ['apiKey', 'mockType', 'userId'] + + new_options = opts.merge( + :operation => :"DashboardsApi.get_va_system_fisma_invetory_summary", + :header_params => header_params, + :query_params => query_params, + :form_params => form_params, + :body => post_body, + :auth_names => auth_names, + :return_type => return_type + ) + + data, status_code, headers = @api_client.call_api(:GET, local_var_path, new_options) + if @api_client.config.debugging + @api_client.config.logger.debug "API called: DashboardsApi#get_va_system_fisma_invetory_summary\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + end + return data, status_code, headers + end + + # Get dashboard information + # Get VA system P.L. 109 reporting summary dashboard information. + # @param org_id [Integer] **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. (default to 0) + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. (default to 20000) + # @return [Object] + def get_va_system_pl109_reporting_summary(org_id, opts = {}) + data, _status_code, _headers = get_va_system_pl109_reporting_summary_with_http_info(org_id, opts) + data + end + + # Get dashboard information + # Get VA system P.L. 109 reporting summary dashboard information. + # @param org_id [Integer] **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. (default to 0) + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. (default to 20000) + # @return [Array<(Object, Integer, Hash)>] Object data, response status code and response headers + def get_va_system_pl109_reporting_summary_with_http_info(org_id, opts = {}) + if @api_client.config.debugging + @api_client.config.logger.debug 'Calling API: DashboardsApi.get_va_system_pl109_reporting_summary ...' + end + # verify the required parameter 'org_id' is set + if @api_client.config.client_side_validation && org_id.nil? + fail ArgumentError, "Missing the required parameter 'org_id' when calling DashboardsApi.get_va_system_pl109_reporting_summary" + end + # resource path + local_var_path = '/api/dashboards/va-system-pl-109-reporting-summary' + + # query parameters + query_params = opts[:query_params] || {} + query_params[:'orgId'] = org_id + query_params[:'pageIndex'] = opts[:'page_index'] if !opts[:'page_index'].nil? + query_params[:'pageSize'] = opts[:'page_size'] if !opts[:'page_size'].nil? + + # header parameters + header_params = opts[:header_params] || {} + # HTTP header 'Accept' (if needed) + header_params['Accept'] = @api_client.select_header_accept(['application/json']) + + # form parameters + form_params = opts[:form_params] || {} + + # http body (model) + post_body = opts[:debug_body] + + # return_type + return_type = opts[:debug_return_type] || 'Object' + + # auth_names + auth_names = opts[:debug_auth_names] || ['apiKey', 'mockType', 'userId'] + + new_options = opts.merge( + :operation => :"DashboardsApi.get_va_system_pl109_reporting_summary", + :header_params => header_params, + :query_params => query_params, + :form_params => form_params, + :body => post_body, + :auth_names => auth_names, + :return_type => return_type + ) + + data, status_code, headers = @api_client.call_api(:GET, local_var_path, new_options) + if @api_client.config.debugging + @api_client.config.logger.debug "API called: DashboardsApi#get_va_system_pl109_reporting_summary\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}" + end + return data, status_code, headers + end + end +end diff --git a/src/ruby_client/lib/emass_client/api/milestones_api.rb b/src/ruby_client/lib/emass_client/api/milestones_api.rb index 3542dcef..a5d5114e 100644 --- a/src/ruby_client/lib/emass_client/api/milestones_api.rb +++ b/src/ruby_client/lib/emass_client/api/milestones_api.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/api/pac_api.rb b/src/ruby_client/lib/emass_client/api/pac_api.rb index c6ea982c..db0ed5e3 100644 --- a/src/ruby_client/lib/emass_client/api/pac_api.rb +++ b/src/ruby_client/lib/emass_client/api/pac_api.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/api/poam_api.rb b/src/ruby_client/lib/emass_client/api/poam_api.rb index 76cd944f..884ef31a 100644 --- a/src/ruby_client/lib/emass_client/api/poam_api.rb +++ b/src/ruby_client/lib/emass_client/api/poam_api.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/api/registration_api.rb b/src/ruby_client/lib/emass_client/api/registration_api.rb index f18be574..8c6e0564 100644 --- a/src/ruby_client/lib/emass_client/api/registration_api.rb +++ b/src/ruby_client/lib/emass_client/api/registration_api.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/api/static_code_scans_api.rb b/src/ruby_client/lib/emass_client/api/static_code_scans_api.rb index c8012327..272c231b 100644 --- a/src/ruby_client/lib/emass_client/api/static_code_scans_api.rb +++ b/src/ruby_client/lib/emass_client/api/static_code_scans_api.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/api/system_roles_api.rb b/src/ruby_client/lib/emass_client/api/system_roles_api.rb index 93921f51..4ab19284 100644 --- a/src/ruby_client/lib/emass_client/api/system_roles_api.rb +++ b/src/ruby_client/lib/emass_client/api/system_roles_api.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/api/systems_api.rb b/src/ruby_client/lib/emass_client/api/systems_api.rb index caeca472..4a35af31 100644 --- a/src/ruby_client/lib/emass_client/api/systems_api.rb +++ b/src/ruby_client/lib/emass_client/api/systems_api.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/api/test_api.rb b/src/ruby_client/lib/emass_client/api/test_api.rb index 8b5a1dcc..5b4a71a6 100644 --- a/src/ruby_client/lib/emass_client/api/test_api.rb +++ b/src/ruby_client/lib/emass_client/api/test_api.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/api/test_results_api.rb b/src/ruby_client/lib/emass_client/api/test_results_api.rb index e717cb68..f27bed66 100644 --- a/src/ruby_client/lib/emass_client/api/test_results_api.rb +++ b/src/ruby_client/lib/emass_client/api/test_results_api.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/api/workflow_definitions_api.rb b/src/ruby_client/lib/emass_client/api/workflow_definitions_api.rb index 7e28abac..4ae06b82 100644 --- a/src/ruby_client/lib/emass_client/api/workflow_definitions_api.rb +++ b/src/ruby_client/lib/emass_client/api/workflow_definitions_api.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/api/workflow_instances_api.rb b/src/ruby_client/lib/emass_client/api/workflow_instances_api.rb index 90d53d74..2171155d 100644 --- a/src/ruby_client/lib/emass_client/api/workflow_instances_api.rb +++ b/src/ruby_client/lib/emass_client/api/workflow_instances_api.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end @@ -23,7 +23,7 @@ def initialize(api_client = ApiClient.default) # View detailed information on all active and historical workflows filtered by provided parameters. # @param [Hash] opts the optional parameters # @option opts [Boolean] :include_comments **Include Comments**: If no value is specified, the default returns true to not include transition comments. Note: Corresponds to the Comments textbox that is required at most workflow transitions. Does not include other text input fields such as Terms / Conditions for Authorization. (default to true) - # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns true to not include transition comments. (default to 0) + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. **Note:** Pages contain 1000 workflow instances. (default to 0) # @option opts [String] :since_date **Date**: Filter on authorization/assessment date (Unix date format). Note: Filters off the lastEditedDate field. Note: The authorization/assessment decisions on completed workflows can be edited for up to 30 days after the initial decision is made. # @option opts [String] :status **Status**: Filter by status. If no value is specified, the default returns all to include both active and inactive workflows. Note: Any workflows at a current stage of Complete or Cancelled are inactive. Ongoing workflows currently at other stages are active. (default to 'all') # @return [WorkflowInstancesResponseGet] @@ -36,7 +36,7 @@ def get_system_workflow_instances(opts = {}) # View detailed information on all active and historical workflows filtered by provided parameters. # @param [Hash] opts the optional parameters # @option opts [Boolean] :include_comments **Include Comments**: If no value is specified, the default returns true to not include transition comments. Note: Corresponds to the Comments textbox that is required at most workflow transitions. Does not include other text input fields such as Terms / Conditions for Authorization. (default to true) - # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns true to not include transition comments. (default to 0) + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. **Note:** Pages contain 1000 workflow instances. (default to 0) # @option opts [String] :since_date **Date**: Filter on authorization/assessment date (Unix date format). Note: Filters off the lastEditedDate field. Note: The authorization/assessment decisions on completed workflows can be edited for up to 30 days after the initial decision is made. # @option opts [String] :status **Status**: Filter by status. If no value is specified, the default returns all to include both active and inactive workflows. Note: Any workflows at a current stage of Complete or Cancelled are inactive. Ongoing workflows currently at other stages are active. (default to 'all') # @return [Array<(WorkflowInstancesResponseGet, Integer, Hash)>] WorkflowInstancesResponseGet data, response status code and response headers diff --git a/src/ruby_client/lib/emass_client/api_client.rb b/src/ruby_client/lib/emass_client/api_client.rb index 51b53078..977087eb 100644 --- a/src/ruby_client/lib/emass_client/api_client.rb +++ b/src/ruby_client/lib/emass_client/api_client.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/api_error.rb b/src/ruby_client/lib/emass_client/api_error.rb index a3e9be00..35168e24 100644 --- a/src/ruby_client/lib/emass_client/api_error.rb +++ b/src/ruby_client/lib/emass_client/api_error.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/configuration.rb b/src/ruby_client/lib/emass_client/configuration.rb index fa1856ba..e3c6c392 100644 --- a/src/ruby_client/lib/emass_client/configuration.rb +++ b/src/ruby_client/lib/emass_client/configuration.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/artifacts_get.rb b/src/ruby_client/lib/emass_client/models/artifacts_get.rb index 12b780dc..a7f406f8 100644 --- a/src/ruby_client/lib/emass_client/models/artifacts_get.rb +++ b/src/ruby_client/lib/emass_client/models/artifacts_get.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/artifacts_request_delete_body_inner.rb b/src/ruby_client/lib/emass_client/models/artifacts_request_delete_body_inner.rb index ffd0bfde..a2e04e96 100644 --- a/src/ruby_client/lib/emass_client/models/artifacts_request_delete_body_inner.rb +++ b/src/ruby_client/lib/emass_client/models/artifacts_request_delete_body_inner.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/artifacts_response_del.rb b/src/ruby_client/lib/emass_client/models/artifacts_response_del.rb index 2e79a77d..0ee09236 100644 --- a/src/ruby_client/lib/emass_client/models/artifacts_response_del.rb +++ b/src/ruby_client/lib/emass_client/models/artifacts_response_del.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/artifacts_response_del_data_inner.rb b/src/ruby_client/lib/emass_client/models/artifacts_response_del_data_inner.rb index 47a83491..73413ea3 100644 --- a/src/ruby_client/lib/emass_client/models/artifacts_response_del_data_inner.rb +++ b/src/ruby_client/lib/emass_client/models/artifacts_response_del_data_inner.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/artifacts_response_get.rb b/src/ruby_client/lib/emass_client/models/artifacts_response_get.rb index 8fc778ff..ba604de3 100644 --- a/src/ruby_client/lib/emass_client/models/artifacts_response_get.rb +++ b/src/ruby_client/lib/emass_client/models/artifacts_response_get.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/artifacts_response_put_post.rb b/src/ruby_client/lib/emass_client/models/artifacts_response_put_post.rb index 195578b0..7da70d05 100644 --- a/src/ruby_client/lib/emass_client/models/artifacts_response_put_post.rb +++ b/src/ruby_client/lib/emass_client/models/artifacts_response_put_post.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/artifacts_response_put_post_data_inner.rb b/src/ruby_client/lib/emass_client/models/artifacts_response_put_post_data_inner.rb index 05d672ab..f5277f72 100644 --- a/src/ruby_client/lib/emass_client/models/artifacts_response_put_post_data_inner.rb +++ b/src/ruby_client/lib/emass_client/models/artifacts_response_put_post_data_inner.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/cac_get.rb b/src/ruby_client/lib/emass_client/models/cac_get.rb index c50e5106..d6bfb402 100644 --- a/src/ruby_client/lib/emass_client/models/cac_get.rb +++ b/src/ruby_client/lib/emass_client/models/cac_get.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/cac_response_get.rb b/src/ruby_client/lib/emass_client/models/cac_response_get.rb index e0b7b497..69b7d758 100644 --- a/src/ruby_client/lib/emass_client/models/cac_response_get.rb +++ b/src/ruby_client/lib/emass_client/models/cac_response_get.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/cac_response_post.rb b/src/ruby_client/lib/emass_client/models/cac_response_post.rb index f949e368..93f9556d 100644 --- a/src/ruby_client/lib/emass_client/models/cac_response_post.rb +++ b/src/ruby_client/lib/emass_client/models/cac_response_post.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/cac_response_post_data_inner.rb b/src/ruby_client/lib/emass_client/models/cac_response_post_data_inner.rb index c801ff73..40352f40 100644 --- a/src/ruby_client/lib/emass_client/models/cac_response_post_data_inner.rb +++ b/src/ruby_client/lib/emass_client/models/cac_response_post_data_inner.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/cloud_resources_post.rb b/src/ruby_client/lib/emass_client/models/cloud_resources_post.rb index ac7bf000..5909a993 100644 --- a/src/ruby_client/lib/emass_client/models/cloud_resources_post.rb +++ b/src/ruby_client/lib/emass_client/models/cloud_resources_post.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/cloud_resources_response_post.rb b/src/ruby_client/lib/emass_client/models/cloud_resources_response_post.rb index d2648ad5..e5c8c373 100644 --- a/src/ruby_client/lib/emass_client/models/cloud_resources_response_post.rb +++ b/src/ruby_client/lib/emass_client/models/cloud_resources_response_post.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/cmmc_get.rb b/src/ruby_client/lib/emass_client/models/cmmc_get.rb index 3b7be873..d74ebcc7 100644 --- a/src/ruby_client/lib/emass_client/models/cmmc_get.rb +++ b/src/ruby_client/lib/emass_client/models/cmmc_get.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/cmmc_response_get.rb b/src/ruby_client/lib/emass_client/models/cmmc_response_get.rb index 7663cbde..4c18138c 100644 --- a/src/ruby_client/lib/emass_client/models/cmmc_response_get.rb +++ b/src/ruby_client/lib/emass_client/models/cmmc_response_get.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/connectivity_ccsd.rb b/src/ruby_client/lib/emass_client/models/connectivity_ccsd.rb index fb1777c1..20b6ed60 100644 --- a/src/ruby_client/lib/emass_client/models/connectivity_ccsd.rb +++ b/src/ruby_client/lib/emass_client/models/connectivity_ccsd.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/containers_resources_post.rb b/src/ruby_client/lib/emass_client/models/containers_resources_post.rb index a9337a79..05d36785 100644 --- a/src/ruby_client/lib/emass_client/models/containers_resources_post.rb +++ b/src/ruby_client/lib/emass_client/models/containers_resources_post.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/containers_response_post.rb b/src/ruby_client/lib/emass_client/models/containers_response_post.rb index c8efeaa7..1d328db3 100644 --- a/src/ruby_client/lib/emass_client/models/containers_response_post.rb +++ b/src/ruby_client/lib/emass_client/models/containers_response_post.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/controls_get.rb b/src/ruby_client/lib/emass_client/models/controls_get.rb index a809d08e..0957a74c 100644 --- a/src/ruby_client/lib/emass_client/models/controls_get.rb +++ b/src/ruby_client/lib/emass_client/models/controls_get.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/controls_put.rb b/src/ruby_client/lib/emass_client/models/controls_put.rb index 5845b418..d50fc7a6 100644 --- a/src/ruby_client/lib/emass_client/models/controls_put.rb +++ b/src/ruby_client/lib/emass_client/models/controls_put.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/controls_response_get.rb b/src/ruby_client/lib/emass_client/models/controls_response_get.rb index 37db1201..93eef97e 100644 --- a/src/ruby_client/lib/emass_client/models/controls_response_get.rb +++ b/src/ruby_client/lib/emass_client/models/controls_response_get.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/controls_response_put.rb b/src/ruby_client/lib/emass_client/models/controls_response_put.rb index 849dd4e6..6e370325 100644 --- a/src/ruby_client/lib/emass_client/models/controls_response_put.rb +++ b/src/ruby_client/lib/emass_client/models/controls_response_put.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/definition_transitions.rb b/src/ruby_client/lib/emass_client/models/definition_transitions.rb index 227975cf..513566b5 100644 --- a/src/ruby_client/lib/emass_client/models/definition_transitions.rb +++ b/src/ruby_client/lib/emass_client/models/definition_transitions.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/instances_transitions.rb b/src/ruby_client/lib/emass_client/models/instances_transitions.rb index 50949a7f..b49053c1 100644 --- a/src/ruby_client/lib/emass_client/models/instances_transitions.rb +++ b/src/ruby_client/lib/emass_client/models/instances_transitions.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/milestone_response_get.rb b/src/ruby_client/lib/emass_client/models/milestone_response_get.rb index b37b5ebf..4d834729 100644 --- a/src/ruby_client/lib/emass_client/models/milestone_response_get.rb +++ b/src/ruby_client/lib/emass_client/models/milestone_response_get.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/milestone_response_get_milestone.rb b/src/ruby_client/lib/emass_client/models/milestone_response_get_milestone.rb index aabebdf5..29fdca74 100644 --- a/src/ruby_client/lib/emass_client/models/milestone_response_get_milestone.rb +++ b/src/ruby_client/lib/emass_client/models/milestone_response_get_milestone.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/milestone_response_post.rb b/src/ruby_client/lib/emass_client/models/milestone_response_post.rb index d79765a1..3bc42b28 100644 --- a/src/ruby_client/lib/emass_client/models/milestone_response_post.rb +++ b/src/ruby_client/lib/emass_client/models/milestone_response_post.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/milestone_response_put.rb b/src/ruby_client/lib/emass_client/models/milestone_response_put.rb index 96348e42..a4b3c746 100644 --- a/src/ruby_client/lib/emass_client/models/milestone_response_put.rb +++ b/src/ruby_client/lib/emass_client/models/milestone_response_put.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/milestones_get.rb b/src/ruby_client/lib/emass_client/models/milestones_get.rb index 63a29aef..4b5c0873 100644 --- a/src/ruby_client/lib/emass_client/models/milestones_get.rb +++ b/src/ruby_client/lib/emass_client/models/milestones_get.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/milestones_put_post_delete.rb b/src/ruby_client/lib/emass_client/models/milestones_put_post_delete.rb index 44e77a06..c9aa9cd2 100644 --- a/src/ruby_client/lib/emass_client/models/milestones_put_post_delete.rb +++ b/src/ruby_client/lib/emass_client/models/milestones_put_post_delete.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/milestones_request_delete_body_inner.rb b/src/ruby_client/lib/emass_client/models/milestones_request_delete_body_inner.rb index f003c0e0..68830360 100644 --- a/src/ruby_client/lib/emass_client/models/milestones_request_delete_body_inner.rb +++ b/src/ruby_client/lib/emass_client/models/milestones_request_delete_body_inner.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/milestones_required_post.rb b/src/ruby_client/lib/emass_client/models/milestones_required_post.rb index 48454da9..8c4bbf64 100644 --- a/src/ruby_client/lib/emass_client/models/milestones_required_post.rb +++ b/src/ruby_client/lib/emass_client/models/milestones_required_post.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/milestones_required_put.rb b/src/ruby_client/lib/emass_client/models/milestones_required_put.rb index 38224eac..b6443047 100644 --- a/src/ruby_client/lib/emass_client/models/milestones_required_put.rb +++ b/src/ruby_client/lib/emass_client/models/milestones_required_put.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/pac_get.rb b/src/ruby_client/lib/emass_client/models/pac_get.rb index 852991f6..871f2cb8 100644 --- a/src/ruby_client/lib/emass_client/models/pac_get.rb +++ b/src/ruby_client/lib/emass_client/models/pac_get.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/pac_post.rb b/src/ruby_client/lib/emass_client/models/pac_post.rb index 07b693bb..006e7531 100644 --- a/src/ruby_client/lib/emass_client/models/pac_post.rb +++ b/src/ruby_client/lib/emass_client/models/pac_post.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/pac_response_get.rb b/src/ruby_client/lib/emass_client/models/pac_response_get.rb index 4af68ce3..b82b6e59 100644 --- a/src/ruby_client/lib/emass_client/models/pac_response_get.rb +++ b/src/ruby_client/lib/emass_client/models/pac_response_get.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/pac_response_post.rb b/src/ruby_client/lib/emass_client/models/pac_response_post.rb index 9de56e53..152f58c1 100644 --- a/src/ruby_client/lib/emass_client/models/pac_response_post.rb +++ b/src/ruby_client/lib/emass_client/models/pac_response_post.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/poam_get.rb b/src/ruby_client/lib/emass_client/models/poam_get.rb index 2a216826..959c29d9 100644 --- a/src/ruby_client/lib/emass_client/models/poam_get.rb +++ b/src/ruby_client/lib/emass_client/models/poam_get.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/poam_post_put_del.rb b/src/ruby_client/lib/emass_client/models/poam_post_put_del.rb index cc180c18..8558c151 100644 --- a/src/ruby_client/lib/emass_client/models/poam_post_put_del.rb +++ b/src/ruby_client/lib/emass_client/models/poam_post_put_del.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/poam_request_delete_body_inner.rb b/src/ruby_client/lib/emass_client/models/poam_request_delete_body_inner.rb index 3f80572c..8041bac8 100644 --- a/src/ruby_client/lib/emass_client/models/poam_request_delete_body_inner.rb +++ b/src/ruby_client/lib/emass_client/models/poam_request_delete_body_inner.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/poam_response_delete.rb b/src/ruby_client/lib/emass_client/models/poam_response_delete.rb index 22b706fd..d7c75b83 100644 --- a/src/ruby_client/lib/emass_client/models/poam_response_delete.rb +++ b/src/ruby_client/lib/emass_client/models/poam_response_delete.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/poam_response_get_poams.rb b/src/ruby_client/lib/emass_client/models/poam_response_get_poams.rb index 5b055ac8..8af966d1 100644 --- a/src/ruby_client/lib/emass_client/models/poam_response_get_poams.rb +++ b/src/ruby_client/lib/emass_client/models/poam_response_get_poams.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/poam_response_get_systems.rb b/src/ruby_client/lib/emass_client/models/poam_response_get_systems.rb index d7580123..55bdb46a 100644 --- a/src/ruby_client/lib/emass_client/models/poam_response_get_systems.rb +++ b/src/ruby_client/lib/emass_client/models/poam_response_get_systems.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/poam_response_post.rb b/src/ruby_client/lib/emass_client/models/poam_response_post.rb index 3df8f6ad..701371d7 100644 --- a/src/ruby_client/lib/emass_client/models/poam_response_post.rb +++ b/src/ruby_client/lib/emass_client/models/poam_response_post.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/poam_response_put.rb b/src/ruby_client/lib/emass_client/models/poam_response_put.rb index dbddeac0..42d7fe30 100644 --- a/src/ruby_client/lib/emass_client/models/poam_response_put.rb +++ b/src/ruby_client/lib/emass_client/models/poam_response_put.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/register.rb b/src/ruby_client/lib/emass_client/models/register.rb index 3adcb485..f9a9cd3e 100644 --- a/src/ruby_client/lib/emass_client/models/register.rb +++ b/src/ruby_client/lib/emass_client/models/register.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/register_data.rb b/src/ruby_client/lib/emass_client/models/register_data.rb index 8202032a..9c9b0a2b 100644 --- a/src/ruby_client/lib/emass_client/models/register_data.rb +++ b/src/ruby_client/lib/emass_client/models/register_data.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/register_user_request_post_body.rb b/src/ruby_client/lib/emass_client/models/register_user_request_post_body.rb index af8cd5e8..7c28c657 100644 --- a/src/ruby_client/lib/emass_client/models/register_user_request_post_body.rb +++ b/src/ruby_client/lib/emass_client/models/register_user_request_post_body.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/response200.rb b/src/ruby_client/lib/emass_client/models/response200.rb index d4d98f82..5ebde967 100644 --- a/src/ruby_client/lib/emass_client/models/response200.rb +++ b/src/ruby_client/lib/emass_client/models/response200.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/response201.rb b/src/ruby_client/lib/emass_client/models/response201.rb index 8302836e..f4167b31 100644 --- a/src/ruby_client/lib/emass_client/models/response201.rb +++ b/src/ruby_client/lib/emass_client/models/response201.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/response201_meta.rb b/src/ruby_client/lib/emass_client/models/response201_meta.rb index 12e4967e..48c10527 100644 --- a/src/ruby_client/lib/emass_client/models/response201_meta.rb +++ b/src/ruby_client/lib/emass_client/models/response201_meta.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/response400.rb b/src/ruby_client/lib/emass_client/models/response400.rb index c274e4c8..2e64137a 100644 --- a/src/ruby_client/lib/emass_client/models/response400.rb +++ b/src/ruby_client/lib/emass_client/models/response400.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/response400_meta.rb b/src/ruby_client/lib/emass_client/models/response400_meta.rb index 4643f950..d48a82a3 100644 --- a/src/ruby_client/lib/emass_client/models/response400_meta.rb +++ b/src/ruby_client/lib/emass_client/models/response400_meta.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/response401.rb b/src/ruby_client/lib/emass_client/models/response401.rb index 716cd893..9c8da62f 100644 --- a/src/ruby_client/lib/emass_client/models/response401.rb +++ b/src/ruby_client/lib/emass_client/models/response401.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/response401_meta.rb b/src/ruby_client/lib/emass_client/models/response401_meta.rb index a71052bd..40a24ae1 100644 --- a/src/ruby_client/lib/emass_client/models/response401_meta.rb +++ b/src/ruby_client/lib/emass_client/models/response401_meta.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/response403.rb b/src/ruby_client/lib/emass_client/models/response403.rb index e74667cc..8881df19 100644 --- a/src/ruby_client/lib/emass_client/models/response403.rb +++ b/src/ruby_client/lib/emass_client/models/response403.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/response403_meta.rb b/src/ruby_client/lib/emass_client/models/response403_meta.rb index 29b69cf2..a9127268 100644 --- a/src/ruby_client/lib/emass_client/models/response403_meta.rb +++ b/src/ruby_client/lib/emass_client/models/response403_meta.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/response404.rb b/src/ruby_client/lib/emass_client/models/response404.rb index 77f14df9..fac3f3e6 100644 --- a/src/ruby_client/lib/emass_client/models/response404.rb +++ b/src/ruby_client/lib/emass_client/models/response404.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/response405.rb b/src/ruby_client/lib/emass_client/models/response405.rb index aed605d8..8e8271c6 100644 --- a/src/ruby_client/lib/emass_client/models/response405.rb +++ b/src/ruby_client/lib/emass_client/models/response405.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/response405_meta.rb b/src/ruby_client/lib/emass_client/models/response405_meta.rb index 04cf6076..112eaf3c 100644 --- a/src/ruby_client/lib/emass_client/models/response405_meta.rb +++ b/src/ruby_client/lib/emass_client/models/response405_meta.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/response411.rb b/src/ruby_client/lib/emass_client/models/response411.rb index 612dfc9c..07fa81ff 100644 --- a/src/ruby_client/lib/emass_client/models/response411.rb +++ b/src/ruby_client/lib/emass_client/models/response411.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/response411_meta.rb b/src/ruby_client/lib/emass_client/models/response411_meta.rb index 1314621c..72eb520d 100644 --- a/src/ruby_client/lib/emass_client/models/response411_meta.rb +++ b/src/ruby_client/lib/emass_client/models/response411_meta.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/response490.rb b/src/ruby_client/lib/emass_client/models/response490.rb index 77c91eb5..f9f11941 100644 --- a/src/ruby_client/lib/emass_client/models/response490.rb +++ b/src/ruby_client/lib/emass_client/models/response490.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/response490_meta.rb b/src/ruby_client/lib/emass_client/models/response490_meta.rb index 5475ee0b..3e5c2421 100644 --- a/src/ruby_client/lib/emass_client/models/response490_meta.rb +++ b/src/ruby_client/lib/emass_client/models/response490_meta.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/response500.rb b/src/ruby_client/lib/emass_client/models/response500.rb index 51f40c09..a10b8772 100644 --- a/src/ruby_client/lib/emass_client/models/response500.rb +++ b/src/ruby_client/lib/emass_client/models/response500.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/response500_meta.rb b/src/ruby_client/lib/emass_client/models/response500_meta.rb index 5b818aef..ece5508a 100644 --- a/src/ruby_client/lib/emass_client/models/response500_meta.rb +++ b/src/ruby_client/lib/emass_client/models/response500_meta.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/role_category.rb b/src/ruby_client/lib/emass_client/models/role_category.rb index 406d59a1..3172c72f 100644 --- a/src/ruby_client/lib/emass_client/models/role_category.rb +++ b/src/ruby_client/lib/emass_client/models/role_category.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/roles.rb b/src/ruby_client/lib/emass_client/models/roles.rb index 38895768..3694ce92 100644 --- a/src/ruby_client/lib/emass_client/models/roles.rb +++ b/src/ruby_client/lib/emass_client/models/roles.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/ssps.rb b/src/ruby_client/lib/emass_client/models/ssps.rb index daca232b..05f2ce72 100644 --- a/src/ruby_client/lib/emass_client/models/ssps.rb +++ b/src/ruby_client/lib/emass_client/models/ssps.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/stage.rb b/src/ruby_client/lib/emass_client/models/stage.rb index 0a590e5d..89e3ce92 100644 --- a/src/ruby_client/lib/emass_client/models/stage.rb +++ b/src/ruby_client/lib/emass_client/models/stage.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/static_code_application.rb b/src/ruby_client/lib/emass_client/models/static_code_application.rb index c0ab3c91..0d4ea0dc 100644 --- a/src/ruby_client/lib/emass_client/models/static_code_application.rb +++ b/src/ruby_client/lib/emass_client/models/static_code_application.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/static_code_post.rb b/src/ruby_client/lib/emass_client/models/static_code_post.rb index e28b8746..f93f8288 100644 --- a/src/ruby_client/lib/emass_client/models/static_code_post.rb +++ b/src/ruby_client/lib/emass_client/models/static_code_post.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/static_code_request_post_body.rb b/src/ruby_client/lib/emass_client/models/static_code_request_post_body.rb index 45e333b7..90b0d88d 100644 --- a/src/ruby_client/lib/emass_client/models/static_code_request_post_body.rb +++ b/src/ruby_client/lib/emass_client/models/static_code_request_post_body.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/static_code_request_post_body_application.rb b/src/ruby_client/lib/emass_client/models/static_code_request_post_body_application.rb index 6d8499d6..6d884a2a 100644 --- a/src/ruby_client/lib/emass_client/models/static_code_request_post_body_application.rb +++ b/src/ruby_client/lib/emass_client/models/static_code_request_post_body_application.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/static_code_response_post.rb b/src/ruby_client/lib/emass_client/models/static_code_response_post.rb index 3b692948..a25b8327 100644 --- a/src/ruby_client/lib/emass_client/models/static_code_response_post.rb +++ b/src/ruby_client/lib/emass_client/models/static_code_response_post.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/success200_response.rb b/src/ruby_client/lib/emass_client/models/success200_response.rb index 5914ea25..d2782992 100644 --- a/src/ruby_client/lib/emass_client/models/success200_response.rb +++ b/src/ruby_client/lib/emass_client/models/success200_response.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/success200_response_data_inner.rb b/src/ruby_client/lib/emass_client/models/success200_response_data_inner.rb index 215b24ac..937a0fa4 100644 --- a/src/ruby_client/lib/emass_client/models/success200_response_data_inner.rb +++ b/src/ruby_client/lib/emass_client/models/success200_response_data_inner.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/system_response.rb b/src/ruby_client/lib/emass_client/models/system_response.rb index 7df87dee..b0216780 100644 --- a/src/ruby_client/lib/emass_client/models/system_response.rb +++ b/src/ruby_client/lib/emass_client/models/system_response.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/system_roles_category_response.rb b/src/ruby_client/lib/emass_client/models/system_roles_category_response.rb index 193a24d8..335dc762 100644 --- a/src/ruby_client/lib/emass_client/models/system_roles_category_response.rb +++ b/src/ruby_client/lib/emass_client/models/system_roles_category_response.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/system_roles_response.rb b/src/ruby_client/lib/emass_client/models/system_roles_response.rb index 23475d51..caf45b4c 100644 --- a/src/ruby_client/lib/emass_client/models/system_roles_response.rb +++ b/src/ruby_client/lib/emass_client/models/system_roles_response.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/system_roles_response_data_inner.rb b/src/ruby_client/lib/emass_client/models/system_roles_response_data_inner.rb index 18f185e1..d4bee0eb 100644 --- a/src/ruby_client/lib/emass_client/models/system_roles_response_data_inner.rb +++ b/src/ruby_client/lib/emass_client/models/system_roles_response_data_inner.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/systems.rb b/src/ruby_client/lib/emass_client/models/systems.rb index 645efcc5..0d292ede 100644 --- a/src/ruby_client/lib/emass_client/models/systems.rb +++ b/src/ruby_client/lib/emass_client/models/systems.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/systems_response.rb b/src/ruby_client/lib/emass_client/models/systems_response.rb index c9990d3d..7c59218f 100644 --- a/src/ruby_client/lib/emass_client/models/systems_response.rb +++ b/src/ruby_client/lib/emass_client/models/systems_response.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/test.rb b/src/ruby_client/lib/emass_client/models/test.rb index 5091d442..c2495df5 100644 --- a/src/ruby_client/lib/emass_client/models/test.rb +++ b/src/ruby_client/lib/emass_client/models/test.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/test_data.rb b/src/ruby_client/lib/emass_client/models/test_data.rb index 1c4a45c9..ca50e7f0 100644 --- a/src/ruby_client/lib/emass_client/models/test_data.rb +++ b/src/ruby_client/lib/emass_client/models/test_data.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/test_results_get.rb b/src/ruby_client/lib/emass_client/models/test_results_get.rb index 22fd2eb4..3cad2f20 100644 --- a/src/ruby_client/lib/emass_client/models/test_results_get.rb +++ b/src/ruby_client/lib/emass_client/models/test_results_get.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/test_results_post.rb b/src/ruby_client/lib/emass_client/models/test_results_post.rb index bf565890..8008ef95 100644 --- a/src/ruby_client/lib/emass_client/models/test_results_post.rb +++ b/src/ruby_client/lib/emass_client/models/test_results_post.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/test_results_response_get.rb b/src/ruby_client/lib/emass_client/models/test_results_response_get.rb index 7d241251..f5e1c90d 100644 --- a/src/ruby_client/lib/emass_client/models/test_results_response_get.rb +++ b/src/ruby_client/lib/emass_client/models/test_results_response_get.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/test_results_response_post.rb b/src/ruby_client/lib/emass_client/models/test_results_response_post.rb index 07a896c4..155880be 100644 --- a/src/ruby_client/lib/emass_client/models/test_results_response_post.rb +++ b/src/ruby_client/lib/emass_client/models/test_results_response_post.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/users.rb b/src/ruby_client/lib/emass_client/models/users.rb index 9d590b83..ee8a0103 100644 --- a/src/ruby_client/lib/emass_client/models/users.rb +++ b/src/ruby_client/lib/emass_client/models/users.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/workflow_definition_get.rb b/src/ruby_client/lib/emass_client/models/workflow_definition_get.rb index b15a3b3b..b696cb42 100644 --- a/src/ruby_client/lib/emass_client/models/workflow_definition_get.rb +++ b/src/ruby_client/lib/emass_client/models/workflow_definition_get.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/workflow_definition_response_get.rb b/src/ruby_client/lib/emass_client/models/workflow_definition_response_get.rb index 53021c5c..31726257 100644 --- a/src/ruby_client/lib/emass_client/models/workflow_definition_response_get.rb +++ b/src/ruby_client/lib/emass_client/models/workflow_definition_response_get.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/workflow_instance_get.rb b/src/ruby_client/lib/emass_client/models/workflow_instance_get.rb index 9d880541..40fe9e9f 100644 --- a/src/ruby_client/lib/emass_client/models/workflow_instance_get.rb +++ b/src/ruby_client/lib/emass_client/models/workflow_instance_get.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/workflow_instance_response_get.rb b/src/ruby_client/lib/emass_client/models/workflow_instance_response_get.rb index d79a70dd..4bf3a64b 100644 --- a/src/ruby_client/lib/emass_client/models/workflow_instance_response_get.rb +++ b/src/ruby_client/lib/emass_client/models/workflow_instance_response_get.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/workflow_instances_get.rb b/src/ruby_client/lib/emass_client/models/workflow_instances_get.rb index 33e8c7b6..7ff150ce 100644 --- a/src/ruby_client/lib/emass_client/models/workflow_instances_get.rb +++ b/src/ruby_client/lib/emass_client/models/workflow_instances_get.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/workflow_instances_response_get.rb b/src/ruby_client/lib/emass_client/models/workflow_instances_response_get.rb index 913007fe..5411f03b 100644 --- a/src/ruby_client/lib/emass_client/models/workflow_instances_response_get.rb +++ b/src/ruby_client/lib/emass_client/models/workflow_instances_response_get.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/models/workflow_instances_response_get_pagination.rb b/src/ruby_client/lib/emass_client/models/workflow_instances_response_get_pagination.rb index 1ebb7cb8..5306e0eb 100644 --- a/src/ruby_client/lib/emass_client/models/workflow_instances_response_get_pagination.rb +++ b/src/ruby_client/lib/emass_client/models/workflow_instances_response_get_pagination.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/lib/emass_client/version.rb b/src/ruby_client/lib/emass_client/version.rb index cb04bc59..8d10faac 100644 --- a/src/ruby_client/lib/emass_client/version.rb +++ b/src/ruby_client/lib/emass_client/version.rb @@ -3,13 +3,13 @@ #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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end module EmassClient - VERSION = '1.0.6' + VERSION = '3.4.0' end diff --git a/src/ruby_client/spec/api/artifacts_api_spec.rb b/src/ruby_client/spec/api/artifacts_api_spec.rb index 3096af24..f8f49c5c 100644 --- a/src/ruby_client/spec/api/artifacts_api_spec.rb +++ b/src/ruby_client/spec/api/artifacts_api_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/api/artifacts_export_api_spec.rb b/src/ruby_client/spec/api/artifacts_export_api_spec.rb index da6a1f9b..6156b570 100644 --- a/src/ruby_client/spec/api/artifacts_export_api_spec.rb +++ b/src/ruby_client/spec/api/artifacts_export_api_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/api/cac_api_spec.rb b/src/ruby_client/spec/api/cac_api_spec.rb index 0160d82f..9fe16392 100644 --- a/src/ruby_client/spec/api/cac_api_spec.rb +++ b/src/ruby_client/spec/api/cac_api_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/api/cloud_resources_api_spec.rb b/src/ruby_client/spec/api/cloud_resources_api_spec.rb index 6d9d2d35..2fdc5953 100644 --- a/src/ruby_client/spec/api/cloud_resources_api_spec.rb +++ b/src/ruby_client/spec/api/cloud_resources_api_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/api/cmmc_assessments_api_spec.rb b/src/ruby_client/spec/api/cmmc_assessments_api_spec.rb index 66645b79..277b2c7a 100644 --- a/src/ruby_client/spec/api/cmmc_assessments_api_spec.rb +++ b/src/ruby_client/spec/api/cmmc_assessments_api_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/api/containers_api_spec.rb b/src/ruby_client/spec/api/containers_api_spec.rb index 93cbbfb9..1e1d11ea 100644 --- a/src/ruby_client/spec/api/containers_api_spec.rb +++ b/src/ruby_client/spec/api/containers_api_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/api/controls_api_spec.rb b/src/ruby_client/spec/api/controls_api_spec.rb index d0b2a1ac..2bacf1b9 100644 --- a/src/ruby_client/spec/api/controls_api_spec.rb +++ b/src/ruby_client/spec/api/controls_api_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/api/dashboards_api_spec.rb b/src/ruby_client/spec/api/dashboards_api_spec.rb new file mode 100644 index 00000000..ca3e21af --- /dev/null +++ b/src/ruby_client/spec/api/dashboards_api_spec.rb @@ -0,0 +1,259 @@ +=begin +#Enterprise Mission Assurance Support Service (eMASS) + +#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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: + +The version of the OpenAPI document: v3.4 +Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil +Generated by: https://openapi-generator.tech +OpenAPI Generator version: 6.1.1-SNAPSHOT + +=end + +require 'spec_helper' +require 'json' + +# Unit tests for EmassClient::DashboardsApi +# Automatically generated by openapi-generator (https://openapi-generator.tech) +# Please update as you see appropriate +describe 'DashboardsApi' do + before do + # run before each test + @api_instance = EmassClient::DashboardsApi.new + end + + after do + # run after each test + end + + describe 'test an instance of DashboardsApi' do + it 'should create an instance of DashboardsApi' do + expect(@api_instance).to be_instance_of(EmassClient::DashboardsApi) + end + end + + # unit tests for get_system_assessment_procedures_details + # Get dashboard information + # Get systems assessement procdures details dashboard information. + # @param org_id **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. + # @return [Object] + describe 'get_system_assessment_procedures_details test' do + it 'should work' do + # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers + end + end + + # unit tests for get_system_associations_details + # Get dashboard information + # Get system associations details dashboard information. + # @param org_id **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. + # @return [Object] + describe 'get_system_associations_details test' do + it 'should work' do + # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers + end + end + + # unit tests for get_system_control_compliance_summary + # Get dashboard information + # Get systems control compliance summary dashboard information. + # @param org_id **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. + # @return [Object] + describe 'get_system_control_compliance_summary test' do + it 'should work' do + # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers + end + end + + # unit tests for get_system_hardware_details + # Get dashboard information + # Get system hardware details dashboard information. + # @param org_id **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. + # @return [Object] + describe 'get_system_hardware_details test' do + it 'should work' do + # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers + end + end + + # unit tests for get_system_hardware_summary + # Get dashboard information + # Get system hardware summary dashboard information. + # @param org_id **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. + # @return [Object] + describe 'get_system_hardware_summary test' do + it 'should work' do + # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers + end + end + + # unit tests for get_system_poam_details + # Get dashboard information + # Get system POA&Ms details dashboard information. + # @param org_id **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. + # @return [Object] + describe 'get_system_poam_details test' do + it 'should work' do + # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers + end + end + + # unit tests for get_system_poam_summary + # Get dashboard information + # Get systems POA&Ms summary dashboard information. + # @param org_id **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. + # @return [Object] + describe 'get_system_poam_summary test' do + it 'should work' do + # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers + end + end + + # unit tests for get_system_privacy_summary + # Get dashboard information + # Get user system privacy summary dashboard information. + # @param org_id **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. + # @return [Object] + describe 'get_system_privacy_summary test' do + it 'should work' do + # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers + end + end + + # unit tests for get_system_security_control_details + # Get dashboard information + # Get systems security control details dashboard information. + # @param org_id **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. + # @return [Object] + describe 'get_system_security_control_details test' do + it 'should work' do + # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers + end + end + + # unit tests for get_system_status_details + # Get dashboard information + # Get systems status detail dashboard information. + # @param org_id **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. + # @return [Object] + describe 'get_system_status_details test' do + it 'should work' do + # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers + end + end + + # unit tests for get_user_system_assignments_details + # Get dashboard information + # Get user system assignments details dashboard information. + # @param org_id **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. + # @return [Object] + describe 'get_user_system_assignments_details test' do + it 'should work' do + # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers + end + end + + # unit tests for get_va_omb_fsma_saop_summary + # Get dashboard information + # Get VA OMB-FISMA SAOP summary dashboard information. + # @param org_id **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. + # @return [Object] + describe 'get_va_omb_fsma_saop_summary test' do + it 'should work' do + # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers + end + end + + # unit tests for get_va_system_a2_summary + # Get dashboard information + # Get VA system A2.0 summary dashboard information. + # @param org_id **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. + # @return [Object] + describe 'get_va_system_a2_summary test' do + it 'should work' do + # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers + end + end + + # unit tests for get_va_system_aa_summary + # Get dashboard information + # Get VA system A&A summary dashboard information. + # @param org_id **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. + # @return [Object] + describe 'get_va_system_aa_summary test' do + it 'should work' do + # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers + end + end + + # unit tests for get_va_system_fisma_invetory_summary + # Get dashboard information + # Get VA system FISMA inventory summary dashboard information. + # @param org_id **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. + # @return [Object] + describe 'get_va_system_fisma_invetory_summary test' do + it 'should work' do + # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers + end + end + + # unit tests for get_va_system_pl109_reporting_summary + # Get dashboard information + # Get VA system P.L. 109 reporting summary dashboard information. + # @param org_id **Organization Id**: The unique organization identifier. + # @param [Hash] opts the optional parameters + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + # @option opts [Integer] :page_size **Page Size**: If no value is specified, the default returns 20000 per page. + # @return [Object] + describe 'get_va_system_pl109_reporting_summary test' do + it 'should work' do + # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers + end + end + +end diff --git a/src/ruby_client/spec/api/milestones_api_spec.rb b/src/ruby_client/spec/api/milestones_api_spec.rb index 53d2c2b4..109e1710 100644 --- a/src/ruby_client/spec/api/milestones_api_spec.rb +++ b/src/ruby_client/spec/api/milestones_api_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/api/pac_api_spec.rb b/src/ruby_client/spec/api/pac_api_spec.rb index 0f8aee9f..b2104b9f 100644 --- a/src/ruby_client/spec/api/pac_api_spec.rb +++ b/src/ruby_client/spec/api/pac_api_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/api/poam_api_spec.rb b/src/ruby_client/spec/api/poam_api_spec.rb index 1e493050..b94a99b2 100644 --- a/src/ruby_client/spec/api/poam_api_spec.rb +++ b/src/ruby_client/spec/api/poam_api_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/api/registration_api_spec.rb b/src/ruby_client/spec/api/registration_api_spec.rb index 0c7efb30..e41766c5 100644 --- a/src/ruby_client/spec/api/registration_api_spec.rb +++ b/src/ruby_client/spec/api/registration_api_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/api/static_code_scans_api_spec.rb b/src/ruby_client/spec/api/static_code_scans_api_spec.rb index 2ecca5ee..2330a3d8 100644 --- a/src/ruby_client/spec/api/static_code_scans_api_spec.rb +++ b/src/ruby_client/spec/api/static_code_scans_api_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/api/system_roles_api_spec.rb b/src/ruby_client/spec/api/system_roles_api_spec.rb index 5b37db64..591b7eb8 100644 --- a/src/ruby_client/spec/api/system_roles_api_spec.rb +++ b/src/ruby_client/spec/api/system_roles_api_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/api/systems_api_spec.rb b/src/ruby_client/spec/api/systems_api_spec.rb index 6ae537b8..e32f03bf 100644 --- a/src/ruby_client/spec/api/systems_api_spec.rb +++ b/src/ruby_client/spec/api/systems_api_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/api/test_api_spec.rb b/src/ruby_client/spec/api/test_api_spec.rb index 311f887b..74dc87de 100644 --- a/src/ruby_client/spec/api/test_api_spec.rb +++ b/src/ruby_client/spec/api/test_api_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/api/test_results_api_spec.rb b/src/ruby_client/spec/api/test_results_api_spec.rb index 034f118a..000de81a 100644 --- a/src/ruby_client/spec/api/test_results_api_spec.rb +++ b/src/ruby_client/spec/api/test_results_api_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/api/workflow_definitions_api_spec.rb b/src/ruby_client/spec/api/workflow_definitions_api_spec.rb index 73b6fb32..7c6a5e90 100644 --- a/src/ruby_client/spec/api/workflow_definitions_api_spec.rb +++ b/src/ruby_client/spec/api/workflow_definitions_api_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/api/workflow_instances_api_spec.rb b/src/ruby_client/spec/api/workflow_instances_api_spec.rb index c8d932c1..9308a4e0 100644 --- a/src/ruby_client/spec/api/workflow_instances_api_spec.rb +++ b/src/ruby_client/spec/api/workflow_instances_api_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end @@ -37,7 +37,7 @@ # View detailed information on all active and historical workflows filtered by provided parameters. # @param [Hash] opts the optional parameters # @option opts [Boolean] :include_comments **Include Comments**: If no value is specified, the default returns true to not include transition comments. Note: Corresponds to the Comments textbox that is required at most workflow transitions. Does not include other text input fields such as Terms / Conditions for Authorization. - # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns true to not include transition comments. + # @option opts [Integer] :page_index **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. **Note:** Pages contain 1000 workflow instances. # @option opts [String] :since_date **Date**: Filter on authorization/assessment date (Unix date format). Note: Filters off the lastEditedDate field. Note: The authorization/assessment decisions on completed workflows can be edited for up to 30 days after the initial decision is made. # @option opts [String] :status **Status**: Filter by status. If no value is specified, the default returns all to include both active and inactive workflows. Note: Any workflows at a current stage of Complete or Cancelled are inactive. Ongoing workflows currently at other stages are active. # @return [WorkflowInstancesResponseGet] diff --git a/src/ruby_client/spec/api_client_spec.rb b/src/ruby_client/spec/api_client_spec.rb index 90d0e019..d47a39c3 100644 --- a/src/ruby_client/spec/api_client_spec.rb +++ b/src/ruby_client/spec/api_client_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/configuration_spec.rb b/src/ruby_client/spec/configuration_spec.rb index 4a0e4860..1ee2eb83 100644 --- a/src/ruby_client/spec/configuration_spec.rb +++ b/src/ruby_client/spec/configuration_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/artifacts_get_spec.rb b/src/ruby_client/spec/models/artifacts_get_spec.rb index 4ce3394d..2c93a34f 100644 --- a/src/ruby_client/spec/models/artifacts_get_spec.rb +++ b/src/ruby_client/spec/models/artifacts_get_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/artifacts_request_delete_body_inner_spec.rb b/src/ruby_client/spec/models/artifacts_request_delete_body_inner_spec.rb index 8075cde0..de093796 100644 --- a/src/ruby_client/spec/models/artifacts_request_delete_body_inner_spec.rb +++ b/src/ruby_client/spec/models/artifacts_request_delete_body_inner_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/artifacts_response_del_data_inner_spec.rb b/src/ruby_client/spec/models/artifacts_response_del_data_inner_spec.rb index e12a4136..94841d76 100644 --- a/src/ruby_client/spec/models/artifacts_response_del_data_inner_spec.rb +++ b/src/ruby_client/spec/models/artifacts_response_del_data_inner_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/artifacts_response_del_spec.rb b/src/ruby_client/spec/models/artifacts_response_del_spec.rb index bfcfac33..f543b2bf 100644 --- a/src/ruby_client/spec/models/artifacts_response_del_spec.rb +++ b/src/ruby_client/spec/models/artifacts_response_del_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/artifacts_response_get_spec.rb b/src/ruby_client/spec/models/artifacts_response_get_spec.rb index 8b8a79b2..953fc6c4 100644 --- a/src/ruby_client/spec/models/artifacts_response_get_spec.rb +++ b/src/ruby_client/spec/models/artifacts_response_get_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/artifacts_response_put_post_data_inner_spec.rb b/src/ruby_client/spec/models/artifacts_response_put_post_data_inner_spec.rb index 32ce0732..45f1eac0 100644 --- a/src/ruby_client/spec/models/artifacts_response_put_post_data_inner_spec.rb +++ b/src/ruby_client/spec/models/artifacts_response_put_post_data_inner_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/artifacts_response_put_post_spec.rb b/src/ruby_client/spec/models/artifacts_response_put_post_spec.rb index d788a182..5f1550f7 100644 --- a/src/ruby_client/spec/models/artifacts_response_put_post_spec.rb +++ b/src/ruby_client/spec/models/artifacts_response_put_post_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/cac_get_spec.rb b/src/ruby_client/spec/models/cac_get_spec.rb index 0feb136d..8080e71c 100644 --- a/src/ruby_client/spec/models/cac_get_spec.rb +++ b/src/ruby_client/spec/models/cac_get_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/cac_response_get_spec.rb b/src/ruby_client/spec/models/cac_response_get_spec.rb index 7fbf8f7e..7748de71 100644 --- a/src/ruby_client/spec/models/cac_response_get_spec.rb +++ b/src/ruby_client/spec/models/cac_response_get_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/cac_response_post_data_inner_spec.rb b/src/ruby_client/spec/models/cac_response_post_data_inner_spec.rb index 4ef794f9..47d7f700 100644 --- a/src/ruby_client/spec/models/cac_response_post_data_inner_spec.rb +++ b/src/ruby_client/spec/models/cac_response_post_data_inner_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/cac_response_post_spec.rb b/src/ruby_client/spec/models/cac_response_post_spec.rb index b68ef6f8..9e324373 100644 --- a/src/ruby_client/spec/models/cac_response_post_spec.rb +++ b/src/ruby_client/spec/models/cac_response_post_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/cloud_resources_post_spec.rb b/src/ruby_client/spec/models/cloud_resources_post_spec.rb index 552b088e..a0896f91 100644 --- a/src/ruby_client/spec/models/cloud_resources_post_spec.rb +++ b/src/ruby_client/spec/models/cloud_resources_post_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/cloud_resources_response_post_spec.rb b/src/ruby_client/spec/models/cloud_resources_response_post_spec.rb index b5cb8ad0..a8b77147 100644 --- a/src/ruby_client/spec/models/cloud_resources_response_post_spec.rb +++ b/src/ruby_client/spec/models/cloud_resources_response_post_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/cmmc_get_spec.rb b/src/ruby_client/spec/models/cmmc_get_spec.rb index 310671ca..e2ba2a19 100644 --- a/src/ruby_client/spec/models/cmmc_get_spec.rb +++ b/src/ruby_client/spec/models/cmmc_get_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/cmmc_response_get_spec.rb b/src/ruby_client/spec/models/cmmc_response_get_spec.rb index 903972a5..9dd71568 100644 --- a/src/ruby_client/spec/models/cmmc_response_get_spec.rb +++ b/src/ruby_client/spec/models/cmmc_response_get_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/connectivity_ccsd_spec.rb b/src/ruby_client/spec/models/connectivity_ccsd_spec.rb index 1676c83c..e0ade687 100644 --- a/src/ruby_client/spec/models/connectivity_ccsd_spec.rb +++ b/src/ruby_client/spec/models/connectivity_ccsd_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/containers_resources_post_spec.rb b/src/ruby_client/spec/models/containers_resources_post_spec.rb index fdeecfba..fe7bab69 100644 --- a/src/ruby_client/spec/models/containers_resources_post_spec.rb +++ b/src/ruby_client/spec/models/containers_resources_post_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/containers_response_post_spec.rb b/src/ruby_client/spec/models/containers_response_post_spec.rb index 8e061947..9ab5893b 100644 --- a/src/ruby_client/spec/models/containers_response_post_spec.rb +++ b/src/ruby_client/spec/models/containers_response_post_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/controls_get_spec.rb b/src/ruby_client/spec/models/controls_get_spec.rb index b497e612..670a7e90 100644 --- a/src/ruby_client/spec/models/controls_get_spec.rb +++ b/src/ruby_client/spec/models/controls_get_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/controls_put_spec.rb b/src/ruby_client/spec/models/controls_put_spec.rb index 8c3c7365..6873195a 100644 --- a/src/ruby_client/spec/models/controls_put_spec.rb +++ b/src/ruby_client/spec/models/controls_put_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/controls_response_get_spec.rb b/src/ruby_client/spec/models/controls_response_get_spec.rb index ca9ffac5..74b9e8e5 100644 --- a/src/ruby_client/spec/models/controls_response_get_spec.rb +++ b/src/ruby_client/spec/models/controls_response_get_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/controls_response_put_spec.rb b/src/ruby_client/spec/models/controls_response_put_spec.rb index 0fa3b299..6b5c0880 100644 --- a/src/ruby_client/spec/models/controls_response_put_spec.rb +++ b/src/ruby_client/spec/models/controls_response_put_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/definition_transitions_spec.rb b/src/ruby_client/spec/models/definition_transitions_spec.rb index 31fa9e94..b5ddc1b3 100644 --- a/src/ruby_client/spec/models/definition_transitions_spec.rb +++ b/src/ruby_client/spec/models/definition_transitions_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/instances_transitions_spec.rb b/src/ruby_client/spec/models/instances_transitions_spec.rb index 40e76fcc..3570defd 100644 --- a/src/ruby_client/spec/models/instances_transitions_spec.rb +++ b/src/ruby_client/spec/models/instances_transitions_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/milestone_response_get_milestone_spec.rb b/src/ruby_client/spec/models/milestone_response_get_milestone_spec.rb index 4296c355..1b81e467 100644 --- a/src/ruby_client/spec/models/milestone_response_get_milestone_spec.rb +++ b/src/ruby_client/spec/models/milestone_response_get_milestone_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/milestone_response_get_spec.rb b/src/ruby_client/spec/models/milestone_response_get_spec.rb index fc37306b..e51a8387 100644 --- a/src/ruby_client/spec/models/milestone_response_get_spec.rb +++ b/src/ruby_client/spec/models/milestone_response_get_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/milestone_response_post_spec.rb b/src/ruby_client/spec/models/milestone_response_post_spec.rb index 597d6d03..5607cc64 100644 --- a/src/ruby_client/spec/models/milestone_response_post_spec.rb +++ b/src/ruby_client/spec/models/milestone_response_post_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/milestone_response_put_spec.rb b/src/ruby_client/spec/models/milestone_response_put_spec.rb index b2c0c1e5..d20ba871 100644 --- a/src/ruby_client/spec/models/milestone_response_put_spec.rb +++ b/src/ruby_client/spec/models/milestone_response_put_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/milestones_get_spec.rb b/src/ruby_client/spec/models/milestones_get_spec.rb index 6b59c60d..a6b685c0 100644 --- a/src/ruby_client/spec/models/milestones_get_spec.rb +++ b/src/ruby_client/spec/models/milestones_get_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/milestones_put_post_delete_spec.rb b/src/ruby_client/spec/models/milestones_put_post_delete_spec.rb index 2af9e3e8..0e90e9f8 100644 --- a/src/ruby_client/spec/models/milestones_put_post_delete_spec.rb +++ b/src/ruby_client/spec/models/milestones_put_post_delete_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/milestones_request_delete_body_inner_spec.rb b/src/ruby_client/spec/models/milestones_request_delete_body_inner_spec.rb index d7ed69a8..6a96fb06 100644 --- a/src/ruby_client/spec/models/milestones_request_delete_body_inner_spec.rb +++ b/src/ruby_client/spec/models/milestones_request_delete_body_inner_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/milestones_required_post_spec.rb b/src/ruby_client/spec/models/milestones_required_post_spec.rb index 2e379d04..c5ebeb4d 100644 --- a/src/ruby_client/spec/models/milestones_required_post_spec.rb +++ b/src/ruby_client/spec/models/milestones_required_post_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/milestones_required_put_spec.rb b/src/ruby_client/spec/models/milestones_required_put_spec.rb index 678ae225..17407bf3 100644 --- a/src/ruby_client/spec/models/milestones_required_put_spec.rb +++ b/src/ruby_client/spec/models/milestones_required_put_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/pac_get_spec.rb b/src/ruby_client/spec/models/pac_get_spec.rb index 9117965b..e644a43c 100644 --- a/src/ruby_client/spec/models/pac_get_spec.rb +++ b/src/ruby_client/spec/models/pac_get_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/pac_post_spec.rb b/src/ruby_client/spec/models/pac_post_spec.rb index 0bd7782d..05547614 100644 --- a/src/ruby_client/spec/models/pac_post_spec.rb +++ b/src/ruby_client/spec/models/pac_post_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/pac_response_get_spec.rb b/src/ruby_client/spec/models/pac_response_get_spec.rb index 861bd474..11d7b310 100644 --- a/src/ruby_client/spec/models/pac_response_get_spec.rb +++ b/src/ruby_client/spec/models/pac_response_get_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/pac_response_post_spec.rb b/src/ruby_client/spec/models/pac_response_post_spec.rb index 3aecaad9..2e975097 100644 --- a/src/ruby_client/spec/models/pac_response_post_spec.rb +++ b/src/ruby_client/spec/models/pac_response_post_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/poam_get_spec.rb b/src/ruby_client/spec/models/poam_get_spec.rb index 7e9afbd9..b0615e42 100644 --- a/src/ruby_client/spec/models/poam_get_spec.rb +++ b/src/ruby_client/spec/models/poam_get_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/poam_post_put_del_spec.rb b/src/ruby_client/spec/models/poam_post_put_del_spec.rb index 778da1bd..63e60cde 100644 --- a/src/ruby_client/spec/models/poam_post_put_del_spec.rb +++ b/src/ruby_client/spec/models/poam_post_put_del_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/poam_request_delete_body_inner_spec.rb b/src/ruby_client/spec/models/poam_request_delete_body_inner_spec.rb index b296cd77..698ae843 100644 --- a/src/ruby_client/spec/models/poam_request_delete_body_inner_spec.rb +++ b/src/ruby_client/spec/models/poam_request_delete_body_inner_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/poam_response_delete_spec.rb b/src/ruby_client/spec/models/poam_response_delete_spec.rb index 857a5aa6..7fc6d213 100644 --- a/src/ruby_client/spec/models/poam_response_delete_spec.rb +++ b/src/ruby_client/spec/models/poam_response_delete_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/poam_response_get_poams_spec.rb b/src/ruby_client/spec/models/poam_response_get_poams_spec.rb index cbb53913..dc1a38eb 100644 --- a/src/ruby_client/spec/models/poam_response_get_poams_spec.rb +++ b/src/ruby_client/spec/models/poam_response_get_poams_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/poam_response_get_systems_spec.rb b/src/ruby_client/spec/models/poam_response_get_systems_spec.rb index 3f6d66ef..009d0bbb 100644 --- a/src/ruby_client/spec/models/poam_response_get_systems_spec.rb +++ b/src/ruby_client/spec/models/poam_response_get_systems_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/poam_response_post_spec.rb b/src/ruby_client/spec/models/poam_response_post_spec.rb index eefe26ba..12a8e705 100644 --- a/src/ruby_client/spec/models/poam_response_post_spec.rb +++ b/src/ruby_client/spec/models/poam_response_post_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/poam_response_put_spec.rb b/src/ruby_client/spec/models/poam_response_put_spec.rb index 544e6e7b..fcdb5188 100644 --- a/src/ruby_client/spec/models/poam_response_put_spec.rb +++ b/src/ruby_client/spec/models/poam_response_put_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/register_data_spec.rb b/src/ruby_client/spec/models/register_data_spec.rb index 315d1fb9..4d97ac61 100644 --- a/src/ruby_client/spec/models/register_data_spec.rb +++ b/src/ruby_client/spec/models/register_data_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/register_spec.rb b/src/ruby_client/spec/models/register_spec.rb index 5e462594..23c88d36 100644 --- a/src/ruby_client/spec/models/register_spec.rb +++ b/src/ruby_client/spec/models/register_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/register_user_request_post_body_spec.rb b/src/ruby_client/spec/models/register_user_request_post_body_spec.rb index 1b88ffff..89093fc5 100644 --- a/src/ruby_client/spec/models/register_user_request_post_body_spec.rb +++ b/src/ruby_client/spec/models/register_user_request_post_body_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/response200_spec.rb b/src/ruby_client/spec/models/response200_spec.rb index 534c4dc8..57ed74b2 100644 --- a/src/ruby_client/spec/models/response200_spec.rb +++ b/src/ruby_client/spec/models/response200_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/response201_meta_spec.rb b/src/ruby_client/spec/models/response201_meta_spec.rb index 4beffc86..1ef90eca 100644 --- a/src/ruby_client/spec/models/response201_meta_spec.rb +++ b/src/ruby_client/spec/models/response201_meta_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/response201_spec.rb b/src/ruby_client/spec/models/response201_spec.rb index be455973..9fa26503 100644 --- a/src/ruby_client/spec/models/response201_spec.rb +++ b/src/ruby_client/spec/models/response201_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/response400_meta_spec.rb b/src/ruby_client/spec/models/response400_meta_spec.rb index decac6ba..37fef7b2 100644 --- a/src/ruby_client/spec/models/response400_meta_spec.rb +++ b/src/ruby_client/spec/models/response400_meta_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/response400_spec.rb b/src/ruby_client/spec/models/response400_spec.rb index c8f5f74b..120496b1 100644 --- a/src/ruby_client/spec/models/response400_spec.rb +++ b/src/ruby_client/spec/models/response400_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/response401_meta_spec.rb b/src/ruby_client/spec/models/response401_meta_spec.rb index 3d265f3c..af36da78 100644 --- a/src/ruby_client/spec/models/response401_meta_spec.rb +++ b/src/ruby_client/spec/models/response401_meta_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/response401_spec.rb b/src/ruby_client/spec/models/response401_spec.rb index 9a743ab9..bfc4c4a3 100644 --- a/src/ruby_client/spec/models/response401_spec.rb +++ b/src/ruby_client/spec/models/response401_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/response403_meta_spec.rb b/src/ruby_client/spec/models/response403_meta_spec.rb index 165abb0a..e90f6098 100644 --- a/src/ruby_client/spec/models/response403_meta_spec.rb +++ b/src/ruby_client/spec/models/response403_meta_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/response403_spec.rb b/src/ruby_client/spec/models/response403_spec.rb index ba68e84e..f56293ce 100644 --- a/src/ruby_client/spec/models/response403_spec.rb +++ b/src/ruby_client/spec/models/response403_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/response404_spec.rb b/src/ruby_client/spec/models/response404_spec.rb index 44884199..c983aeb5 100644 --- a/src/ruby_client/spec/models/response404_spec.rb +++ b/src/ruby_client/spec/models/response404_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/response405_meta_spec.rb b/src/ruby_client/spec/models/response405_meta_spec.rb index d4d0e6d6..87a690d7 100644 --- a/src/ruby_client/spec/models/response405_meta_spec.rb +++ b/src/ruby_client/spec/models/response405_meta_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/response405_spec.rb b/src/ruby_client/spec/models/response405_spec.rb index 9dbe2e6e..c6d31789 100644 --- a/src/ruby_client/spec/models/response405_spec.rb +++ b/src/ruby_client/spec/models/response405_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/response411_meta_spec.rb b/src/ruby_client/spec/models/response411_meta_spec.rb index b1578627..3adda3f8 100644 --- a/src/ruby_client/spec/models/response411_meta_spec.rb +++ b/src/ruby_client/spec/models/response411_meta_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/response411_spec.rb b/src/ruby_client/spec/models/response411_spec.rb index 55a7fc2f..338a306c 100644 --- a/src/ruby_client/spec/models/response411_spec.rb +++ b/src/ruby_client/spec/models/response411_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/response490_meta_spec.rb b/src/ruby_client/spec/models/response490_meta_spec.rb index f7a14900..0a743408 100644 --- a/src/ruby_client/spec/models/response490_meta_spec.rb +++ b/src/ruby_client/spec/models/response490_meta_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/response490_spec.rb b/src/ruby_client/spec/models/response490_spec.rb index aac54b22..19ad7a17 100644 --- a/src/ruby_client/spec/models/response490_spec.rb +++ b/src/ruby_client/spec/models/response490_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/response500_meta_spec.rb b/src/ruby_client/spec/models/response500_meta_spec.rb index fc25494c..23f3fe78 100644 --- a/src/ruby_client/spec/models/response500_meta_spec.rb +++ b/src/ruby_client/spec/models/response500_meta_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/response500_spec.rb b/src/ruby_client/spec/models/response500_spec.rb index 83dc3c39..c7c3dc9b 100644 --- a/src/ruby_client/spec/models/response500_spec.rb +++ b/src/ruby_client/spec/models/response500_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/role_category_spec.rb b/src/ruby_client/spec/models/role_category_spec.rb index d7d3ca7f..64357d6d 100644 --- a/src/ruby_client/spec/models/role_category_spec.rb +++ b/src/ruby_client/spec/models/role_category_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/roles_spec.rb b/src/ruby_client/spec/models/roles_spec.rb index 28b9ecf1..b86ed40c 100644 --- a/src/ruby_client/spec/models/roles_spec.rb +++ b/src/ruby_client/spec/models/roles_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/ssps_spec.rb b/src/ruby_client/spec/models/ssps_spec.rb index f147fafc..c8330c50 100644 --- a/src/ruby_client/spec/models/ssps_spec.rb +++ b/src/ruby_client/spec/models/ssps_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/stage_spec.rb b/src/ruby_client/spec/models/stage_spec.rb index fe1157ce..abb8b08e 100644 --- a/src/ruby_client/spec/models/stage_spec.rb +++ b/src/ruby_client/spec/models/stage_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/static_code_application_spec.rb b/src/ruby_client/spec/models/static_code_application_spec.rb index 7b3a33c0..9d90d98b 100644 --- a/src/ruby_client/spec/models/static_code_application_spec.rb +++ b/src/ruby_client/spec/models/static_code_application_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/static_code_post_spec.rb b/src/ruby_client/spec/models/static_code_post_spec.rb index effa3d72..24b01548 100644 --- a/src/ruby_client/spec/models/static_code_post_spec.rb +++ b/src/ruby_client/spec/models/static_code_post_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/static_code_request_post_body_application_spec.rb b/src/ruby_client/spec/models/static_code_request_post_body_application_spec.rb index 152b5c5c..852c28f5 100644 --- a/src/ruby_client/spec/models/static_code_request_post_body_application_spec.rb +++ b/src/ruby_client/spec/models/static_code_request_post_body_application_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/static_code_request_post_body_spec.rb b/src/ruby_client/spec/models/static_code_request_post_body_spec.rb index 638bd1fa..49c11f9e 100644 --- a/src/ruby_client/spec/models/static_code_request_post_body_spec.rb +++ b/src/ruby_client/spec/models/static_code_request_post_body_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/static_code_response_post_spec.rb b/src/ruby_client/spec/models/static_code_response_post_spec.rb index deae4b71..56547b03 100644 --- a/src/ruby_client/spec/models/static_code_response_post_spec.rb +++ b/src/ruby_client/spec/models/static_code_response_post_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/success200_response_data_inner_spec.rb b/src/ruby_client/spec/models/success200_response_data_inner_spec.rb index a2b056be..ecbd8e1f 100644 --- a/src/ruby_client/spec/models/success200_response_data_inner_spec.rb +++ b/src/ruby_client/spec/models/success200_response_data_inner_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/success200_response_spec.rb b/src/ruby_client/spec/models/success200_response_spec.rb index 72d8ed6b..f3130ac6 100644 --- a/src/ruby_client/spec/models/success200_response_spec.rb +++ b/src/ruby_client/spec/models/success200_response_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/system_response_spec.rb b/src/ruby_client/spec/models/system_response_spec.rb index ec8eac0f..0dea6eec 100644 --- a/src/ruby_client/spec/models/system_response_spec.rb +++ b/src/ruby_client/spec/models/system_response_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/system_roles_category_response_spec.rb b/src/ruby_client/spec/models/system_roles_category_response_spec.rb index 4208fa7a..98db0b20 100644 --- a/src/ruby_client/spec/models/system_roles_category_response_spec.rb +++ b/src/ruby_client/spec/models/system_roles_category_response_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/system_roles_response_data_inner_spec.rb b/src/ruby_client/spec/models/system_roles_response_data_inner_spec.rb index 0554845a..34a17956 100644 --- a/src/ruby_client/spec/models/system_roles_response_data_inner_spec.rb +++ b/src/ruby_client/spec/models/system_roles_response_data_inner_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/system_roles_response_spec.rb b/src/ruby_client/spec/models/system_roles_response_spec.rb index c47191e2..c751694c 100644 --- a/src/ruby_client/spec/models/system_roles_response_spec.rb +++ b/src/ruby_client/spec/models/system_roles_response_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/systems_response_spec.rb b/src/ruby_client/spec/models/systems_response_spec.rb index d34f8725..05cf358a 100644 --- a/src/ruby_client/spec/models/systems_response_spec.rb +++ b/src/ruby_client/spec/models/systems_response_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/systems_spec.rb b/src/ruby_client/spec/models/systems_spec.rb index 32a29943..5dc07837 100644 --- a/src/ruby_client/spec/models/systems_spec.rb +++ b/src/ruby_client/spec/models/systems_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/test_data_spec.rb b/src/ruby_client/spec/models/test_data_spec.rb index 937d71dd..018d879b 100644 --- a/src/ruby_client/spec/models/test_data_spec.rb +++ b/src/ruby_client/spec/models/test_data_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/test_results_get_spec.rb b/src/ruby_client/spec/models/test_results_get_spec.rb index 79ccbc15..c21a8cc4 100644 --- a/src/ruby_client/spec/models/test_results_get_spec.rb +++ b/src/ruby_client/spec/models/test_results_get_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/test_results_post_spec.rb b/src/ruby_client/spec/models/test_results_post_spec.rb index 59a97f4f..332d8db3 100644 --- a/src/ruby_client/spec/models/test_results_post_spec.rb +++ b/src/ruby_client/spec/models/test_results_post_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/test_results_response_get_spec.rb b/src/ruby_client/spec/models/test_results_response_get_spec.rb index 96b3321b..7ac36957 100644 --- a/src/ruby_client/spec/models/test_results_response_get_spec.rb +++ b/src/ruby_client/spec/models/test_results_response_get_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/test_results_response_post_spec.rb b/src/ruby_client/spec/models/test_results_response_post_spec.rb index 1e712e9c..52416864 100644 --- a/src/ruby_client/spec/models/test_results_response_post_spec.rb +++ b/src/ruby_client/spec/models/test_results_response_post_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/test_spec.rb b/src/ruby_client/spec/models/test_spec.rb index 971e8d1a..4786783e 100644 --- a/src/ruby_client/spec/models/test_spec.rb +++ b/src/ruby_client/spec/models/test_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/users_spec.rb b/src/ruby_client/spec/models/users_spec.rb index 371acec8..71aa1db1 100644 --- a/src/ruby_client/spec/models/users_spec.rb +++ b/src/ruby_client/spec/models/users_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/workflow_definition_get_spec.rb b/src/ruby_client/spec/models/workflow_definition_get_spec.rb index da27a0fc..fff2b546 100644 --- a/src/ruby_client/spec/models/workflow_definition_get_spec.rb +++ b/src/ruby_client/spec/models/workflow_definition_get_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/workflow_definition_response_get_spec.rb b/src/ruby_client/spec/models/workflow_definition_response_get_spec.rb index 67c68366..a720b36e 100644 --- a/src/ruby_client/spec/models/workflow_definition_response_get_spec.rb +++ b/src/ruby_client/spec/models/workflow_definition_response_get_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/workflow_instance_get_spec.rb b/src/ruby_client/spec/models/workflow_instance_get_spec.rb index 3f37e1c3..0b46cb34 100644 --- a/src/ruby_client/spec/models/workflow_instance_get_spec.rb +++ b/src/ruby_client/spec/models/workflow_instance_get_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/workflow_instance_response_get_spec.rb b/src/ruby_client/spec/models/workflow_instance_response_get_spec.rb index ccc21b5d..122848bd 100644 --- a/src/ruby_client/spec/models/workflow_instance_response_get_spec.rb +++ b/src/ruby_client/spec/models/workflow_instance_response_get_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/workflow_instances_get_spec.rb b/src/ruby_client/spec/models/workflow_instances_get_spec.rb index e7db6140..794bdc54 100644 --- a/src/ruby_client/spec/models/workflow_instances_get_spec.rb +++ b/src/ruby_client/spec/models/workflow_instances_get_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/workflow_instances_response_get_pagination_spec.rb b/src/ruby_client/spec/models/workflow_instances_response_get_pagination_spec.rb index 9f8d8ea1..2da1609f 100644 --- a/src/ruby_client/spec/models/workflow_instances_response_get_pagination_spec.rb +++ b/src/ruby_client/spec/models/workflow_instances_response_get_pagination_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/models/workflow_instances_response_get_spec.rb b/src/ruby_client/spec/models/workflow_instances_response_get_spec.rb index 76d57271..9014be6c 100644 --- a/src/ruby_client/spec/models/workflow_instances_response_get_spec.rb +++ b/src/ruby_client/spec/models/workflow_instances_response_get_spec.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/ruby_client/spec/spec_helper.rb b/src/ruby_client/spec/spec_helper.rb index 90608598..7532e70f 100644 --- a/src/ruby_client/spec/spec_helper.rb +++ b/src/ruby_client/spec/spec_helper.rb @@ -3,10 +3,10 @@ #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: -The version of the OpenAPI document: v3.3 +The version of the OpenAPI document: v3.4 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://openapi-generator.tech -OpenAPI Generator version: 6.0.1-SNAPSHOT +OpenAPI Generator version: 6.1.1-SNAPSHOT =end diff --git a/src/typescript_client/.openapi-generator/VERSION b/src/typescript_client/.openapi-generator/VERSION index 89648de3..7b7e20b5 100644 --- a/src/typescript_client/.openapi-generator/VERSION +++ b/src/typescript_client/.openapi-generator/VERSION @@ -1 +1 @@ -6.0.1-SNAPSHOT \ No newline at end of file +6.1.1-SNAPSHOT \ No newline at end of file diff --git a/src/typescript_client/README.md b/src/typescript_client/README.md index 34ba9295..761a85a5 100644 --- a/src/typescript_client/README.md +++ b/src/typescript_client/README.md @@ -1,4 +1,4 @@ -## @mitre/emass_client@1.0.6 +## @mitre/emass_client@3.4.0 This generator creates TypeScript/JavaScript client that utilizes [axios](https://github.com/axios/axios). The generated Node module can be used in the following environments: @@ -59,7 +59,7 @@ navigate to the folder of your consuming project and run one of the following co _published:_ ``` -npm install @mitre/emass_client@1.0.6 --save +npm install @mitre/emass_client@3.4.0 --save ``` _unPublished (not recommended):_ @@ -72,7 +72,7 @@ npm install PATH_TO_GENERATED_PACKAGE --save Before accessing any of the endpoints provided by the @mitre/emass_client, we need to configure common axios settings. ### Axios Configuration -All calls utilizing the @mitre/emass_client@1.0.6 need to initialize axios as follows: +All calls utilizing the @mitre/emass_client@3.4.0 need to initialize axios as follows: ```typescript // Load the necessary modules diff --git a/src/typescript_client/api.ts b/src/typescript_client/api.ts index dcc9be28..8afb24b4 100644 --- a/src/typescript_client/api.ts +++ b/src/typescript_client/api.ts @@ -4,7 +4,7 @@ * Enterprise Mission Assurance Support Service (eMASS) * 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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: * - * The version of the OpenAPI document: v3.3 + * The version of the OpenAPI document: v3.4 * Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). @@ -3618,14 +3618,14 @@ export const ArtifactsApiAxiosParamCreator = function (configuration?: Configura * Information
The request body of a POST request through the Artifact Endpoint accepts a single binary file with file extension \".zip\" only. This accepted .zip file should contain one or more files corresponding to existing artifacts or new artifacts that will be created upon successful receipt. Filename uniqueness throughout eMASS will be enforced by the API.

Upon successful receipt of a file, if a file within the .zip 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 blank.
  • isTemplate: false
  • type: other
  • category: evidence
To update values other than the file itself, please submit a PUT request.
Zip file information
Upload a zip file contain one or more files corresponding to existing artifacts or new artifacts that will be created upon successful receipt.

Business Rules
Artifact cannot be saved if the file does not have the following file extensions: .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. * @summary Add one or many artifacts in a system * @param {number} systemId **System Id**: The unique system record identifier. - * @param {any} zipper + * @param {File} zipper * @param {boolean} [isTemplate] * @param {string} [type] * @param {string} [category] * @param {*} [options] Override http request option. * @throws {RequiredError} */ - addArtifactsBySystemId: async (systemId: number, zipper: any, isTemplate?: boolean, type?: string, category?: string, options: AxiosRequestConfig = {}): Promise => { + addArtifactsBySystemId: async (systemId: number, zipper: File, isTemplate?: boolean, type?: string, category?: string, options: AxiosRequestConfig = {}): Promise => { // verify required parameter 'systemId' is not null or undefined assertParamExists('addArtifactsBySystemId', 'systemId', systemId) // verify required parameter 'zipper' is not null or undefined @@ -3858,14 +3858,14 @@ export const ArtifactsApiFp = function(configuration?: Configuration) { * Information
The request body of a POST request through the Artifact Endpoint accepts a single binary file with file extension \".zip\" only. This accepted .zip file should contain one or more files corresponding to existing artifacts or new artifacts that will be created upon successful receipt. Filename uniqueness throughout eMASS will be enforced by the API.

Upon successful receipt of a file, if a file within the .zip 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 blank.
  • isTemplate: false
  • type: other
  • category: evidence
To update values other than the file itself, please submit a PUT request.
Zip file information
Upload a zip file contain one or more files corresponding to existing artifacts or new artifacts that will be created upon successful receipt.

Business Rules
Artifact cannot be saved if the file does not have the following file extensions: .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. * @summary Add one or many artifacts in a system * @param {number} systemId **System Id**: The unique system record identifier. - * @param {any} zipper + * @param {File} zipper * @param {boolean} [isTemplate] * @param {string} [type] * @param {string} [category] * @param {*} [options] Override http request option. * @throws {RequiredError} */ - async addArtifactsBySystemId(systemId: number, zipper: any, isTemplate?: boolean, type?: string, category?: string, options?: AxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise> { + async addArtifactsBySystemId(systemId: number, zipper: File, isTemplate?: boolean, type?: string, category?: string, options?: AxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise> { const localVarAxiosArgs = await localVarAxiosParamCreator.addArtifactsBySystemId(systemId, zipper, isTemplate, type, category, options); return createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration); }, @@ -3922,14 +3922,14 @@ export const ArtifactsApiFactory = function (configuration?: Configuration, base * Information
The request body of a POST request through the Artifact Endpoint accepts a single binary file with file extension \".zip\" only. This accepted .zip file should contain one or more files corresponding to existing artifacts or new artifacts that will be created upon successful receipt. Filename uniqueness throughout eMASS will be enforced by the API.

Upon successful receipt of a file, if a file within the .zip 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 blank.
  • isTemplate: false
  • type: other
  • category: evidence
To update values other than the file itself, please submit a PUT request.
Zip file information
Upload a zip file contain one or more files corresponding to existing artifacts or new artifacts that will be created upon successful receipt.

Business Rules
Artifact cannot be saved if the file does not have the following file extensions: .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. * @summary Add one or many artifacts in a system * @param {number} systemId **System Id**: The unique system record identifier. - * @param {any} zipper + * @param {File} zipper * @param {boolean} [isTemplate] * @param {string} [type] * @param {string} [category] * @param {*} [options] Override http request option. * @throws {RequiredError} */ - addArtifactsBySystemId(systemId: number, zipper: any, isTemplate?: boolean, type?: string, category?: string, options?: any): AxiosPromise { + addArtifactsBySystemId(systemId: number, zipper: File, isTemplate?: boolean, type?: string, category?: string, options?: any): AxiosPromise { return localVarFp.addArtifactsBySystemId(systemId, zipper, isTemplate, type, category, options).then((request) => request(axios, basePath)); }, /** @@ -3982,7 +3982,7 @@ export class ArtifactsApi extends BaseAPI { * Information
The request body of a POST request through the Artifact Endpoint accepts a single binary file with file extension \".zip\" only. This accepted .zip file should contain one or more files corresponding to existing artifacts or new artifacts that will be created upon successful receipt. Filename uniqueness throughout eMASS will be enforced by the API.

Upon successful receipt of a file, if a file within the .zip 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 blank.
  • isTemplate: false
  • type: other
  • category: evidence
To update values other than the file itself, please submit a PUT request.
Zip file information
Upload a zip file contain one or more files corresponding to existing artifacts or new artifacts that will be created upon successful receipt.

Business Rules
Artifact cannot be saved if the file does not have the following file extensions: .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. * @summary Add one or many artifacts in a system * @param {number} systemId **System Id**: The unique system record identifier. - * @param {any} zipper + * @param {File} zipper * @param {boolean} [isTemplate] * @param {string} [type] * @param {string} [category] @@ -3990,7 +3990,7 @@ export class ArtifactsApi extends BaseAPI { * @throws {RequiredError} * @memberof ArtifactsApi */ - public addArtifactsBySystemId(systemId: number, zipper: any, isTemplate?: boolean, type?: string, category?: string, options?: AxiosRequestConfig) { + public addArtifactsBySystemId(systemId: number, zipper: File, isTemplate?: boolean, type?: string, category?: string, options?: AxiosRequestConfig) { return ArtifactsApiFp(this.configuration).addArtifactsBySystemId(systemId, zipper, isTemplate, type, category, options).then((request) => request(this.axios, this.basePath)); } @@ -4118,7 +4118,7 @@ export const ArtifactsExportApiFp = function(configuration?: Configuration) { * @param {*} [options] Override http request option. * @throws {RequiredError} */ - async getSystemArtifactsExport(systemId: number, filename: string, compress?: boolean, options?: AxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise> { + async getSystemArtifactsExport(systemId: number, filename: string, compress?: boolean, options?: AxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise> { const localVarAxiosArgs = await localVarAxiosParamCreator.getSystemArtifactsExport(systemId, filename, compress, options); return createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration); }, @@ -4141,7 +4141,7 @@ export const ArtifactsExportApiFactory = function (configuration?: Configuration * @param {*} [options] Override http request option. * @throws {RequiredError} */ - getSystemArtifactsExport(systemId: number, filename: string, compress?: boolean, options?: any): AxiosPromise { + getSystemArtifactsExport(systemId: number, filename: string, compress?: boolean, options?: any): AxiosPromise { return localVarFp.getSystemArtifactsExport(systemId, filename, compress, options).then((request) => request(axios, basePath)); }, }; @@ -4947,6 +4947,1564 @@ export class ControlsApi extends BaseAPI { } +/** + * DashboardsApi - axios parameter creator + * @export + */ +export const DashboardsApiAxiosParamCreator = function (configuration?: Configuration) { + return { + /** + * Get systems assessement procdures details dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + getSystemAssessmentProceduresDetails: async (orgId: number, pageIndex?: number, pageSize?: number, options: AxiosRequestConfig = {}): Promise => { + // verify required parameter 'orgId' is not null or undefined + assertParamExists('getSystemAssessmentProceduresDetails', 'orgId', orgId) + const localVarPath = `/api/dashboards/system-assessment-procedures-details`; + // use dummy base URL string because the URL constructor only accepts absolute URLs. + const localVarUrlObj = new URL(localVarPath, DUMMY_BASE_URL); + let baseOptions; + if (configuration) { + baseOptions = configuration.baseOptions; + } + + const localVarRequestOptions = { method: 'GET', ...baseOptions, ...options}; + const localVarHeaderParameter = {} as any; + const localVarQueryParameter = {} as any; + + // authentication apiKey required + await setApiKeyToObject(localVarHeaderParameter, "api-key", configuration) + + // authentication mockType required + await setApiKeyToObject(localVarHeaderParameter, "Prefer", configuration) + + // authentication userId required + await setApiKeyToObject(localVarHeaderParameter, "user-uid", configuration) + + if (orgId !== undefined) { + localVarQueryParameter['orgId'] = orgId; + } + + if (pageIndex !== undefined) { + localVarQueryParameter['pageIndex'] = pageIndex; + } + + if (pageSize !== undefined) { + localVarQueryParameter['pageSize'] = pageSize; + } + + + + setSearchParams(localVarUrlObj, localVarQueryParameter); + let headersFromBaseOptions = baseOptions && baseOptions.headers ? baseOptions.headers : {}; + localVarRequestOptions.headers = {...localVarHeaderParameter, ...headersFromBaseOptions, ...options.headers}; + + return { + url: toPathString(localVarUrlObj), + options: localVarRequestOptions, + }; + }, + /** + * Get system associations details dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + getSystemAssociationsDetails: async (orgId: number, pageIndex?: number, pageSize?: number, options: AxiosRequestConfig = {}): Promise => { + // verify required parameter 'orgId' is not null or undefined + assertParamExists('getSystemAssociationsDetails', 'orgId', orgId) + const localVarPath = `/api/dashboards/system-associations-details`; + // use dummy base URL string because the URL constructor only accepts absolute URLs. + const localVarUrlObj = new URL(localVarPath, DUMMY_BASE_URL); + let baseOptions; + if (configuration) { + baseOptions = configuration.baseOptions; + } + + const localVarRequestOptions = { method: 'GET', ...baseOptions, ...options}; + const localVarHeaderParameter = {} as any; + const localVarQueryParameter = {} as any; + + // authentication apiKey required + await setApiKeyToObject(localVarHeaderParameter, "api-key", configuration) + + // authentication mockType required + await setApiKeyToObject(localVarHeaderParameter, "Prefer", configuration) + + // authentication userId required + await setApiKeyToObject(localVarHeaderParameter, "user-uid", configuration) + + if (orgId !== undefined) { + localVarQueryParameter['orgId'] = orgId; + } + + if (pageIndex !== undefined) { + localVarQueryParameter['pageIndex'] = pageIndex; + } + + if (pageSize !== undefined) { + localVarQueryParameter['pageSize'] = pageSize; + } + + + + setSearchParams(localVarUrlObj, localVarQueryParameter); + let headersFromBaseOptions = baseOptions && baseOptions.headers ? baseOptions.headers : {}; + localVarRequestOptions.headers = {...localVarHeaderParameter, ...headersFromBaseOptions, ...options.headers}; + + return { + url: toPathString(localVarUrlObj), + options: localVarRequestOptions, + }; + }, + /** + * Get systems control compliance summary dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + getSystemControlComplianceSummary: async (orgId: number, pageIndex?: number, pageSize?: number, options: AxiosRequestConfig = {}): Promise => { + // verify required parameter 'orgId' is not null or undefined + assertParamExists('getSystemControlComplianceSummary', 'orgId', orgId) + const localVarPath = `/api/dashboards/system-control-compliance-summary`; + // use dummy base URL string because the URL constructor only accepts absolute URLs. + const localVarUrlObj = new URL(localVarPath, DUMMY_BASE_URL); + let baseOptions; + if (configuration) { + baseOptions = configuration.baseOptions; + } + + const localVarRequestOptions = { method: 'GET', ...baseOptions, ...options}; + const localVarHeaderParameter = {} as any; + const localVarQueryParameter = {} as any; + + // authentication apiKey required + await setApiKeyToObject(localVarHeaderParameter, "api-key", configuration) + + // authentication mockType required + await setApiKeyToObject(localVarHeaderParameter, "Prefer", configuration) + + // authentication userId required + await setApiKeyToObject(localVarHeaderParameter, "user-uid", configuration) + + if (orgId !== undefined) { + localVarQueryParameter['orgId'] = orgId; + } + + if (pageIndex !== undefined) { + localVarQueryParameter['pageIndex'] = pageIndex; + } + + if (pageSize !== undefined) { + localVarQueryParameter['pageSize'] = pageSize; + } + + + + setSearchParams(localVarUrlObj, localVarQueryParameter); + let headersFromBaseOptions = baseOptions && baseOptions.headers ? baseOptions.headers : {}; + localVarRequestOptions.headers = {...localVarHeaderParameter, ...headersFromBaseOptions, ...options.headers}; + + return { + url: toPathString(localVarUrlObj), + options: localVarRequestOptions, + }; + }, + /** + * Get system hardware details dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + getSystemHardwareDetails: async (orgId: number, pageIndex?: number, pageSize?: number, options: AxiosRequestConfig = {}): Promise => { + // verify required parameter 'orgId' is not null or undefined + assertParamExists('getSystemHardwareDetails', 'orgId', orgId) + const localVarPath = `/api/dashboards/system-hardware-details`; + // use dummy base URL string because the URL constructor only accepts absolute URLs. + const localVarUrlObj = new URL(localVarPath, DUMMY_BASE_URL); + let baseOptions; + if (configuration) { + baseOptions = configuration.baseOptions; + } + + const localVarRequestOptions = { method: 'GET', ...baseOptions, ...options}; + const localVarHeaderParameter = {} as any; + const localVarQueryParameter = {} as any; + + // authentication apiKey required + await setApiKeyToObject(localVarHeaderParameter, "api-key", configuration) + + // authentication mockType required + await setApiKeyToObject(localVarHeaderParameter, "Prefer", configuration) + + // authentication userId required + await setApiKeyToObject(localVarHeaderParameter, "user-uid", configuration) + + if (orgId !== undefined) { + localVarQueryParameter['orgId'] = orgId; + } + + if (pageIndex !== undefined) { + localVarQueryParameter['pageIndex'] = pageIndex; + } + + if (pageSize !== undefined) { + localVarQueryParameter['pageSize'] = pageSize; + } + + + + setSearchParams(localVarUrlObj, localVarQueryParameter); + let headersFromBaseOptions = baseOptions && baseOptions.headers ? baseOptions.headers : {}; + localVarRequestOptions.headers = {...localVarHeaderParameter, ...headersFromBaseOptions, ...options.headers}; + + return { + url: toPathString(localVarUrlObj), + options: localVarRequestOptions, + }; + }, + /** + * Get system hardware summary dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + getSystemHardwareSummary: async (orgId: number, pageIndex?: number, pageSize?: number, options: AxiosRequestConfig = {}): Promise => { + // verify required parameter 'orgId' is not null or undefined + assertParamExists('getSystemHardwareSummary', 'orgId', orgId) + const localVarPath = `/api/dashboards/system-hardware-summary`; + // use dummy base URL string because the URL constructor only accepts absolute URLs. + const localVarUrlObj = new URL(localVarPath, DUMMY_BASE_URL); + let baseOptions; + if (configuration) { + baseOptions = configuration.baseOptions; + } + + const localVarRequestOptions = { method: 'GET', ...baseOptions, ...options}; + const localVarHeaderParameter = {} as any; + const localVarQueryParameter = {} as any; + + // authentication apiKey required + await setApiKeyToObject(localVarHeaderParameter, "api-key", configuration) + + // authentication mockType required + await setApiKeyToObject(localVarHeaderParameter, "Prefer", configuration) + + // authentication userId required + await setApiKeyToObject(localVarHeaderParameter, "user-uid", configuration) + + if (orgId !== undefined) { + localVarQueryParameter['orgId'] = orgId; + } + + if (pageIndex !== undefined) { + localVarQueryParameter['pageIndex'] = pageIndex; + } + + if (pageSize !== undefined) { + localVarQueryParameter['pageSize'] = pageSize; + } + + + + setSearchParams(localVarUrlObj, localVarQueryParameter); + let headersFromBaseOptions = baseOptions && baseOptions.headers ? baseOptions.headers : {}; + localVarRequestOptions.headers = {...localVarHeaderParameter, ...headersFromBaseOptions, ...options.headers}; + + return { + url: toPathString(localVarUrlObj), + options: localVarRequestOptions, + }; + }, + /** + * Get system POA&Ms details dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + getSystemPoamDetails: async (orgId: number, pageIndex?: number, pageSize?: number, options: AxiosRequestConfig = {}): Promise => { + // verify required parameter 'orgId' is not null or undefined + assertParamExists('getSystemPoamDetails', 'orgId', orgId) + const localVarPath = `/api/dashboards/system-poam-details`; + // use dummy base URL string because the URL constructor only accepts absolute URLs. + const localVarUrlObj = new URL(localVarPath, DUMMY_BASE_URL); + let baseOptions; + if (configuration) { + baseOptions = configuration.baseOptions; + } + + const localVarRequestOptions = { method: 'GET', ...baseOptions, ...options}; + const localVarHeaderParameter = {} as any; + const localVarQueryParameter = {} as any; + + // authentication apiKey required + await setApiKeyToObject(localVarHeaderParameter, "api-key", configuration) + + // authentication mockType required + await setApiKeyToObject(localVarHeaderParameter, "Prefer", configuration) + + // authentication userId required + await setApiKeyToObject(localVarHeaderParameter, "user-uid", configuration) + + if (orgId !== undefined) { + localVarQueryParameter['orgId'] = orgId; + } + + if (pageIndex !== undefined) { + localVarQueryParameter['pageIndex'] = pageIndex; + } + + if (pageSize !== undefined) { + localVarQueryParameter['pageSize'] = pageSize; + } + + + + setSearchParams(localVarUrlObj, localVarQueryParameter); + let headersFromBaseOptions = baseOptions && baseOptions.headers ? baseOptions.headers : {}; + localVarRequestOptions.headers = {...localVarHeaderParameter, ...headersFromBaseOptions, ...options.headers}; + + return { + url: toPathString(localVarUrlObj), + options: localVarRequestOptions, + }; + }, + /** + * Get systems POA&Ms summary dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + getSystemPoamSummary: async (orgId: number, pageIndex?: number, pageSize?: number, options: AxiosRequestConfig = {}): Promise => { + // verify required parameter 'orgId' is not null or undefined + assertParamExists('getSystemPoamSummary', 'orgId', orgId) + const localVarPath = `/api/dashboards/system-poam-summary`; + // use dummy base URL string because the URL constructor only accepts absolute URLs. + const localVarUrlObj = new URL(localVarPath, DUMMY_BASE_URL); + let baseOptions; + if (configuration) { + baseOptions = configuration.baseOptions; + } + + const localVarRequestOptions = { method: 'GET', ...baseOptions, ...options}; + const localVarHeaderParameter = {} as any; + const localVarQueryParameter = {} as any; + + // authentication apiKey required + await setApiKeyToObject(localVarHeaderParameter, "api-key", configuration) + + // authentication mockType required + await setApiKeyToObject(localVarHeaderParameter, "Prefer", configuration) + + // authentication userId required + await setApiKeyToObject(localVarHeaderParameter, "user-uid", configuration) + + if (orgId !== undefined) { + localVarQueryParameter['orgId'] = orgId; + } + + if (pageIndex !== undefined) { + localVarQueryParameter['pageIndex'] = pageIndex; + } + + if (pageSize !== undefined) { + localVarQueryParameter['pageSize'] = pageSize; + } + + + + setSearchParams(localVarUrlObj, localVarQueryParameter); + let headersFromBaseOptions = baseOptions && baseOptions.headers ? baseOptions.headers : {}; + localVarRequestOptions.headers = {...localVarHeaderParameter, ...headersFromBaseOptions, ...options.headers}; + + return { + url: toPathString(localVarUrlObj), + options: localVarRequestOptions, + }; + }, + /** + * Get user system privacy summary dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + getSystemPrivacySummary: async (orgId: number, pageIndex?: number, pageSize?: number, options: AxiosRequestConfig = {}): Promise => { + // verify required parameter 'orgId' is not null or undefined + assertParamExists('getSystemPrivacySummary', 'orgId', orgId) + const localVarPath = `/api/dashboards/system-privacy-summary`; + // use dummy base URL string because the URL constructor only accepts absolute URLs. + const localVarUrlObj = new URL(localVarPath, DUMMY_BASE_URL); + let baseOptions; + if (configuration) { + baseOptions = configuration.baseOptions; + } + + const localVarRequestOptions = { method: 'GET', ...baseOptions, ...options}; + const localVarHeaderParameter = {} as any; + const localVarQueryParameter = {} as any; + + // authentication apiKey required + await setApiKeyToObject(localVarHeaderParameter, "api-key", configuration) + + // authentication mockType required + await setApiKeyToObject(localVarHeaderParameter, "Prefer", configuration) + + // authentication userId required + await setApiKeyToObject(localVarHeaderParameter, "user-uid", configuration) + + if (orgId !== undefined) { + localVarQueryParameter['orgId'] = orgId; + } + + if (pageIndex !== undefined) { + localVarQueryParameter['pageIndex'] = pageIndex; + } + + if (pageSize !== undefined) { + localVarQueryParameter['pageSize'] = pageSize; + } + + + + setSearchParams(localVarUrlObj, localVarQueryParameter); + let headersFromBaseOptions = baseOptions && baseOptions.headers ? baseOptions.headers : {}; + localVarRequestOptions.headers = {...localVarHeaderParameter, ...headersFromBaseOptions, ...options.headers}; + + return { + url: toPathString(localVarUrlObj), + options: localVarRequestOptions, + }; + }, + /** + * Get systems security control details dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + getSystemSecurityControlDetails: async (orgId: number, pageIndex?: number, pageSize?: number, options: AxiosRequestConfig = {}): Promise => { + // verify required parameter 'orgId' is not null or undefined + assertParamExists('getSystemSecurityControlDetails', 'orgId', orgId) + const localVarPath = `/api/dashboards/system-security-controls-details`; + // use dummy base URL string because the URL constructor only accepts absolute URLs. + const localVarUrlObj = new URL(localVarPath, DUMMY_BASE_URL); + let baseOptions; + if (configuration) { + baseOptions = configuration.baseOptions; + } + + const localVarRequestOptions = { method: 'GET', ...baseOptions, ...options}; + const localVarHeaderParameter = {} as any; + const localVarQueryParameter = {} as any; + + // authentication apiKey required + await setApiKeyToObject(localVarHeaderParameter, "api-key", configuration) + + // authentication mockType required + await setApiKeyToObject(localVarHeaderParameter, "Prefer", configuration) + + // authentication userId required + await setApiKeyToObject(localVarHeaderParameter, "user-uid", configuration) + + if (orgId !== undefined) { + localVarQueryParameter['orgId'] = orgId; + } + + if (pageIndex !== undefined) { + localVarQueryParameter['pageIndex'] = pageIndex; + } + + if (pageSize !== undefined) { + localVarQueryParameter['pageSize'] = pageSize; + } + + + + setSearchParams(localVarUrlObj, localVarQueryParameter); + let headersFromBaseOptions = baseOptions && baseOptions.headers ? baseOptions.headers : {}; + localVarRequestOptions.headers = {...localVarHeaderParameter, ...headersFromBaseOptions, ...options.headers}; + + return { + url: toPathString(localVarUrlObj), + options: localVarRequestOptions, + }; + }, + /** + * Get systems status detail dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + getSystemStatusDetails: async (orgId: number, pageIndex?: number, pageSize?: number, options: AxiosRequestConfig = {}): Promise => { + // verify required parameter 'orgId' is not null or undefined + assertParamExists('getSystemStatusDetails', 'orgId', orgId) + const localVarPath = `/api/dashboards/system-status-details`; + // use dummy base URL string because the URL constructor only accepts absolute URLs. + const localVarUrlObj = new URL(localVarPath, DUMMY_BASE_URL); + let baseOptions; + if (configuration) { + baseOptions = configuration.baseOptions; + } + + const localVarRequestOptions = { method: 'GET', ...baseOptions, ...options}; + const localVarHeaderParameter = {} as any; + const localVarQueryParameter = {} as any; + + // authentication apiKey required + await setApiKeyToObject(localVarHeaderParameter, "api-key", configuration) + + // authentication mockType required + await setApiKeyToObject(localVarHeaderParameter, "Prefer", configuration) + + // authentication userId required + await setApiKeyToObject(localVarHeaderParameter, "user-uid", configuration) + + if (orgId !== undefined) { + localVarQueryParameter['orgId'] = orgId; + } + + if (pageIndex !== undefined) { + localVarQueryParameter['pageIndex'] = pageIndex; + } + + if (pageSize !== undefined) { + localVarQueryParameter['pageSize'] = pageSize; + } + + + + setSearchParams(localVarUrlObj, localVarQueryParameter); + let headersFromBaseOptions = baseOptions && baseOptions.headers ? baseOptions.headers : {}; + localVarRequestOptions.headers = {...localVarHeaderParameter, ...headersFromBaseOptions, ...options.headers}; + + return { + url: toPathString(localVarUrlObj), + options: localVarRequestOptions, + }; + }, + /** + * Get user system assignments details dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + getUserSystemAssignmentsDetails: async (orgId: number, pageIndex?: number, pageSize?: number, options: AxiosRequestConfig = {}): Promise => { + // verify required parameter 'orgId' is not null or undefined + assertParamExists('getUserSystemAssignmentsDetails', 'orgId', orgId) + const localVarPath = `/api/dashboards/user-system-assignments-details`; + // use dummy base URL string because the URL constructor only accepts absolute URLs. + const localVarUrlObj = new URL(localVarPath, DUMMY_BASE_URL); + let baseOptions; + if (configuration) { + baseOptions = configuration.baseOptions; + } + + const localVarRequestOptions = { method: 'GET', ...baseOptions, ...options}; + const localVarHeaderParameter = {} as any; + const localVarQueryParameter = {} as any; + + // authentication apiKey required + await setApiKeyToObject(localVarHeaderParameter, "api-key", configuration) + + // authentication mockType required + await setApiKeyToObject(localVarHeaderParameter, "Prefer", configuration) + + // authentication userId required + await setApiKeyToObject(localVarHeaderParameter, "user-uid", configuration) + + if (orgId !== undefined) { + localVarQueryParameter['orgId'] = orgId; + } + + if (pageIndex !== undefined) { + localVarQueryParameter['pageIndex'] = pageIndex; + } + + if (pageSize !== undefined) { + localVarQueryParameter['pageSize'] = pageSize; + } + + + + setSearchParams(localVarUrlObj, localVarQueryParameter); + let headersFromBaseOptions = baseOptions && baseOptions.headers ? baseOptions.headers : {}; + localVarRequestOptions.headers = {...localVarHeaderParameter, ...headersFromBaseOptions, ...options.headers}; + + return { + url: toPathString(localVarUrlObj), + options: localVarRequestOptions, + }; + }, + /** + * Get VA OMB-FISMA SAOP summary dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + getVaOmbFsmaSaopSummary: async (orgId: number, pageIndex?: number, pageSize?: number, options: AxiosRequestConfig = {}): Promise => { + // verify required parameter 'orgId' is not null or undefined + assertParamExists('getVaOmbFsmaSaopSummary', 'orgId', orgId) + const localVarPath = `/api/dashboards/va-omb-fisma-saop-summary`; + // use dummy base URL string because the URL constructor only accepts absolute URLs. + const localVarUrlObj = new URL(localVarPath, DUMMY_BASE_URL); + let baseOptions; + if (configuration) { + baseOptions = configuration.baseOptions; + } + + const localVarRequestOptions = { method: 'GET', ...baseOptions, ...options}; + const localVarHeaderParameter = {} as any; + const localVarQueryParameter = {} as any; + + // authentication apiKey required + await setApiKeyToObject(localVarHeaderParameter, "api-key", configuration) + + // authentication mockType required + await setApiKeyToObject(localVarHeaderParameter, "Prefer", configuration) + + // authentication userId required + await setApiKeyToObject(localVarHeaderParameter, "user-uid", configuration) + + if (orgId !== undefined) { + localVarQueryParameter['orgId'] = orgId; + } + + if (pageIndex !== undefined) { + localVarQueryParameter['pageIndex'] = pageIndex; + } + + if (pageSize !== undefined) { + localVarQueryParameter['pageSize'] = pageSize; + } + + + + setSearchParams(localVarUrlObj, localVarQueryParameter); + let headersFromBaseOptions = baseOptions && baseOptions.headers ? baseOptions.headers : {}; + localVarRequestOptions.headers = {...localVarHeaderParameter, ...headersFromBaseOptions, ...options.headers}; + + return { + url: toPathString(localVarUrlObj), + options: localVarRequestOptions, + }; + }, + /** + * Get VA system A2.0 summary dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + getVaSystemA2Summary: async (orgId: number, pageIndex?: number, pageSize?: number, options: AxiosRequestConfig = {}): Promise => { + // verify required parameter 'orgId' is not null or undefined + assertParamExists('getVaSystemA2Summary', 'orgId', orgId) + const localVarPath = `/api/dashboards/va-system-a2-summary`; + // use dummy base URL string because the URL constructor only accepts absolute URLs. + const localVarUrlObj = new URL(localVarPath, DUMMY_BASE_URL); + let baseOptions; + if (configuration) { + baseOptions = configuration.baseOptions; + } + + const localVarRequestOptions = { method: 'GET', ...baseOptions, ...options}; + const localVarHeaderParameter = {} as any; + const localVarQueryParameter = {} as any; + + // authentication apiKey required + await setApiKeyToObject(localVarHeaderParameter, "api-key", configuration) + + // authentication mockType required + await setApiKeyToObject(localVarHeaderParameter, "Prefer", configuration) + + // authentication userId required + await setApiKeyToObject(localVarHeaderParameter, "user-uid", configuration) + + if (orgId !== undefined) { + localVarQueryParameter['orgId'] = orgId; + } + + if (pageIndex !== undefined) { + localVarQueryParameter['pageIndex'] = pageIndex; + } + + if (pageSize !== undefined) { + localVarQueryParameter['pageSize'] = pageSize; + } + + + + setSearchParams(localVarUrlObj, localVarQueryParameter); + let headersFromBaseOptions = baseOptions && baseOptions.headers ? baseOptions.headers : {}; + localVarRequestOptions.headers = {...localVarHeaderParameter, ...headersFromBaseOptions, ...options.headers}; + + return { + url: toPathString(localVarUrlObj), + options: localVarRequestOptions, + }; + }, + /** + * Get VA system A&A summary dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + getVaSystemAaSummary: async (orgId: number, pageIndex?: number, pageSize?: number, options: AxiosRequestConfig = {}): Promise => { + // verify required parameter 'orgId' is not null or undefined + assertParamExists('getVaSystemAaSummary', 'orgId', orgId) + const localVarPath = `/api/dashboards/va-system-aa-summary`; + // use dummy base URL string because the URL constructor only accepts absolute URLs. + const localVarUrlObj = new URL(localVarPath, DUMMY_BASE_URL); + let baseOptions; + if (configuration) { + baseOptions = configuration.baseOptions; + } + + const localVarRequestOptions = { method: 'GET', ...baseOptions, ...options}; + const localVarHeaderParameter = {} as any; + const localVarQueryParameter = {} as any; + + // authentication apiKey required + await setApiKeyToObject(localVarHeaderParameter, "api-key", configuration) + + // authentication mockType required + await setApiKeyToObject(localVarHeaderParameter, "Prefer", configuration) + + // authentication userId required + await setApiKeyToObject(localVarHeaderParameter, "user-uid", configuration) + + if (orgId !== undefined) { + localVarQueryParameter['orgId'] = orgId; + } + + if (pageIndex !== undefined) { + localVarQueryParameter['pageIndex'] = pageIndex; + } + + if (pageSize !== undefined) { + localVarQueryParameter['pageSize'] = pageSize; + } + + + + setSearchParams(localVarUrlObj, localVarQueryParameter); + let headersFromBaseOptions = baseOptions && baseOptions.headers ? baseOptions.headers : {}; + localVarRequestOptions.headers = {...localVarHeaderParameter, ...headersFromBaseOptions, ...options.headers}; + + return { + url: toPathString(localVarUrlObj), + options: localVarRequestOptions, + }; + }, + /** + * Get VA system FISMA inventory summary dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + getVaSystemFismaInvetorySummary: async (orgId: number, pageIndex?: number, pageSize?: number, options: AxiosRequestConfig = {}): Promise => { + // verify required parameter 'orgId' is not null or undefined + assertParamExists('getVaSystemFismaInvetorySummary', 'orgId', orgId) + const localVarPath = `/api/dashboards/va-system-fisma-inventory-summary`; + // use dummy base URL string because the URL constructor only accepts absolute URLs. + const localVarUrlObj = new URL(localVarPath, DUMMY_BASE_URL); + let baseOptions; + if (configuration) { + baseOptions = configuration.baseOptions; + } + + const localVarRequestOptions = { method: 'GET', ...baseOptions, ...options}; + const localVarHeaderParameter = {} as any; + const localVarQueryParameter = {} as any; + + // authentication apiKey required + await setApiKeyToObject(localVarHeaderParameter, "api-key", configuration) + + // authentication mockType required + await setApiKeyToObject(localVarHeaderParameter, "Prefer", configuration) + + // authentication userId required + await setApiKeyToObject(localVarHeaderParameter, "user-uid", configuration) + + if (orgId !== undefined) { + localVarQueryParameter['orgId'] = orgId; + } + + if (pageIndex !== undefined) { + localVarQueryParameter['pageIndex'] = pageIndex; + } + + if (pageSize !== undefined) { + localVarQueryParameter['pageSize'] = pageSize; + } + + + + setSearchParams(localVarUrlObj, localVarQueryParameter); + let headersFromBaseOptions = baseOptions && baseOptions.headers ? baseOptions.headers : {}; + localVarRequestOptions.headers = {...localVarHeaderParameter, ...headersFromBaseOptions, ...options.headers}; + + return { + url: toPathString(localVarUrlObj), + options: localVarRequestOptions, + }; + }, + /** + * Get VA system P.L. 109 reporting summary dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + getVaSystemPl109ReportingSummary: async (orgId: number, pageIndex?: number, pageSize?: number, options: AxiosRequestConfig = {}): Promise => { + // verify required parameter 'orgId' is not null or undefined + assertParamExists('getVaSystemPl109ReportingSummary', 'orgId', orgId) + const localVarPath = `/api/dashboards/va-system-pl-109-reporting-summary`; + // use dummy base URL string because the URL constructor only accepts absolute URLs. + const localVarUrlObj = new URL(localVarPath, DUMMY_BASE_URL); + let baseOptions; + if (configuration) { + baseOptions = configuration.baseOptions; + } + + const localVarRequestOptions = { method: 'GET', ...baseOptions, ...options}; + const localVarHeaderParameter = {} as any; + const localVarQueryParameter = {} as any; + + // authentication apiKey required + await setApiKeyToObject(localVarHeaderParameter, "api-key", configuration) + + // authentication mockType required + await setApiKeyToObject(localVarHeaderParameter, "Prefer", configuration) + + // authentication userId required + await setApiKeyToObject(localVarHeaderParameter, "user-uid", configuration) + + if (orgId !== undefined) { + localVarQueryParameter['orgId'] = orgId; + } + + if (pageIndex !== undefined) { + localVarQueryParameter['pageIndex'] = pageIndex; + } + + if (pageSize !== undefined) { + localVarQueryParameter['pageSize'] = pageSize; + } + + + + setSearchParams(localVarUrlObj, localVarQueryParameter); + let headersFromBaseOptions = baseOptions && baseOptions.headers ? baseOptions.headers : {}; + localVarRequestOptions.headers = {...localVarHeaderParameter, ...headersFromBaseOptions, ...options.headers}; + + return { + url: toPathString(localVarUrlObj), + options: localVarRequestOptions, + }; + }, + } +}; + +/** + * DashboardsApi - functional programming interface + * @export + */ +export const DashboardsApiFp = function(configuration?: Configuration) { + const localVarAxiosParamCreator = DashboardsApiAxiosParamCreator(configuration) + return { + /** + * Get systems assessement procdures details dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + async getSystemAssessmentProceduresDetails(orgId: number, pageIndex?: number, pageSize?: number, options?: AxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise> { + const localVarAxiosArgs = await localVarAxiosParamCreator.getSystemAssessmentProceduresDetails(orgId, pageIndex, pageSize, options); + return createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration); + }, + /** + * Get system associations details dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + async getSystemAssociationsDetails(orgId: number, pageIndex?: number, pageSize?: number, options?: AxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise> { + const localVarAxiosArgs = await localVarAxiosParamCreator.getSystemAssociationsDetails(orgId, pageIndex, pageSize, options); + return createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration); + }, + /** + * Get systems control compliance summary dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + async getSystemControlComplianceSummary(orgId: number, pageIndex?: number, pageSize?: number, options?: AxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise> { + const localVarAxiosArgs = await localVarAxiosParamCreator.getSystemControlComplianceSummary(orgId, pageIndex, pageSize, options); + return createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration); + }, + /** + * Get system hardware details dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + async getSystemHardwareDetails(orgId: number, pageIndex?: number, pageSize?: number, options?: AxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise> { + const localVarAxiosArgs = await localVarAxiosParamCreator.getSystemHardwareDetails(orgId, pageIndex, pageSize, options); + return createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration); + }, + /** + * Get system hardware summary dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + async getSystemHardwareSummary(orgId: number, pageIndex?: number, pageSize?: number, options?: AxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise> { + const localVarAxiosArgs = await localVarAxiosParamCreator.getSystemHardwareSummary(orgId, pageIndex, pageSize, options); + return createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration); + }, + /** + * Get system POA&Ms details dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + async getSystemPoamDetails(orgId: number, pageIndex?: number, pageSize?: number, options?: AxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise> { + const localVarAxiosArgs = await localVarAxiosParamCreator.getSystemPoamDetails(orgId, pageIndex, pageSize, options); + return createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration); + }, + /** + * Get systems POA&Ms summary dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + async getSystemPoamSummary(orgId: number, pageIndex?: number, pageSize?: number, options?: AxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise> { + const localVarAxiosArgs = await localVarAxiosParamCreator.getSystemPoamSummary(orgId, pageIndex, pageSize, options); + return createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration); + }, + /** + * Get user system privacy summary dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + async getSystemPrivacySummary(orgId: number, pageIndex?: number, pageSize?: number, options?: AxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise> { + const localVarAxiosArgs = await localVarAxiosParamCreator.getSystemPrivacySummary(orgId, pageIndex, pageSize, options); + return createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration); + }, + /** + * Get systems security control details dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + async getSystemSecurityControlDetails(orgId: number, pageIndex?: number, pageSize?: number, options?: AxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise> { + const localVarAxiosArgs = await localVarAxiosParamCreator.getSystemSecurityControlDetails(orgId, pageIndex, pageSize, options); + return createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration); + }, + /** + * Get systems status detail dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + async getSystemStatusDetails(orgId: number, pageIndex?: number, pageSize?: number, options?: AxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise> { + const localVarAxiosArgs = await localVarAxiosParamCreator.getSystemStatusDetails(orgId, pageIndex, pageSize, options); + return createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration); + }, + /** + * Get user system assignments details dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + async getUserSystemAssignmentsDetails(orgId: number, pageIndex?: number, pageSize?: number, options?: AxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise> { + const localVarAxiosArgs = await localVarAxiosParamCreator.getUserSystemAssignmentsDetails(orgId, pageIndex, pageSize, options); + return createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration); + }, + /** + * Get VA OMB-FISMA SAOP summary dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + async getVaOmbFsmaSaopSummary(orgId: number, pageIndex?: number, pageSize?: number, options?: AxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise> { + const localVarAxiosArgs = await localVarAxiosParamCreator.getVaOmbFsmaSaopSummary(orgId, pageIndex, pageSize, options); + return createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration); + }, + /** + * Get VA system A2.0 summary dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + async getVaSystemA2Summary(orgId: number, pageIndex?: number, pageSize?: number, options?: AxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise> { + const localVarAxiosArgs = await localVarAxiosParamCreator.getVaSystemA2Summary(orgId, pageIndex, pageSize, options); + return createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration); + }, + /** + * Get VA system A&A summary dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + async getVaSystemAaSummary(orgId: number, pageIndex?: number, pageSize?: number, options?: AxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise> { + const localVarAxiosArgs = await localVarAxiosParamCreator.getVaSystemAaSummary(orgId, pageIndex, pageSize, options); + return createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration); + }, + /** + * Get VA system FISMA inventory summary dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + async getVaSystemFismaInvetorySummary(orgId: number, pageIndex?: number, pageSize?: number, options?: AxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise> { + const localVarAxiosArgs = await localVarAxiosParamCreator.getVaSystemFismaInvetorySummary(orgId, pageIndex, pageSize, options); + return createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration); + }, + /** + * Get VA system P.L. 109 reporting summary dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + async getVaSystemPl109ReportingSummary(orgId: number, pageIndex?: number, pageSize?: number, options?: AxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise> { + const localVarAxiosArgs = await localVarAxiosParamCreator.getVaSystemPl109ReportingSummary(orgId, pageIndex, pageSize, options); + return createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration); + }, + } +}; + +/** + * DashboardsApi - factory interface + * @export + */ +export const DashboardsApiFactory = function (configuration?: Configuration, basePath?: string, axios?: AxiosInstance) { + const localVarFp = DashboardsApiFp(configuration) + return { + /** + * Get systems assessement procdures details dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + getSystemAssessmentProceduresDetails(orgId: number, pageIndex?: number, pageSize?: number, options?: any): AxiosPromise { + return localVarFp.getSystemAssessmentProceduresDetails(orgId, pageIndex, pageSize, options).then((request) => request(axios, basePath)); + }, + /** + * Get system associations details dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + getSystemAssociationsDetails(orgId: number, pageIndex?: number, pageSize?: number, options?: any): AxiosPromise { + return localVarFp.getSystemAssociationsDetails(orgId, pageIndex, pageSize, options).then((request) => request(axios, basePath)); + }, + /** + * Get systems control compliance summary dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + getSystemControlComplianceSummary(orgId: number, pageIndex?: number, pageSize?: number, options?: any): AxiosPromise { + return localVarFp.getSystemControlComplianceSummary(orgId, pageIndex, pageSize, options).then((request) => request(axios, basePath)); + }, + /** + * Get system hardware details dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + getSystemHardwareDetails(orgId: number, pageIndex?: number, pageSize?: number, options?: any): AxiosPromise { + return localVarFp.getSystemHardwareDetails(orgId, pageIndex, pageSize, options).then((request) => request(axios, basePath)); + }, + /** + * Get system hardware summary dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + getSystemHardwareSummary(orgId: number, pageIndex?: number, pageSize?: number, options?: any): AxiosPromise { + return localVarFp.getSystemHardwareSummary(orgId, pageIndex, pageSize, options).then((request) => request(axios, basePath)); + }, + /** + * Get system POA&Ms details dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + getSystemPoamDetails(orgId: number, pageIndex?: number, pageSize?: number, options?: any): AxiosPromise { + return localVarFp.getSystemPoamDetails(orgId, pageIndex, pageSize, options).then((request) => request(axios, basePath)); + }, + /** + * Get systems POA&Ms summary dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + getSystemPoamSummary(orgId: number, pageIndex?: number, pageSize?: number, options?: any): AxiosPromise { + return localVarFp.getSystemPoamSummary(orgId, pageIndex, pageSize, options).then((request) => request(axios, basePath)); + }, + /** + * Get user system privacy summary dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + getSystemPrivacySummary(orgId: number, pageIndex?: number, pageSize?: number, options?: any): AxiosPromise { + return localVarFp.getSystemPrivacySummary(orgId, pageIndex, pageSize, options).then((request) => request(axios, basePath)); + }, + /** + * Get systems security control details dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + getSystemSecurityControlDetails(orgId: number, pageIndex?: number, pageSize?: number, options?: any): AxiosPromise { + return localVarFp.getSystemSecurityControlDetails(orgId, pageIndex, pageSize, options).then((request) => request(axios, basePath)); + }, + /** + * Get systems status detail dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + getSystemStatusDetails(orgId: number, pageIndex?: number, pageSize?: number, options?: any): AxiosPromise { + return localVarFp.getSystemStatusDetails(orgId, pageIndex, pageSize, options).then((request) => request(axios, basePath)); + }, + /** + * Get user system assignments details dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + getUserSystemAssignmentsDetails(orgId: number, pageIndex?: number, pageSize?: number, options?: any): AxiosPromise { + return localVarFp.getUserSystemAssignmentsDetails(orgId, pageIndex, pageSize, options).then((request) => request(axios, basePath)); + }, + /** + * Get VA OMB-FISMA SAOP summary dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + getVaOmbFsmaSaopSummary(orgId: number, pageIndex?: number, pageSize?: number, options?: any): AxiosPromise { + return localVarFp.getVaOmbFsmaSaopSummary(orgId, pageIndex, pageSize, options).then((request) => request(axios, basePath)); + }, + /** + * Get VA system A2.0 summary dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + getVaSystemA2Summary(orgId: number, pageIndex?: number, pageSize?: number, options?: any): AxiosPromise { + return localVarFp.getVaSystemA2Summary(orgId, pageIndex, pageSize, options).then((request) => request(axios, basePath)); + }, + /** + * Get VA system A&A summary dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + getVaSystemAaSummary(orgId: number, pageIndex?: number, pageSize?: number, options?: any): AxiosPromise { + return localVarFp.getVaSystemAaSummary(orgId, pageIndex, pageSize, options).then((request) => request(axios, basePath)); + }, + /** + * Get VA system FISMA inventory summary dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + getVaSystemFismaInvetorySummary(orgId: number, pageIndex?: number, pageSize?: number, options?: any): AxiosPromise { + return localVarFp.getVaSystemFismaInvetorySummary(orgId, pageIndex, pageSize, options).then((request) => request(axios, basePath)); + }, + /** + * Get VA system P.L. 109 reporting summary dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + */ + getVaSystemPl109ReportingSummary(orgId: number, pageIndex?: number, pageSize?: number, options?: any): AxiosPromise { + return localVarFp.getVaSystemPl109ReportingSummary(orgId, pageIndex, pageSize, options).then((request) => request(axios, basePath)); + }, + }; +}; + +/** + * DashboardsApi - object-oriented interface + * @export + * @class DashboardsApi + * @extends {BaseAPI} + */ +export class DashboardsApi extends BaseAPI { + /** + * Get systems assessement procdures details dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + * @memberof DashboardsApi + */ + public getSystemAssessmentProceduresDetails(orgId: number, pageIndex?: number, pageSize?: number, options?: AxiosRequestConfig) { + return DashboardsApiFp(this.configuration).getSystemAssessmentProceduresDetails(orgId, pageIndex, pageSize, options).then((request) => request(this.axios, this.basePath)); + } + + /** + * Get system associations details dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + * @memberof DashboardsApi + */ + public getSystemAssociationsDetails(orgId: number, pageIndex?: number, pageSize?: number, options?: AxiosRequestConfig) { + return DashboardsApiFp(this.configuration).getSystemAssociationsDetails(orgId, pageIndex, pageSize, options).then((request) => request(this.axios, this.basePath)); + } + + /** + * Get systems control compliance summary dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + * @memberof DashboardsApi + */ + public getSystemControlComplianceSummary(orgId: number, pageIndex?: number, pageSize?: number, options?: AxiosRequestConfig) { + return DashboardsApiFp(this.configuration).getSystemControlComplianceSummary(orgId, pageIndex, pageSize, options).then((request) => request(this.axios, this.basePath)); + } + + /** + * Get system hardware details dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + * @memberof DashboardsApi + */ + public getSystemHardwareDetails(orgId: number, pageIndex?: number, pageSize?: number, options?: AxiosRequestConfig) { + return DashboardsApiFp(this.configuration).getSystemHardwareDetails(orgId, pageIndex, pageSize, options).then((request) => request(this.axios, this.basePath)); + } + + /** + * Get system hardware summary dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + * @memberof DashboardsApi + */ + public getSystemHardwareSummary(orgId: number, pageIndex?: number, pageSize?: number, options?: AxiosRequestConfig) { + return DashboardsApiFp(this.configuration).getSystemHardwareSummary(orgId, pageIndex, pageSize, options).then((request) => request(this.axios, this.basePath)); + } + + /** + * Get system POA&Ms details dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + * @memberof DashboardsApi + */ + public getSystemPoamDetails(orgId: number, pageIndex?: number, pageSize?: number, options?: AxiosRequestConfig) { + return DashboardsApiFp(this.configuration).getSystemPoamDetails(orgId, pageIndex, pageSize, options).then((request) => request(this.axios, this.basePath)); + } + + /** + * Get systems POA&Ms summary dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + * @memberof DashboardsApi + */ + public getSystemPoamSummary(orgId: number, pageIndex?: number, pageSize?: number, options?: AxiosRequestConfig) { + return DashboardsApiFp(this.configuration).getSystemPoamSummary(orgId, pageIndex, pageSize, options).then((request) => request(this.axios, this.basePath)); + } + + /** + * Get user system privacy summary dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + * @memberof DashboardsApi + */ + public getSystemPrivacySummary(orgId: number, pageIndex?: number, pageSize?: number, options?: AxiosRequestConfig) { + return DashboardsApiFp(this.configuration).getSystemPrivacySummary(orgId, pageIndex, pageSize, options).then((request) => request(this.axios, this.basePath)); + } + + /** + * Get systems security control details dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + * @memberof DashboardsApi + */ + public getSystemSecurityControlDetails(orgId: number, pageIndex?: number, pageSize?: number, options?: AxiosRequestConfig) { + return DashboardsApiFp(this.configuration).getSystemSecurityControlDetails(orgId, pageIndex, pageSize, options).then((request) => request(this.axios, this.basePath)); + } + + /** + * Get systems status detail dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + * @memberof DashboardsApi + */ + public getSystemStatusDetails(orgId: number, pageIndex?: number, pageSize?: number, options?: AxiosRequestConfig) { + return DashboardsApiFp(this.configuration).getSystemStatusDetails(orgId, pageIndex, pageSize, options).then((request) => request(this.axios, this.basePath)); + } + + /** + * Get user system assignments details dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + * @memberof DashboardsApi + */ + public getUserSystemAssignmentsDetails(orgId: number, pageIndex?: number, pageSize?: number, options?: AxiosRequestConfig) { + return DashboardsApiFp(this.configuration).getUserSystemAssignmentsDetails(orgId, pageIndex, pageSize, options).then((request) => request(this.axios, this.basePath)); + } + + /** + * Get VA OMB-FISMA SAOP summary dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + * @memberof DashboardsApi + */ + public getVaOmbFsmaSaopSummary(orgId: number, pageIndex?: number, pageSize?: number, options?: AxiosRequestConfig) { + return DashboardsApiFp(this.configuration).getVaOmbFsmaSaopSummary(orgId, pageIndex, pageSize, options).then((request) => request(this.axios, this.basePath)); + } + + /** + * Get VA system A2.0 summary dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + * @memberof DashboardsApi + */ + public getVaSystemA2Summary(orgId: number, pageIndex?: number, pageSize?: number, options?: AxiosRequestConfig) { + return DashboardsApiFp(this.configuration).getVaSystemA2Summary(orgId, pageIndex, pageSize, options).then((request) => request(this.axios, this.basePath)); + } + + /** + * Get VA system A&A summary dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + * @memberof DashboardsApi + */ + public getVaSystemAaSummary(orgId: number, pageIndex?: number, pageSize?: number, options?: AxiosRequestConfig) { + return DashboardsApiFp(this.configuration).getVaSystemAaSummary(orgId, pageIndex, pageSize, options).then((request) => request(this.axios, this.basePath)); + } + + /** + * Get VA system FISMA inventory summary dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + * @memberof DashboardsApi + */ + public getVaSystemFismaInvetorySummary(orgId: number, pageIndex?: number, pageSize?: number, options?: AxiosRequestConfig) { + return DashboardsApiFp(this.configuration).getVaSystemFismaInvetorySummary(orgId, pageIndex, pageSize, options).then((request) => request(this.axios, this.basePath)); + } + + /** + * Get VA system P.L. 109 reporting summary dashboard information. + * @summary Get dashboard information + * @param {number} orgId **Organization Id**: The unique organization identifier. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. + * @param {number} [pageSize] **Page Size**: If no value is specified, the default returns 20000 per page. + * @param {*} [options] Override http request option. + * @throws {RequiredError} + * @memberof DashboardsApi + */ + public getVaSystemPl109ReportingSummary(orgId: number, pageIndex?: number, pageSize?: number, options?: AxiosRequestConfig) { + return DashboardsApiFp(this.configuration).getVaSystemPl109ReportingSummary(orgId, pageIndex, pageSize, options).then((request) => request(this.axios, this.basePath)); + } +} + + /** * MilestonesApi - axios parameter creator * @export @@ -7315,7 +8873,7 @@ export const WorkflowInstancesApiAxiosParamCreator = function (configuration?: C * View detailed information on all active and historical workflows filtered by provided parameters. * @summary Get workflow instances in a site * @param {boolean} [includeComments] **Include Comments**: If no value is specified, the default returns true to not include transition comments. Note: Corresponds to the Comments textbox that is required at most workflow transitions. Does not include other text input fields such as Terms / Conditions for Authorization. - * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns true to not include transition comments. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. **Note:** Pages contain 1000 workflow instances. * @param {string} [sinceDate] **Date**: Filter on authorization/assessment date (Unix date format). Note: Filters off the lastEditedDate field. Note: The authorization/assessment decisions on completed workflows can be edited for up to 30 days after the initial decision is made. * @param {'active' | 'inactive' | 'all'} [status] **Status**: Filter by status. If no value is specified, the default returns all to include both active and inactive workflows. Note: Any workflows at a current stage of Complete or Cancelled are inactive. Ongoing workflows currently at other stages are active. * @param {*} [options] Override http request option. @@ -7427,7 +8985,7 @@ export const WorkflowInstancesApiFp = function(configuration?: Configuration) { * View detailed information on all active and historical workflows filtered by provided parameters. * @summary Get workflow instances in a site * @param {boolean} [includeComments] **Include Comments**: If no value is specified, the default returns true to not include transition comments. Note: Corresponds to the Comments textbox that is required at most workflow transitions. Does not include other text input fields such as Terms / Conditions for Authorization. - * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns true to not include transition comments. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. **Note:** Pages contain 1000 workflow instances. * @param {string} [sinceDate] **Date**: Filter on authorization/assessment date (Unix date format). Note: Filters off the lastEditedDate field. Note: The authorization/assessment decisions on completed workflows can be edited for up to 30 days after the initial decision is made. * @param {'active' | 'inactive' | 'all'} [status] **Status**: Filter by status. If no value is specified, the default returns all to include both active and inactive workflows. Note: Any workflows at a current stage of Complete or Cancelled are inactive. Ongoing workflows currently at other stages are active. * @param {*} [options] Override http request option. @@ -7462,7 +9020,7 @@ export const WorkflowInstancesApiFactory = function (configuration?: Configurati * View detailed information on all active and historical workflows filtered by provided parameters. * @summary Get workflow instances in a site * @param {boolean} [includeComments] **Include Comments**: If no value is specified, the default returns true to not include transition comments. Note: Corresponds to the Comments textbox that is required at most workflow transitions. Does not include other text input fields such as Terms / Conditions for Authorization. - * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns true to not include transition comments. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. **Note:** Pages contain 1000 workflow instances. * @param {string} [sinceDate] **Date**: Filter on authorization/assessment date (Unix date format). Note: Filters off the lastEditedDate field. Note: The authorization/assessment decisions on completed workflows can be edited for up to 30 days after the initial decision is made. * @param {'active' | 'inactive' | 'all'} [status] **Status**: Filter by status. If no value is specified, the default returns all to include both active and inactive workflows. Note: Any workflows at a current stage of Complete or Cancelled are inactive. Ongoing workflows currently at other stages are active. * @param {*} [options] Override http request option. @@ -7495,7 +9053,7 @@ export class WorkflowInstancesApi extends BaseAPI { * View detailed information on all active and historical workflows filtered by provided parameters. * @summary Get workflow instances in a site * @param {boolean} [includeComments] **Include Comments**: If no value is specified, the default returns true to not include transition comments. Note: Corresponds to the Comments textbox that is required at most workflow transitions. Does not include other text input fields such as Terms / Conditions for Authorization. - * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns true to not include transition comments. + * @param {number} [pageIndex] **Page Index**: If no value is specified, the default returns results from the first page with an index of 0. **Note:** Pages contain 1000 workflow instances. * @param {string} [sinceDate] **Date**: Filter on authorization/assessment date (Unix date format). Note: Filters off the lastEditedDate field. Note: The authorization/assessment decisions on completed workflows can be edited for up to 30 days after the initial decision is made. * @param {'active' | 'inactive' | 'all'} [status] **Status**: Filter by status. If no value is specified, the default returns all to include both active and inactive workflows. Note: Any workflows at a current stage of Complete or Cancelled are inactive. Ongoing workflows currently at other stages are active. * @param {*} [options] Override http request option. diff --git a/src/typescript_client/base.ts b/src/typescript_client/base.ts index 7771c20b..a0cb8d0a 100644 --- a/src/typescript_client/base.ts +++ b/src/typescript_client/base.ts @@ -4,7 +4,7 @@ * Enterprise Mission Assurance Support Service (eMASS) * 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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: * - * The version of the OpenAPI document: v3.3 + * The version of the OpenAPI document: v3.4 * Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/src/typescript_client/common.ts b/src/typescript_client/common.ts index 9a83d1a7..1af99c52 100644 --- a/src/typescript_client/common.ts +++ b/src/typescript_client/common.ts @@ -4,7 +4,7 @@ * Enterprise Mission Assurance Support Service (eMASS) * 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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: * - * The version of the OpenAPI document: v3.3 + * The version of the OpenAPI document: v3.4 * Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). @@ -83,24 +83,34 @@ export const setOAuthToObject = async function (object: any, name: string, scope } } +function setFlattenedQueryParams(urlSearchParams: URLSearchParams, parameter: any, key: string = ""): void { + if (typeof parameter === "object") { + if (Array.isArray(parameter)) { + (parameter as any[]).forEach(item => setFlattenedQueryParams(urlSearchParams, item, key)); + } + else { + Object.keys(parameter).forEach(currentKey => + setFlattenedQueryParams(urlSearchParams, parameter[currentKey], `${key}${key !== '' ? '.' : ''}${currentKey}`) + ); + } + } + else { + if (urlSearchParams.has(key)) { + urlSearchParams.append(key, parameter); + } + else { + urlSearchParams.set(key, parameter); + } + } +} + /** * * @export */ export const setSearchParams = function (url: URL, ...objects: any[]) { const searchParams = new URLSearchParams(url.search); - for (const object of objects) { - for (const key in object) { - if (Array.isArray(object[key])) { - searchParams.delete(key); - for (const item of object[key]) { - searchParams.append(key, item); - } - } else { - searchParams.set(key, object[key]); - } - } - } + setFlattenedQueryParams(searchParams, objects); url.search = searchParams.toString(); } diff --git a/src/typescript_client/configuration.ts b/src/typescript_client/configuration.ts index 846f0fbf..c1ce25a0 100644 --- a/src/typescript_client/configuration.ts +++ b/src/typescript_client/configuration.ts @@ -4,7 +4,7 @@ * Enterprise Mission Assurance Support Service (eMASS) * 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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: * - * The version of the OpenAPI document: v3.3 + * The version of the OpenAPI document: v3.4 * Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/src/typescript_client/index.ts b/src/typescript_client/index.ts index 4c01d78d..e6cf2ebb 100644 --- a/src/typescript_client/index.ts +++ b/src/typescript_client/index.ts @@ -4,7 +4,7 @@ * Enterprise Mission Assurance Support Service (eMASS) * 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. Register External Application (that use the eMASS API)
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.

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.

Available Request Headers
key Example Value Description
`api-key` api-key-provided-by-emass This API key must be provided in the request header for all endpoint calls
`user-uid` USER.UID.KEY This User unique identifier key must be provided in the request header for all PUT, POST, and DELETE endpoint calls
Note: For DoD users this is the DoD ID Number (EIDIPI) on their DoD CAC

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: * - * The version of the OpenAPI document: v3.3 + * The version of the OpenAPI document: v3.4 * Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/src/typescript_client/package.json b/src/typescript_client/package.json index a1c5c4df..42d3d26a 100644 --- a/src/typescript_client/package.json +++ b/src/typescript_client/package.json @@ -1,11 +1,11 @@ { "name": "@mitre/emass_client", - "version": "1.0.6", + "version": "3.4.0", + "description": "OpenAPI client for @mitre/emass_client", "repository": { "type": "git", "url": "https://github.com/mitre/emass_client.git" - }, - "description": "OpenAPI client for @mitre/emass_client", + }, "author": "OpenAPI-Generator Contributors", "keywords": [ "axios",