From 2fb375f6396b9e875e2e6b8eb8cdfc0c156c8756 Mon Sep 17 00:00:00 2001 From: CI Pipeline Date: Tue, 10 Oct 2023 14:36:06 +0000 Subject: [PATCH] CI Build Client Artifacts (eMASS Clients) --- src/python_client/README.md | 4 +- src/python_client/emass_client/__init__.py | 6 +- .../emass_client/api/artifacts_api.py | 76 +++++++++++++--- .../emass_client/api/artifacts_export_api.py | 20 ++++- src/python_client/emass_client/api/cac_api.py | 32 +++++-- .../api/cloud_resource_results_api.py | 32 +++++-- .../emass_client/api/cmmc_assessments_api.py | 16 +++- .../api/container_scan_results_api.py | 32 +++++-- .../emass_client/api/controls_api.py | 32 +++++-- .../enterprise_artifacts_dashboards_api.py | 40 +++++++-- .../api/enterprise_poam_dashboards_api.py | 40 +++++++-- ...rprise_security_controls_dashboards_api.py | 58 +++++++++++-- ...based_hardware_resources_dashboards_api.py | 40 +++++++-- ...based_software_resources_dashboards_api.py | 58 +++++++++++-- ...erprise_terms_conditions_dashboards_api.py | 40 +++++++-- ...enterprise_vulnerability_dashboards_api.py | 58 +++++++++++-- .../fisma_inventory_summary_dashboards_api.py | 40 +++++++-- .../api/hardware_baseline_dashboards_api.py | 40 +++++++-- .../emass_client/api/milestones_api.py | 86 ++++++++++++++++--- src/python_client/emass_client/api/pac_api.py | 30 +++++-- .../emass_client/api/poam_api.py | 84 +++++++++++++++--- .../api/ports_and_protocols_dashboards_api.py | 40 +++++++-- .../api/privacy_compliance_dashboards_api.py | 40 +++++++-- .../emass_client/api/registration_api.py | 14 ++- .../api/software_baseline_dashboards_api.py | 40 +++++++-- .../emass_client/api/static_code_scans_api.py | 18 +++- .../api/system_a20_summary_dashboard_api.py | 22 ++++- .../api/system_aa_summary_dashboard_api.py | 22 ++++- .../api/system_associations_dashboard_api.py | 22 ++++- ...conmon_integration_status_dashboard_api.py | 22 ++++- ...m_pl109_reporting_summary_dashboard_api.py | 22 ++++- .../emass_client/api/system_roles_api.py | 30 +++++-- .../api/system_status_dashboard_api.py | 22 ++++- .../emass_client/api/systems_api.py | 46 ++++++++-- .../emass_client/api/test_api.py | 14 ++- .../emass_client/api/test_results_api.py | 38 ++++++-- .../api/threat_risks_dashboards_api.py | 58 +++++++++++-- .../emass_client/api/users_dashboard_api.py | 22 ++++- .../api/workflow_definitions_api.py | 18 +++- .../api/workflow_instances_api.py | 36 ++++++-- src/python_client/emass_client/api_client.py | 6 +- .../emass_client/configuration.py | 6 +- src/python_client/emass_client/exceptions.py | 4 +- .../emass_client/models/__init__.py | 4 +- .../emass_client/models/artifacts_get.py | 4 +- .../artifacts_request_delete_body_inner.py | 4 +- .../models/artifacts_response_del.py | 4 +- .../artifacts_response_del_data_inner.py | 4 +- .../models/artifacts_response_get.py | 4 +- .../models/artifacts_response_put_post.py | 4 +- .../artifacts_response_put_post_data_inner.py | 4 +- .../emass_client/models/cac_get.py | 4 +- .../emass_client/models/cac_response_get.py | 4 +- .../emass_client/models/cac_response_post.py | 4 +- .../models/cac_response_post_data_inner.py | 4 +- .../models/cloud_resources_delete.py | 4 +- .../cloud_resources_delete_body_inner.py | 4 +- .../models/cloud_resources_post_delete.py | 4 +- .../models/cloud_resources_response_post.py | 4 +- .../emass_client/models/cmmc_get.py | 4 +- .../emass_client/models/cmmc_response_get.py | 4 +- .../emass_client/models/connectivity_ccsd.py | 4 +- .../container_resources_delete_body_inner.py | 4 +- .../containers_resources_post_delete.py | 4 +- .../models/containers_response_delete.py | 4 +- .../models/containers_response_post.py | 4 +- .../emass_client/models/controls_get.py | 4 +- .../emass_client/models/controls_put.py | 4 +- .../models/controls_response_get.py | 4 +- .../models/controls_response_put.py | 4 +- .../models/dashboard_mock_response.py | 4 +- .../dashboard_mock_response_pagination.py | 4 +- .../models/definition_transitions.py | 4 +- .../models/instances_transitions.py | 4 +- .../models/milestone_response_delete.py | 4 +- .../models/milestone_response_get.py | 4 +- .../milestone_response_get_milestone.py | 4 +- .../models/milestone_response_post.py | 4 +- .../models/milestone_response_put.py | 4 +- .../emass_client/models/milestones_get.py | 4 +- .../models/milestones_put_post_delete.py | 4 +- .../milestones_request_delete_body_inner.py | 4 +- .../models/milestones_required_post.py | 4 +- .../models/milestones_required_put.py | 4 +- .../emass_client/models/mock_object.py | 4 +- .../emass_client/models/pac_get.py | 4 +- .../emass_client/models/pac_post.py | 4 +- .../emass_client/models/pac_response_get.py | 4 +- .../emass_client/models/pac_response_post.py | 4 +- .../emass_client/models/poam_get.py | 4 +- .../emass_client/models/poam_post_put_del.py | 4 +- .../models/poam_request_delete_body_inner.py | 4 +- .../models/poam_response_delete.py | 4 +- .../models/poam_response_get_poams.py | 4 +- .../models/poam_response_get_systems.py | 4 +- .../emass_client/models/poam_response_post.py | 4 +- .../emass_client/models/poam_response_put.py | 4 +- .../emass_client/models/register.py | 4 +- .../emass_client/models/register_data.py | 4 +- .../models/register_user_request_post_body.py | 4 +- .../emass_client/models/response200.py | 4 +- .../emass_client/models/response201.py | 4 +- .../emass_client/models/response201_meta.py | 4 +- .../emass_client/models/response400.py | 4 +- .../emass_client/models/response400_meta.py | 4 +- .../emass_client/models/response401.py | 4 +- .../emass_client/models/response401_meta.py | 4 +- .../emass_client/models/response403.py | 4 +- .../emass_client/models/response403_meta.py | 4 +- .../emass_client/models/response404.py | 4 +- .../emass_client/models/response405.py | 4 +- .../emass_client/models/response405_meta.py | 4 +- .../emass_client/models/response411.py | 4 +- .../emass_client/models/response411_meta.py | 4 +- .../emass_client/models/response490.py | 4 +- .../emass_client/models/response490_meta.py | 4 +- .../emass_client/models/response500.py | 4 +- .../emass_client/models/response500_meta.py | 4 +- .../emass_client/models/role_category.py | 4 +- .../emass_client/models/roles.py | 4 +- src/python_client/emass_client/models/ssps.py | 4 +- .../emass_client/models/stage.py | 4 +- .../models/static_code_application_post.py | 4 +- .../emass_client/models/static_code_post.py | 4 +- .../models/static_code_request_post_body.py | 4 +- ...atic_code_request_post_body_application.py | 4 +- .../models/static_code_response_post.py | 4 +- .../models/success200_response.py | 4 +- .../models/success200_response_data_inner.py | 4 +- .../emass_client/models/system_response.py | 4 +- .../models/system_roles_category_response.py | 4 +- .../models/system_roles_response.py | 4 +- .../system_roles_response_data_inner.py | 4 +- .../emass_client/models/systems.py | 4 +- .../emass_client/models/systems_response.py | 4 +- src/python_client/emass_client/models/test.py | 4 +- .../emass_client/models/test_data.py | 4 +- .../emass_client/models/test_results_get.py | 4 +- .../emass_client/models/test_results_post.py | 4 +- .../models/test_results_response_get.py | 4 +- .../models/test_results_response_post.py | 4 +- .../emass_client/models/users.py | 4 +- .../models/workflow_definition_get.py | 4 +- .../workflow_definition_response_get.py | 4 +- .../models/workflow_instance_get.py | 4 +- .../models/workflow_instance_response_get.py | 4 +- .../models/workflow_instances_get.py | 4 +- .../models/workflow_instances_response_get.py | 4 +- ...kflow_instances_response_get_pagination.py | 4 +- src/python_client/emass_client/rest.py | 4 +- src/python_client/pyproject.toml | 2 +- src/python_client/setup.py | 6 +- src/python_client/test/test_artifacts_api.py | 4 +- .../test/test_artifacts_export_api.py | 4 +- src/python_client/test/test_artifacts_get.py | 4 +- ...est_artifacts_request_delete_body_inner.py | 4 +- .../test/test_artifacts_response_del.py | 4 +- .../test_artifacts_response_del_data_inner.py | 4 +- .../test/test_artifacts_response_get.py | 4 +- .../test/test_artifacts_response_put_post.py | 4 +- ..._artifacts_response_put_post_data_inner.py | 4 +- src/python_client/test/test_cac_api.py | 4 +- src/python_client/test/test_cac_get.py | 4 +- .../test/test_cac_response_get.py | 4 +- .../test/test_cac_response_post.py | 4 +- .../test/test_cac_response_post_data_inner.py | 4 +- .../test/test_cloud_resource_results_api.py | 4 +- .../test/test_cloud_resources_delete.py | 4 +- .../test_cloud_resources_delete_body_inner.py | 4 +- .../test/test_cloud_resources_post_delete.py | 4 +- .../test_cloud_resources_response_post.py | 4 +- .../test/test_cmmc_assessments_api.py | 4 +- src/python_client/test/test_cmmc_get.py | 4 +- .../test/test_cmmc_response_get.py | 4 +- .../test/test_connectivity_ccsd.py | 4 +- ...t_container_resources_delete_body_inner.py | 4 +- .../test/test_container_scan_results_api.py | 4 +- .../test_containers_resources_post_delete.py | 4 +- .../test/test_containers_response_delete.py | 4 +- .../test/test_containers_response_post.py | 4 +- src/python_client/test/test_controls_api.py | 4 +- src/python_client/test/test_controls_get.py | 4 +- src/python_client/test/test_controls_put.py | 4 +- .../test/test_controls_response_get.py | 4 +- .../test/test_controls_response_put.py | 4 +- .../test/test_dashboard_mock_response.py | 4 +- ...test_dashboard_mock_response_pagination.py | 4 +- .../test/test_definition_transitions.py | 4 +- ...est_enterprise_artifacts_dashboards_api.py | 4 +- .../test_enterprise_poam_dashboards_api.py | 4 +- ...rprise_security_controls_dashboards_api.py | 4 +- ...based_hardware_resources_dashboards_api.py | 4 +- ...based_software_resources_dashboards_api.py | 4 +- ...erprise_terms_conditions_dashboards_api.py | 4 +- ...enterprise_vulnerability_dashboards_api.py | 4 +- ..._fisma_inventory_summary_dashboards_api.py | 4 +- .../test_hardware_baseline_dashboards_api.py | 4 +- .../test/test_instances_transitions.py | 4 +- .../test/test_milestone_response_delete.py | 4 +- .../test/test_milestone_response_get.py | 4 +- .../test_milestone_response_get_milestone.py | 4 +- .../test/test_milestone_response_post.py | 4 +- .../test/test_milestone_response_put.py | 4 +- src/python_client/test/test_milestones_api.py | 4 +- src/python_client/test/test_milestones_get.py | 4 +- .../test/test_milestones_put_post_delete.py | 4 +- ...st_milestones_request_delete_body_inner.py | 4 +- .../test/test_milestones_required_post.py | 4 +- .../test/test_milestones_required_put.py | 4 +- src/python_client/test/test_mock_object.py | 4 +- src/python_client/test/test_pac_api.py | 4 +- src/python_client/test/test_pac_get.py | 4 +- src/python_client/test/test_pac_post.py | 4 +- .../test/test_pac_response_get.py | 4 +- .../test/test_pac_response_post.py | 4 +- src/python_client/test/test_poam_api.py | 4 +- src/python_client/test/test_poam_get.py | 4 +- .../test/test_poam_post_put_del.py | 4 +- .../test_poam_request_delete_body_inner.py | 4 +- .../test/test_poam_response_delete.py | 4 +- .../test/test_poam_response_get_poams.py | 4 +- .../test/test_poam_response_get_systems.py | 4 +- .../test/test_poam_response_post.py | 4 +- .../test/test_poam_response_put.py | 4 +- ...test_ports_and_protocols_dashboards_api.py | 4 +- .../test_privacy_compliance_dashboards_api.py | 4 +- src/python_client/test/test_register.py | 4 +- src/python_client/test/test_register_data.py | 4 +- .../test_register_user_request_post_body.py | 4 +- .../test/test_registration_api.py | 4 +- src/python_client/test/test_response200.py | 4 +- src/python_client/test/test_response201.py | 4 +- .../test/test_response201_meta.py | 4 +- src/python_client/test/test_response400.py | 4 +- .../test/test_response400_meta.py | 4 +- src/python_client/test/test_response401.py | 4 +- .../test/test_response401_meta.py | 4 +- src/python_client/test/test_response403.py | 4 +- .../test/test_response403_meta.py | 4 +- src/python_client/test/test_response404.py | 4 +- src/python_client/test/test_response405.py | 4 +- .../test/test_response405_meta.py | 4 +- src/python_client/test/test_response411.py | 4 +- .../test/test_response411_meta.py | 4 +- src/python_client/test/test_response490.py | 4 +- .../test/test_response490_meta.py | 4 +- src/python_client/test/test_response500.py | 4 +- .../test/test_response500_meta.py | 4 +- src/python_client/test/test_role_category.py | 4 +- src/python_client/test/test_roles.py | 4 +- .../test_software_baseline_dashboards_api.py | 4 +- src/python_client/test/test_ssps.py | 4 +- src/python_client/test/test_stage.py | 4 +- .../test/test_static_code_application_post.py | 4 +- .../test/test_static_code_post.py | 4 +- .../test_static_code_request_post_body.py | 4 +- ...atic_code_request_post_body_application.py | 4 +- .../test/test_static_code_response_post.py | 4 +- .../test/test_static_code_scans_api.py | 4 +- .../test/test_success200_response.py | 4 +- .../test_success200_response_data_inner.py | 4 +- .../test_system_a20_summary_dashboard_api.py | 4 +- .../test_system_aa_summary_dashboard_api.py | 4 +- .../test_system_associations_dashboard_api.py | 4 +- ...conmon_integration_status_dashboard_api.py | 4 +- ...m_pl109_reporting_summary_dashboard_api.py | 4 +- .../test/test_system_response.py | 4 +- .../test/test_system_roles_api.py | 4 +- .../test_system_roles_category_response.py | 4 +- .../test/test_system_roles_response.py | 4 +- .../test_system_roles_response_data_inner.py | 4 +- .../test/test_system_status_dashboard_api.py | 4 +- src/python_client/test/test_systems.py | 4 +- src/python_client/test/test_systems_api.py | 4 +- .../test/test_systems_response.py | 4 +- src/python_client/test/test_test.py | 4 +- src/python_client/test/test_test_api.py | 4 +- src/python_client/test/test_test_data.py | 4 +- .../test/test_test_results_api.py | 4 +- .../test/test_test_results_get.py | 4 +- .../test/test_test_results_post.py | 4 +- .../test/test_test_results_response_get.py | 4 +- .../test/test_test_results_response_post.py | 4 +- .../test/test_threat_risks_dashboards_api.py | 4 +- src/python_client/test/test_users.py | 4 +- .../test/test_users_dashboard_api.py | 4 +- .../test/test_workflow_definition_get.py | 4 +- .../test_workflow_definition_response_get.py | 4 +- .../test/test_workflow_definitions_api.py | 4 +- .../test/test_workflow_instance_get.py | 4 +- .../test_workflow_instance_response_get.py | 4 +- .../test/test_workflow_instances_api.py | 4 +- .../test/test_workflow_instances_get.py | 4 +- .../test_workflow_instances_response_get.py | 4 +- ...kflow_instances_response_get_pagination.py | 4 +- src/ruby_client/README.md | 2 +- src/ruby_client/emass_client.gemspec | 4 +- src/ruby_client/lib/emass_client.rb | 2 +- .../lib/emass_client/api/artifacts_api.rb | 2 +- .../emass_client/api/artifacts_export_api.rb | 2 +- .../lib/emass_client/api/cac_api.rb | 2 +- .../api/cloud_resource_results_api.rb | 2 +- .../emass_client/api/cmmc_assessments_api.rb | 2 +- .../api/container_scan_results_api.rb | 2 +- .../lib/emass_client/api/controls_api.rb | 2 +- .../enterprise_artifacts_dashboards_api.rb | 2 +- .../api/enterprise_poam_dashboards_api.rb | 2 +- ...rprise_security_controls_dashboards_api.rb | 2 +- ...based_hardware_resources_dashboards_api.rb | 2 +- ...based_software_resources_dashboards_api.rb | 2 +- ...erprise_terms_conditions_dashboards_api.rb | 2 +- ...enterprise_vulnerability_dashboards_api.rb | 2 +- .../fisma_inventory_summary_dashboards_api.rb | 2 +- .../api/hardware_baseline_dashboards_api.rb | 2 +- .../lib/emass_client/api/milestones_api.rb | 2 +- .../lib/emass_client/api/pac_api.rb | 2 +- .../lib/emass_client/api/poam_api.rb | 2 +- .../api/ports_and_protocols_dashboards_api.rb | 2 +- .../api/privacy_compliance_dashboards_api.rb | 2 +- .../lib/emass_client/api/registration_api.rb | 2 +- .../api/software_baseline_dashboards_api.rb | 2 +- .../emass_client/api/static_code_scans_api.rb | 2 +- .../api/system_a20_summary_dashboard_api.rb | 2 +- .../api/system_aa_summary_dashboard_api.rb | 2 +- .../api/system_associations_dashboard_api.rb | 2 +- ...conmon_integration_status_dashboard_api.rb | 2 +- ...m_pl109_reporting_summary_dashboard_api.rb | 2 +- .../lib/emass_client/api/system_roles_api.rb | 2 +- .../api/system_status_dashboard_api.rb | 2 +- .../lib/emass_client/api/systems_api.rb | 2 +- .../lib/emass_client/api/test_api.rb | 2 +- .../lib/emass_client/api/test_results_api.rb | 2 +- .../api/threat_risks_dashboards_api.rb | 2 +- .../emass_client/api/users_dashboard_api.rb | 2 +- .../api/workflow_definitions_api.rb | 2 +- .../api/workflow_instances_api.rb | 2 +- .../lib/emass_client/api_client.rb | 2 +- src/ruby_client/lib/emass_client/api_error.rb | 2 +- .../lib/emass_client/configuration.rb | 2 +- .../lib/emass_client/models/artifacts_get.rb | 2 +- .../artifacts_request_delete_body_inner.rb | 2 +- .../models/artifacts_response_del.rb | 2 +- .../artifacts_response_del_data_inner.rb | 2 +- .../models/artifacts_response_get.rb | 2 +- .../models/artifacts_response_put_post.rb | 2 +- .../artifacts_response_put_post_data_inner.rb | 2 +- .../lib/emass_client/models/cac_get.rb | 2 +- .../emass_client/models/cac_response_get.rb | 2 +- .../emass_client/models/cac_response_post.rb | 2 +- .../models/cac_response_post_data_inner.rb | 2 +- .../models/cloud_resources_delete.rb | 2 +- .../cloud_resources_delete_body_inner.rb | 2 +- .../models/cloud_resources_post_delete.rb | 2 +- .../models/cloud_resources_response_post.rb | 2 +- .../lib/emass_client/models/cmmc_get.rb | 2 +- .../emass_client/models/cmmc_response_get.rb | 2 +- .../emass_client/models/connectivity_ccsd.rb | 2 +- .../container_resources_delete_body_inner.rb | 2 +- .../containers_resources_post_delete.rb | 2 +- .../models/containers_response_delete.rb | 2 +- .../models/containers_response_post.rb | 2 +- .../lib/emass_client/models/controls_get.rb | 2 +- .../lib/emass_client/models/controls_put.rb | 2 +- .../models/controls_response_get.rb | 2 +- .../models/controls_response_put.rb | 2 +- .../models/dashboard_mock_response.rb | 2 +- .../dashboard_mock_response_pagination.rb | 2 +- .../models/definition_transitions.rb | 2 +- .../models/instances_transitions.rb | 2 +- .../models/milestone_response_delete.rb | 2 +- .../models/milestone_response_get.rb | 2 +- .../milestone_response_get_milestone.rb | 2 +- .../models/milestone_response_post.rb | 2 +- .../models/milestone_response_put.rb | 2 +- .../lib/emass_client/models/milestones_get.rb | 2 +- .../models/milestones_put_post_delete.rb | 2 +- .../milestones_request_delete_body_inner.rb | 2 +- .../models/milestones_required_post.rb | 2 +- .../models/milestones_required_put.rb | 2 +- .../lib/emass_client/models/mock_object.rb | 2 +- .../lib/emass_client/models/pac_get.rb | 2 +- .../lib/emass_client/models/pac_post.rb | 2 +- .../emass_client/models/pac_response_get.rb | 2 +- .../emass_client/models/pac_response_post.rb | 2 +- .../lib/emass_client/models/poam_get.rb | 2 +- .../emass_client/models/poam_post_put_del.rb | 2 +- .../models/poam_request_delete_body_inner.rb | 2 +- .../models/poam_response_delete.rb | 2 +- .../models/poam_response_get_poams.rb | 2 +- .../models/poam_response_get_systems.rb | 2 +- .../emass_client/models/poam_response_post.rb | 2 +- .../emass_client/models/poam_response_put.rb | 2 +- .../lib/emass_client/models/register.rb | 2 +- .../lib/emass_client/models/register_data.rb | 2 +- .../models/register_user_request_post_body.rb | 2 +- .../lib/emass_client/models/response200.rb | 2 +- .../lib/emass_client/models/response201.rb | 2 +- .../emass_client/models/response201_meta.rb | 2 +- .../lib/emass_client/models/response400.rb | 2 +- .../emass_client/models/response400_meta.rb | 2 +- .../lib/emass_client/models/response401.rb | 2 +- .../emass_client/models/response401_meta.rb | 2 +- .../lib/emass_client/models/response403.rb | 2 +- .../emass_client/models/response403_meta.rb | 2 +- .../lib/emass_client/models/response404.rb | 2 +- .../lib/emass_client/models/response405.rb | 2 +- .../emass_client/models/response405_meta.rb | 2 +- .../lib/emass_client/models/response411.rb | 2 +- .../emass_client/models/response411_meta.rb | 2 +- .../lib/emass_client/models/response490.rb | 2 +- .../emass_client/models/response490_meta.rb | 2 +- .../lib/emass_client/models/response500.rb | 2 +- .../emass_client/models/response500_meta.rb | 2 +- .../lib/emass_client/models/role_category.rb | 2 +- .../lib/emass_client/models/roles.rb | 2 +- .../lib/emass_client/models/ssps.rb | 2 +- .../lib/emass_client/models/stage.rb | 2 +- .../models/static_code_application_post.rb | 2 +- .../emass_client/models/static_code_post.rb | 2 +- .../models/static_code_request_post_body.rb | 2 +- ...atic_code_request_post_body_application.rb | 2 +- .../models/static_code_response_post.rb | 2 +- .../models/success200_response.rb | 2 +- .../models/success200_response_data_inner.rb | 2 +- .../emass_client/models/system_response.rb | 2 +- .../models/system_roles_category_response.rb | 2 +- .../models/system_roles_response.rb | 2 +- .../system_roles_response_data_inner.rb | 2 +- .../lib/emass_client/models/systems.rb | 2 +- .../emass_client/models/systems_response.rb | 2 +- .../lib/emass_client/models/test.rb | 2 +- .../lib/emass_client/models/test_data.rb | 2 +- .../emass_client/models/test_results_get.rb | 2 +- .../emass_client/models/test_results_post.rb | 2 +- .../models/test_results_response_get.rb | 2 +- .../models/test_results_response_post.rb | 2 +- .../lib/emass_client/models/users.rb | 2 +- .../models/workflow_definition_get.rb | 2 +- .../workflow_definition_response_get.rb | 2 +- .../models/workflow_instance_get.rb | 2 +- .../models/workflow_instance_response_get.rb | 2 +- .../models/workflow_instances_get.rb | 2 +- .../models/workflow_instances_response_get.rb | 2 +- ...kflow_instances_response_get_pagination.rb | 2 +- src/ruby_client/lib/emass_client/version.rb | 2 +- .../spec/api/artifacts_api_spec.rb | 2 +- .../spec/api/artifacts_export_api_spec.rb | 2 +- src/ruby_client/spec/api/cac_api_spec.rb | 2 +- .../api/cloud_resource_results_api_spec.rb | 2 +- .../spec/api/cmmc_assessments_api_spec.rb | 2 +- .../api/container_scan_results_api_spec.rb | 2 +- src/ruby_client/spec/api/controls_api_spec.rb | 2 +- ...nterprise_artifacts_dashboards_api_spec.rb | 2 +- .../enterprise_poam_dashboards_api_spec.rb | 2 +- ...e_security_controls_dashboards_api_spec.rb | 2 +- ..._hardware_resources_dashboards_api_spec.rb | 2 +- ..._software_resources_dashboards_api_spec.rb | 2 +- ...se_terms_conditions_dashboards_api_spec.rb | 2 +- ...prise_vulnerability_dashboards_api_spec.rb | 2 +- ...a_inventory_summary_dashboards_api_spec.rb | 2 +- .../hardware_baseline_dashboards_api_spec.rb | 2 +- .../spec/api/milestones_api_spec.rb | 2 +- src/ruby_client/spec/api/pac_api_spec.rb | 2 +- src/ruby_client/spec/api/poam_api_spec.rb | 2 +- ...ports_and_protocols_dashboards_api_spec.rb | 2 +- .../privacy_compliance_dashboards_api_spec.rb | 2 +- .../spec/api/registration_api_spec.rb | 2 +- .../software_baseline_dashboards_api_spec.rb | 2 +- .../spec/api/static_code_scans_api_spec.rb | 2 +- .../system_a20_summary_dashboard_api_spec.rb | 2 +- .../system_aa_summary_dashboard_api_spec.rb | 2 +- .../system_associations_dashboard_api_spec.rb | 2 +- ...n_integration_status_dashboard_api_spec.rb | 2 +- ...09_reporting_summary_dashboard_api_spec.rb | 2 +- .../spec/api/system_roles_api_spec.rb | 2 +- .../api/system_status_dashboard_api_spec.rb | 2 +- src/ruby_client/spec/api/systems_api_spec.rb | 2 +- src/ruby_client/spec/api/test_api_spec.rb | 2 +- .../spec/api/test_results_api_spec.rb | 2 +- .../api/threat_risks_dashboards_api_spec.rb | 2 +- .../spec/api/users_dashboard_api_spec.rb | 2 +- .../spec/api/workflow_definitions_api_spec.rb | 2 +- .../spec/api/workflow_instances_api_spec.rb | 2 +- src/ruby_client/spec/api_client_spec.rb | 2 +- src/ruby_client/spec/configuration_spec.rb | 2 +- .../spec/models/artifacts_get_spec.rb | 2 +- ...rtifacts_request_delete_body_inner_spec.rb | 2 +- .../artifacts_response_del_data_inner_spec.rb | 2 +- .../models/artifacts_response_del_spec.rb | 2 +- .../models/artifacts_response_get_spec.rb | 2 +- ...facts_response_put_post_data_inner_spec.rb | 2 +- .../artifacts_response_put_post_spec.rb | 2 +- src/ruby_client/spec/models/cac_get_spec.rb | 2 +- .../spec/models/cac_response_get_spec.rb | 2 +- .../cac_response_post_data_inner_spec.rb | 2 +- .../spec/models/cac_response_post_spec.rb | 2 +- .../cloud_resources_delete_body_inner_spec.rb | 2 +- .../models/cloud_resources_delete_spec.rb | 2 +- .../cloud_resources_post_delete_spec.rb | 2 +- .../cloud_resources_response_post_spec.rb | 2 +- src/ruby_client/spec/models/cmmc_get_spec.rb | 2 +- .../spec/models/cmmc_response_get_spec.rb | 2 +- .../spec/models/connectivity_ccsd_spec.rb | 2 +- ...tainer_resources_delete_body_inner_spec.rb | 2 +- .../containers_resources_post_delete_spec.rb | 2 +- .../models/containers_response_delete_spec.rb | 2 +- .../models/containers_response_post_spec.rb | 2 +- .../spec/models/controls_get_spec.rb | 2 +- .../spec/models/controls_put_spec.rb | 2 +- .../spec/models/controls_response_get_spec.rb | 2 +- .../spec/models/controls_response_put_spec.rb | 2 +- ...dashboard_mock_response_pagination_spec.rb | 2 +- .../models/dashboard_mock_response_spec.rb | 2 +- .../models/definition_transitions_spec.rb | 2 +- .../spec/models/instances_transitions_spec.rb | 2 +- .../models/milestone_response_delete_spec.rb | 2 +- .../milestone_response_get_milestone_spec.rb | 2 +- .../models/milestone_response_get_spec.rb | 2 +- .../models/milestone_response_post_spec.rb | 2 +- .../models/milestone_response_put_spec.rb | 2 +- .../spec/models/milestones_get_spec.rb | 2 +- .../models/milestones_put_post_delete_spec.rb | 2 +- ...lestones_request_delete_body_inner_spec.rb | 2 +- .../models/milestones_required_post_spec.rb | 2 +- .../models/milestones_required_put_spec.rb | 2 +- .../spec/models/mock_object_spec.rb | 2 +- src/ruby_client/spec/models/pac_get_spec.rb | 2 +- src/ruby_client/spec/models/pac_post_spec.rb | 2 +- .../spec/models/pac_response_get_spec.rb | 2 +- .../spec/models/pac_response_post_spec.rb | 2 +- src/ruby_client/spec/models/poam_get_spec.rb | 2 +- .../spec/models/poam_post_put_del_spec.rb | 2 +- .../poam_request_delete_body_inner_spec.rb | 2 +- .../spec/models/poam_response_delete_spec.rb | 2 +- .../models/poam_response_get_poams_spec.rb | 2 +- .../models/poam_response_get_systems_spec.rb | 2 +- .../spec/models/poam_response_post_spec.rb | 2 +- .../spec/models/poam_response_put_spec.rb | 2 +- .../spec/models/register_data_spec.rb | 2 +- src/ruby_client/spec/models/register_spec.rb | 2 +- .../register_user_request_post_body_spec.rb | 2 +- .../spec/models/response200_spec.rb | 2 +- .../spec/models/response201_meta_spec.rb | 2 +- .../spec/models/response201_spec.rb | 2 +- .../spec/models/response400_meta_spec.rb | 2 +- .../spec/models/response400_spec.rb | 2 +- .../spec/models/response401_meta_spec.rb | 2 +- .../spec/models/response401_spec.rb | 2 +- .../spec/models/response403_meta_spec.rb | 2 +- .../spec/models/response403_spec.rb | 2 +- .../spec/models/response404_spec.rb | 2 +- .../spec/models/response405_meta_spec.rb | 2 +- .../spec/models/response405_spec.rb | 2 +- .../spec/models/response411_meta_spec.rb | 2 +- .../spec/models/response411_spec.rb | 2 +- .../spec/models/response490_meta_spec.rb | 2 +- .../spec/models/response490_spec.rb | 2 +- .../spec/models/response500_meta_spec.rb | 2 +- .../spec/models/response500_spec.rb | 2 +- .../spec/models/role_category_spec.rb | 2 +- src/ruby_client/spec/models/roles_spec.rb | 2 +- src/ruby_client/spec/models/ssps_spec.rb | 2 +- src/ruby_client/spec/models/stage_spec.rb | 2 +- .../static_code_application_post_spec.rb | 2 +- .../spec/models/static_code_post_spec.rb | 2 +- ...code_request_post_body_application_spec.rb | 2 +- .../static_code_request_post_body_spec.rb | 2 +- .../models/static_code_response_post_spec.rb | 2 +- .../success200_response_data_inner_spec.rb | 2 +- .../spec/models/success200_response_spec.rb | 2 +- .../spec/models/system_response_spec.rb | 2 +- .../system_roles_category_response_spec.rb | 2 +- .../system_roles_response_data_inner_spec.rb | 2 +- .../spec/models/system_roles_response_spec.rb | 2 +- .../spec/models/systems_response_spec.rb | 2 +- src/ruby_client/spec/models/systems_spec.rb | 2 +- src/ruby_client/spec/models/test_data_spec.rb | 2 +- .../spec/models/test_results_get_spec.rb | 2 +- .../spec/models/test_results_post_spec.rb | 2 +- .../models/test_results_response_get_spec.rb | 2 +- .../models/test_results_response_post_spec.rb | 2 +- src/ruby_client/spec/models/test_spec.rb | 2 +- src/ruby_client/spec/models/users_spec.rb | 2 +- .../models/workflow_definition_get_spec.rb | 2 +- .../workflow_definition_response_get_spec.rb | 2 +- .../spec/models/workflow_instance_get_spec.rb | 2 +- .../workflow_instance_response_get_spec.rb | 2 +- .../models/workflow_instances_get_spec.rb | 2 +- ..._instances_response_get_pagination_spec.rb | 2 +- .../workflow_instances_response_get_spec.rb | 2 +- src/ruby_client/spec/spec_helper.rb | 2 +- src/typescript_client/api.ts | 2 +- src/typescript_client/base.ts | 2 +- src/typescript_client/common.ts | 2 +- src/typescript_client/configuration.ts | 2 +- src/typescript_client/index.ts | 2 +- 596 files changed, 1993 insertions(+), 1045 deletions(-) diff --git a/src/python_client/README.md b/src/python_client/README.md index e65724d6..760c2134 100644 --- a/src/python_client/README.md +++ b/src/python_client/README.md @@ -7,8 +7,8 @@ Representational State Transfer (REST) Application Programming Interface (API) s This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/__init__.py b/src/python_client/emass_client/__init__.py index b9ecfd8f..17959ed9 100644 --- a/src/python_client/emass_client/__init__.py +++ b/src/python_client/emass_client/__init__.py @@ -11,8 +11,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. @@ -51,7 +51,7 @@ Execute `pytest` to run the tests. -__version__ = "3.11.1" +__version__ = "3.12.0" # import apis into sdk package from emass_client.api.artifacts_api import ArtifactsApi diff --git a/src/python_client/emass_client/api/artifacts_api.py b/src/python_client/emass_client/api/artifacts_api.py index 4d79fedb..551e3d04 100644 --- a/src/python_client/emass_client/api/artifacts_api.py +++ b/src/python_client/emass_client/api/artifacts_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. @@ -89,7 +89,16 @@ def __init__(self, api_client=None) -> None: self.api_client = api_client @validate_call - def add_artifacts_by_system_id(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], zipper : Union[StrictBytes, StrictStr], is_bulk : Annotated[Optional[StrictBool], Field(description="**Is Bulk**: If no value is specified, the default is false, and an individual artifact file is expected. When set to true, a .zip file is expected which can contain multiple artifact files\" ")] = None, is_template : Optional[StrictBool] = None, type : Optional[StrictStr] = None, category : Optional[StrictStr] = None, **kwargs) -> ArtifactsResponsePutPost: # noqa: E501 + def add_artifacts_by_system_id( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + zipper: Union[StrictBytes, StrictStr], + is_bulk: Annotated[Optional[StrictBool], Field(description="**Is Bulk**: If no value is specified, the default is false, and an individual artifact file is expected. When set to true, a .zip file is expected which can contain multiple artifact files\" ")] = None, + is_template: Optional[StrictBool] = None, + type: Optional[StrictStr] = None, + category: Optional[StrictStr] = None, + **kwargs, + ) -> ArtifactsResponsePutPost: """Add one or many artifacts in a system # noqa: E501 Information
The body of a request through the Artifacts POST endpoint accepts a single binary file. Two Artifact POST methods are currently accepted: individual and bulk. Filename uniqueness within an eMASS system will be enforced by the API for both methods.

For POST requests that should result in a single artifact, the request should include the file.

For POST requests that should result in the creation of many artifacts, the request should include a single file with the extension \".zip\" only and the parameter isBulk should be set to true. This .zip file should contain one or more files corresponding to existing artifacts or new artifacts that will be created upon successful receipt.

Upon successful receipt of one or many artifacts, if a file is matched via filename to an artifact existing within the application, the file associated with the artifact will be updated. If no artifact is matched via filename to the application, a new artifact will be created with the following default values. Any values not specified below will be null To update values other than the file itself, please submit a PUT request.
Business Rules
Artifact cannot be saved if the fields below exceed the following character limits: Artifact cannot be saved if the file does not have an allowable file extension/type: .docx,.doc,.txt,.rtf,.xfdl,.xml,.mht,.mh,tml,.html,.htm,.pdf,.mdb,.accdb,.ppt, .pptx,.xls,.xlsx,.csv,.log,.jpeg,.jpg,.tiff,.bmp,.tif,.png,.gif,.zip,.rar,.msg, .vsd,.vsw,.vdx,.z{#},.ckl,.avi,.vsdx Artifact version cannot be saved if an Artifact with the same file name (filename) already exist in the system. Artifact cannot be saved if the file size exceeds 30MB. Artifact cannot be saved if the following fields are missing data: Artifact cannot be saved if the Last Review Date (`lastReviewedDate`) is set in the future. # noqa: E501 @@ -129,7 +138,16 @@ def add_artifacts_by_system_id(self, system_id : Annotated[StrictInt, Field(desc return self.add_artifacts_by_system_id_with_http_info(system_id, zipper, is_bulk, is_template, type, category, **kwargs) # noqa: E501 @validate_call - def add_artifacts_by_system_id_with_http_info(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], zipper : Union[StrictBytes, StrictStr], is_bulk : Annotated[Optional[StrictBool], Field(description="**Is Bulk**: If no value is specified, the default is false, and an individual artifact file is expected. When set to true, a .zip file is expected which can contain multiple artifact files\" ")] = None, is_template : Optional[StrictBool] = None, type : Optional[StrictStr] = None, category : Optional[StrictStr] = None, **kwargs) -> ApiResponse: # noqa: E501 + def add_artifacts_by_system_id_with_http_info( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + zipper: Union[StrictBytes, StrictStr], + is_bulk: Annotated[Optional[StrictBool], Field(description="**Is Bulk**: If no value is specified, the default is false, and an individual artifact file is expected. When set to true, a .zip file is expected which can contain multiple artifact files\" ")] = None, + is_template: Optional[StrictBool] = None, + type: Optional[StrictStr] = None, + category: Optional[StrictStr] = None, + **kwargs, + ) -> ApiResponse: """Add one or many artifacts in a system # noqa: E501 Information
The body of a request through the Artifacts POST endpoint accepts a single binary file. Two Artifact POST methods are currently accepted: individual and bulk. Filename uniqueness within an eMASS system will be enforced by the API for both methods.

For POST requests that should result in a single artifact, the request should include the file.

For POST requests that should result in the creation of many artifacts, the request should include a single file with the extension \".zip\" only and the parameter isBulk should be set to true. This .zip file should contain one or more files corresponding to existing artifacts or new artifacts that will be created upon successful receipt.

Upon successful receipt of one or many artifacts, if a file is matched via filename to an artifact existing within the application, the file associated with the artifact will be updated. If no artifact is matched via filename to the application, a new artifact will be created with the following default values. Any values not specified below will be null To update values other than the file itself, please submit a PUT request.
Business Rules
Artifact cannot be saved if the fields below exceed the following character limits: Artifact cannot be saved if the file does not have an allowable file extension/type: .docx,.doc,.txt,.rtf,.xfdl,.xml,.mht,.mh,tml,.html,.htm,.pdf,.mdb,.accdb,.ppt, .pptx,.xls,.xlsx,.csv,.log,.jpeg,.jpg,.tiff,.bmp,.tif,.png,.gif,.zip,.rar,.msg, .vsd,.vsw,.vdx,.z{#},.ckl,.avi,.vsdx Artifact version cannot be saved if an Artifact with the same file name (filename) already exist in the system. Artifact cannot be saved if the file size exceeds 30MB. Artifact cannot be saved if the following fields are missing data: Artifact cannot be saved if the Last Review Date (`lastReviewedDate`) is set in the future. # noqa: E501 @@ -284,7 +302,12 @@ def add_artifacts_by_system_id_with_http_info(self, system_id : Annotated[Strict _request_auth=_params.get('_request_auth')) @validate_call - def delete_artifact(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], artifacts_request_delete_body_inner : Annotated[List[ArtifactsRequestDeleteBodyInner], Field(description="Delete artifact files for the given System Id")], **kwargs) -> ArtifactsResponseDel: # noqa: E501 + def delete_artifact( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + artifacts_request_delete_body_inner: Annotated[List[ArtifactsRequestDeleteBodyInner], Field(description="Delete artifact files for the given System Id")], + **kwargs, + ) -> ArtifactsResponseDel: """Remove one or many artifacts in a system # noqa: E501 Remove the Artifact(s) matching `systemId` path parameter and request body artifact(s) file name

Note: Multiple files can be deleted by providing multiple file names at the CL (comma delimited) Example: --files file1.txt, file2.txt # noqa: E501 @@ -316,7 +339,12 @@ def delete_artifact(self, system_id : Annotated[StrictInt, Field(description="** return self.delete_artifact_with_http_info(system_id, artifacts_request_delete_body_inner, **kwargs) # noqa: E501 @validate_call - def delete_artifact_with_http_info(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], artifacts_request_delete_body_inner : Annotated[List[ArtifactsRequestDeleteBodyInner], Field(description="Delete artifact files for the given System Id")], **kwargs) -> ApiResponse: # noqa: E501 + def delete_artifact_with_http_info( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + artifacts_request_delete_body_inner: Annotated[List[ArtifactsRequestDeleteBodyInner], Field(description="Delete artifact files for the given System Id")], + **kwargs, + ) -> ApiResponse: """Remove one or many artifacts in a system # noqa: E501 Remove the Artifact(s) matching `systemId` path parameter and request body artifact(s) file name

Note: Multiple files can be deleted by providing multiple file names at the CL (comma delimited) Example: --files file1.txt, file2.txt # noqa: E501 @@ -444,7 +472,16 @@ def delete_artifact_with_http_info(self, system_id : Annotated[StrictInt, Field( _request_auth=_params.get('_request_auth')) @validate_call - def get_system_artifacts(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], filename : Annotated[Optional[StrictStr], Field(description="**File Name**: The file name (to include file-extension).")] = None, control_acronyms : Annotated[Optional[StrictStr], Field(description="**Control Acronym**: Filter query by given system acronym (single value or comma separated).")] = None, assessment_procedures : Annotated[Optional[StrictStr], Field(description="**Assessment Procedure**: Filter query by given Security Control Assessment Procedure (single value or comma separated).")] = None, ccis : Annotated[Optional[StrictStr], Field(description="**CCI System**: Filter query by Control Correlation Identifiers (CCIs) (single value or comma separated).")] = None, system_only : Annotated[Optional[StrictBool], Field(description="**Systems Only**: Indicates that only system(s) information is retrieved.")] = None, **kwargs) -> ArtifactsResponseGet: # noqa: E501 + def get_system_artifacts( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + filename: Annotated[Optional[StrictStr], Field(description="**File Name**: The file name (to include file-extension).")] = None, + control_acronyms: Annotated[Optional[StrictStr], Field(description="**Control Acronym**: Filter query by given system acronym (single value or comma separated).")] = None, + assessment_procedures: Annotated[Optional[StrictStr], Field(description="**Assessment Procedure**: Filter query by given Security Control Assessment Procedure (single value or comma separated).")] = None, + ccis: Annotated[Optional[StrictStr], Field(description="**CCI System**: Filter query by Control Correlation Identifiers (CCIs) (single value or comma separated).")] = None, + system_only: Annotated[Optional[StrictBool], Field(description="**Systems Only**: Indicates that only system(s) information is retrieved.")] = None, + **kwargs, + ) -> ArtifactsResponseGet: """Get one or many artifacts in a system # noqa: E501 Returns selected artifacts matching parameters to include the file name containing the artifacts. # noqa: E501 @@ -484,7 +521,16 @@ def get_system_artifacts(self, system_id : Annotated[StrictInt, Field(descriptio return self.get_system_artifacts_with_http_info(system_id, filename, control_acronyms, assessment_procedures, ccis, system_only, **kwargs) # noqa: E501 @validate_call - def get_system_artifacts_with_http_info(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], filename : Annotated[Optional[StrictStr], Field(description="**File Name**: The file name (to include file-extension).")] = None, control_acronyms : Annotated[Optional[StrictStr], Field(description="**Control Acronym**: Filter query by given system acronym (single value or comma separated).")] = None, assessment_procedures : Annotated[Optional[StrictStr], Field(description="**Assessment Procedure**: Filter query by given Security Control Assessment Procedure (single value or comma separated).")] = None, ccis : Annotated[Optional[StrictStr], Field(description="**CCI System**: Filter query by Control Correlation Identifiers (CCIs) (single value or comma separated).")] = None, system_only : Annotated[Optional[StrictBool], Field(description="**Systems Only**: Indicates that only system(s) information is retrieved.")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_system_artifacts_with_http_info( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + filename: Annotated[Optional[StrictStr], Field(description="**File Name**: The file name (to include file-extension).")] = None, + control_acronyms: Annotated[Optional[StrictStr], Field(description="**Control Acronym**: Filter query by given system acronym (single value or comma separated).")] = None, + assessment_procedures: Annotated[Optional[StrictStr], Field(description="**Assessment Procedure**: Filter query by given Security Control Assessment Procedure (single value or comma separated).")] = None, + ccis: Annotated[Optional[StrictStr], Field(description="**CCI System**: Filter query by Control Correlation Identifiers (CCIs) (single value or comma separated).")] = None, + system_only: Annotated[Optional[StrictBool], Field(description="**Systems Only**: Indicates that only system(s) information is retrieved.")] = None, + **kwargs, + ) -> ApiResponse: """Get one or many artifacts in a system # noqa: E501 Returns selected artifacts matching parameters to include the file name containing the artifacts. # noqa: E501 @@ -631,7 +677,12 @@ def get_system_artifacts_with_http_info(self, system_id : Annotated[StrictInt, F _request_auth=_params.get('_request_auth')) @validate_call - def update_artifact_by_system_id(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], request_body : Annotated[List[object], Field(description="See `information` above for additional instructions")], **kwargs) -> ArtifactsResponsePutPost: # noqa: E501 + def update_artifact_by_system_id( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + request_body: Annotated[List[object], Field(description="See `information` above for additional instructions")], + **kwargs, + ) -> ArtifactsResponsePutPost: """Update one or many artifacts in a system # noqa: E501 Updates an artifact for given `systemId` path parameter

**Request Body Required Fields** - `filename` - `isTemplate` - `type` - `category` Information
The PUT request will replace all existing data with the field/value combinations included in the request body. If any fields are not included, the absent fields will become null. The fields `name` and `isTemplate` are non-nullable fields. If not specified in the PUT command they will default to the following: - `name=filename` - `isTemplate=false` Also, note that one-to-many fields (`controls` and `ccis`) will also be replaced with the values specified in the PUT. If existing `control or cci` mappings exist in eMASS, the values in the PUT will not append, but rather replace all existing control and cci mappings with the values in the request body. # noqa: E501 @@ -663,7 +714,12 @@ def update_artifact_by_system_id(self, system_id : Annotated[StrictInt, Field(de return self.update_artifact_by_system_id_with_http_info(system_id, request_body, **kwargs) # noqa: E501 @validate_call - def update_artifact_by_system_id_with_http_info(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], request_body : Annotated[List[object], Field(description="See `information` above for additional instructions")], **kwargs) -> ApiResponse: # noqa: E501 + def update_artifact_by_system_id_with_http_info( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + request_body: Annotated[List[object], Field(description="See `information` above for additional instructions")], + **kwargs, + ) -> ApiResponse: """Update one or many artifacts in a system # noqa: E501 Updates an artifact for given `systemId` path parameter

**Request Body Required Fields** - `filename` - `isTemplate` - `type` - `category` Information
The PUT request will replace all existing data with the field/value combinations included in the request body. If any fields are not included, the absent fields will become null. The fields `name` and `isTemplate` are non-nullable fields. If not specified in the PUT command they will default to the following: - `name=filename` - `isTemplate=false` Also, note that one-to-many fields (`controls` and `ccis`) will also be replaced with the values specified in the PUT. If existing `control or cci` mappings exist in eMASS, the values in the PUT will not append, but rather replace all existing control and cci mappings with the values in the request body. # noqa: E501 diff --git a/src/python_client/emass_client/api/artifacts_export_api.py b/src/python_client/emass_client/api/artifacts_export_api.py index a1e2a096..b156e9a7 100644 --- a/src/python_client/emass_client/api/artifacts_export_api.py +++ b/src/python_client/emass_client/api/artifacts_export_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. @@ -84,7 +84,13 @@ def __init__(self, api_client=None) -> None: self.api_client = api_client @validate_call - def get_system_artifacts_export(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], filename : Annotated[StrictStr, Field(description="**File Name**: The file name (to include file-extension).")], compress : Annotated[Optional[StrictBool], Field(description="**Compress File**: Determines if returned file is compressed.")] = None, **kwargs) -> bytearray: # noqa: E501 + def get_system_artifacts_export( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + filename: Annotated[StrictStr, Field(description="**File Name**: The file name (to include file-extension).")], + compress: Annotated[Optional[StrictBool], Field(description="**Compress File**: Determines if returned file is compressed.")] = None, + **kwargs, + ) -> bytearray: """Get the file of an artifact in a system # noqa: E501 Sample Responce
Binary file associated with given filename.
If `compress` parameter is specified, zip archive of binary file associated with given filename. # noqa: E501 @@ -118,7 +124,13 @@ def get_system_artifacts_export(self, system_id : Annotated[StrictInt, Field(des return self.get_system_artifacts_export_with_http_info(system_id, filename, compress, **kwargs) # noqa: E501 @validate_call - def get_system_artifacts_export_with_http_info(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], filename : Annotated[StrictStr, Field(description="**File Name**: The file name (to include file-extension).")], compress : Annotated[Optional[StrictBool], Field(description="**Compress File**: Determines if returned file is compressed.")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_system_artifacts_export_with_http_info( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + filename: Annotated[StrictStr, Field(description="**File Name**: The file name (to include file-extension).")], + compress: Annotated[Optional[StrictBool], Field(description="**Compress File**: Determines if returned file is compressed.")] = None, + **kwargs, + ) -> ApiResponse: """Get the file of an artifact in a system # noqa: E501 Sample Responce
Binary file associated with given filename.
If `compress` parameter is specified, zip archive of binary file associated with given filename. # noqa: E501 diff --git a/src/python_client/emass_client/api/cac_api.py b/src/python_client/emass_client/api/cac_api.py index 454bbc41..ec0eb21c 100644 --- a/src/python_client/emass_client/api/cac_api.py +++ b/src/python_client/emass_client/api/cac_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. @@ -87,7 +87,12 @@ def __init__(self, api_client=None) -> None: self.api_client = api_client @validate_call - def add_system_cac(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], request_body : Annotated[List[object], Field(description="Add control(s) to second role of CAC")], **kwargs) -> CacResponsePost: # noqa: E501 + def add_system_cac( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + request_body: Annotated[List[object], Field(description="Add control(s) to second role of CAC")], + **kwargs, + ) -> CacResponsePost: """Submit control to second role of CAC # noqa: E501 **Request Body Required Fields** - `controlAcronym` - `comments` **Notes:** - Comments `comments` are not required at the first role of the CAC but are required at the second role of the CAC. Comments cannot exceed 10,000 characters. - POST requests will only yield successful results if the control is currently sitting at the first role of the CAC. If the control is not currently sitting at the first role, then an error will be returned. # noqa: E501 @@ -119,7 +124,12 @@ def add_system_cac(self, system_id : Annotated[StrictInt, Field(description="**S return self.add_system_cac_with_http_info(system_id, request_body, **kwargs) # noqa: E501 @validate_call - def add_system_cac_with_http_info(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], request_body : Annotated[List[object], Field(description="Add control(s) to second role of CAC")], **kwargs) -> ApiResponse: # noqa: E501 + def add_system_cac_with_http_info( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + request_body: Annotated[List[object], Field(description="Add control(s) to second role of CAC")], + **kwargs, + ) -> ApiResponse: """Submit control to second role of CAC # noqa: E501 **Request Body Required Fields** - `controlAcronym` - `comments` **Notes:** - Comments `comments` are not required at the first role of the CAC but are required at the second role of the CAC. Comments cannot exceed 10,000 characters. - POST requests will only yield successful results if the control is currently sitting at the first role of the CAC. If the control is not currently sitting at the first role, then an error will be returned. # noqa: E501 @@ -250,7 +260,12 @@ def add_system_cac_with_http_info(self, system_id : Annotated[StrictInt, Field(d _request_auth=_params.get('_request_auth')) @validate_call - def get_system_cac(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], control_acronyms : Annotated[Optional[StrictStr], Field(description="**Control Acronym**: Filter query by given system acronym (single value or comma separated).")] = None, **kwargs) -> CacResponseGet: # noqa: E501 + def get_system_cac( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + control_acronyms: Annotated[Optional[StrictStr], Field(description="**Control Acronym**: Filter query by given system acronym (single value or comma separated).")] = None, + **kwargs, + ) -> CacResponseGet: """Get location of one or many controls in CAC # noqa: E501 Returns the location of a system's package in the Control Approval Chain (CAC) for matching `systemId` path parameter # noqa: E501 @@ -282,7 +297,12 @@ def get_system_cac(self, system_id : Annotated[StrictInt, Field(description="**S return self.get_system_cac_with_http_info(system_id, control_acronyms, **kwargs) # noqa: E501 @validate_call - def get_system_cac_with_http_info(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], control_acronyms : Annotated[Optional[StrictStr], Field(description="**Control Acronym**: Filter query by given system acronym (single value or comma separated).")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_system_cac_with_http_info( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + control_acronyms: Annotated[Optional[StrictStr], Field(description="**Control Acronym**: Filter query by given system acronym (single value or comma separated).")] = None, + **kwargs, + ) -> ApiResponse: """Get location of one or many controls in CAC # noqa: E501 Returns the location of a system's package in the Control Approval Chain (CAC) for matching `systemId` path parameter # noqa: E501 diff --git a/src/python_client/emass_client/api/cloud_resource_results_api.py b/src/python_client/emass_client/api/cloud_resource_results_api.py index 42515223..7234b555 100644 --- a/src/python_client/emass_client/api/cloud_resource_results_api.py +++ b/src/python_client/emass_client/api/cloud_resource_results_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. @@ -88,7 +88,12 @@ def __init__(self, api_client=None) -> None: self.api_client = api_client @validate_call - def add_cloud_resources_by_system_id(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], request_body : Annotated[List[object], Field(description="Add cloud resources and their scan results")], **kwargs) -> CloudResourcesResponsePost: # noqa: E501 + def add_cloud_resources_by_system_id( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + request_body: Annotated[List[object], Field(description="Add cloud resources and their scan results")], + **kwargs, + ) -> CloudResourcesResponsePost: """Add one or many cloud resources and their scan results # noqa: E501 Add cloud resources and their scan results in the assets module for a system `systemId` **Request Body Required Fields** - `provider` - `resourceId` - `resourceName` - `resourceType` - Compliance Results Object Array `complianceResults` - `cspPolicyDefinitionId` - `isCompliant` - `policyDefinitionTitle` **Example Request Body Required Fields** ``` [ { \"provider\": \"provide name\", \"resourceId\": \"resource identification\", \"resourceName\": \"resource name\", \"resourceType\": \"resource type\", \"complianceResults\": [ { \"cspPolicyDefinitionId\": \"CSP policy definition identification\", \"policyDefinitionTitle\": \"policy definition title\", \"isCompliant\": [true or false] } ] } ] ``` # noqa: E501 @@ -120,7 +125,12 @@ def add_cloud_resources_by_system_id(self, system_id : Annotated[StrictInt, Fiel return self.add_cloud_resources_by_system_id_with_http_info(system_id, request_body, **kwargs) # noqa: E501 @validate_call - def add_cloud_resources_by_system_id_with_http_info(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], request_body : Annotated[List[object], Field(description="Add cloud resources and their scan results")], **kwargs) -> ApiResponse: # noqa: E501 + def add_cloud_resources_by_system_id_with_http_info( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + request_body: Annotated[List[object], Field(description="Add cloud resources and their scan results")], + **kwargs, + ) -> ApiResponse: """Add one or many cloud resources and their scan results # noqa: E501 Add cloud resources and their scan results in the assets module for a system `systemId` **Request Body Required Fields** - `provider` - `resourceId` - `resourceName` - `resourceType` - Compliance Results Object Array `complianceResults` - `cspPolicyDefinitionId` - `isCompliant` - `policyDefinitionTitle` **Example Request Body Required Fields** ``` [ { \"provider\": \"provide name\", \"resourceId\": \"resource identification\", \"resourceName\": \"resource name\", \"resourceType\": \"resource type\", \"complianceResults\": [ { \"cspPolicyDefinitionId\": \"CSP policy definition identification\", \"policyDefinitionTitle\": \"policy definition title\", \"isCompliant\": [true or false] } ] } ] ``` # noqa: E501 @@ -251,7 +261,12 @@ def add_cloud_resources_by_system_id_with_http_info(self, system_id : Annotated[ _request_auth=_params.get('_request_auth')) @validate_call - def delete_cloud_resources(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], cloud_resources_delete_body_inner : Annotated[List[CloudResourcesDeleteBodyInner], Field(description="Delete the given Cloud Resource Id")], **kwargs) -> CloudResourcesDelete: # noqa: E501 + def delete_cloud_resources( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + cloud_resources_delete_body_inner: Annotated[List[CloudResourcesDeleteBodyInner], Field(description="Delete the given Cloud Resource Id")], + **kwargs, + ) -> CloudResourcesDelete: """Remove one or many cloud resources in a system # noqa: E501 Removes cloud resources and their scan results in the assets module for a system `systemId` # noqa: E501 @@ -283,7 +298,12 @@ def delete_cloud_resources(self, system_id : Annotated[StrictInt, Field(descript return self.delete_cloud_resources_with_http_info(system_id, cloud_resources_delete_body_inner, **kwargs) # noqa: E501 @validate_call - def delete_cloud_resources_with_http_info(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], cloud_resources_delete_body_inner : Annotated[List[CloudResourcesDeleteBodyInner], Field(description="Delete the given Cloud Resource Id")], **kwargs) -> ApiResponse: # noqa: E501 + def delete_cloud_resources_with_http_info( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + cloud_resources_delete_body_inner: Annotated[List[CloudResourcesDeleteBodyInner], Field(description="Delete the given Cloud Resource Id")], + **kwargs, + ) -> ApiResponse: """Remove one or many cloud resources in a system # noqa: E501 Removes cloud resources and their scan results in the assets module for a system `systemId` # noqa: E501 diff --git a/src/python_client/emass_client/api/cmmc_assessments_api.py b/src/python_client/emass_client/api/cmmc_assessments_api.py index f53d8d35..f595c09c 100644 --- a/src/python_client/emass_client/api/cmmc_assessments_api.py +++ b/src/python_client/emass_client/api/cmmc_assessments_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. @@ -83,7 +83,11 @@ def __init__(self, api_client=None) -> None: self.api_client = api_client @validate_call - def get_cmmc_assessments(self, since_date : Annotated[StrictStr, Field(description="**Date** CMMC date (Unix date format)")], **kwargs) -> CmmcResponseGet: # noqa: E501 + def get_cmmc_assessments( + self, + since_date: Annotated[StrictStr, Field(description="**Date** CMMC date (Unix date format)")], + **kwargs, + ) -> CmmcResponseGet: """Get CMMC assessment information # noqa: E501 Get all CMMC assessment after the given date `sinceDate` parameter. It is available to CMMC eMASS only. # noqa: E501 @@ -113,7 +117,11 @@ def get_cmmc_assessments(self, since_date : Annotated[StrictStr, Field(descripti return self.get_cmmc_assessments_with_http_info(since_date, **kwargs) # noqa: E501 @validate_call - def get_cmmc_assessments_with_http_info(self, since_date : Annotated[StrictStr, Field(description="**Date** CMMC date (Unix date format)")], **kwargs) -> ApiResponse: # noqa: E501 + def get_cmmc_assessments_with_http_info( + self, + since_date: Annotated[StrictStr, Field(description="**Date** CMMC date (Unix date format)")], + **kwargs, + ) -> ApiResponse: """Get CMMC assessment information # noqa: E501 Get all CMMC assessment after the given date `sinceDate` parameter. It is available to CMMC eMASS only. # noqa: E501 diff --git a/src/python_client/emass_client/api/container_scan_results_api.py b/src/python_client/emass_client/api/container_scan_results_api.py index f1240879..aa53e0ca 100644 --- a/src/python_client/emass_client/api/container_scan_results_api.py +++ b/src/python_client/emass_client/api/container_scan_results_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. @@ -88,7 +88,12 @@ def __init__(self, api_client=None) -> None: self.api_client = api_client @validate_call - def add_container_sans_by_system_id(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], request_body : Annotated[List[object], Field(description="Add containers and their scan results")], **kwargs) -> ContainersResponsePost: # noqa: E501 + def add_container_sans_by_system_id( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + request_body: Annotated[List[object], Field(description="Add containers and their scan results")], + **kwargs, + ) -> ContainersResponsePost: """Add one or many containers and their scan results # noqa: E501 Add containers and their scan results in the assets module for a system `systemId`. **Request Body Required Fields** - `containerId` - `containerName` - `time` - Bench Marks Object Array `benchmarks` - `benchmark` - Results Object Array `results` - `ruleId` - `status` - `lastSeen` **Example Request Body Required Fields** ``` [ { \"containerId\": \"container identification\", \"containerName\": \"container name\", \"time\": Datetime of scan/result (1648217219), \"benchmarks\": [ { \"benchmark\": \"RHEL_8_STIG\", \"results\": [ { \"ruleId\": \"rule identification\", \"status\": [Pass,Fail,Other,Not Reviewed,Not Checked,Not Applicable], \"lastSeen\": Unix date format (1648217219) }, { \"ruleId\": \"rule identification\", \"status\": [Pass,Fail,Other,Not Reviewed,Not Checked,Not Applicable], \"lastSeen\": Unix date format (1648217219) } ] } ] } ] ```` # noqa: E501 @@ -120,7 +125,12 @@ def add_container_sans_by_system_id(self, system_id : Annotated[StrictInt, Field return self.add_container_sans_by_system_id_with_http_info(system_id, request_body, **kwargs) # noqa: E501 @validate_call - def add_container_sans_by_system_id_with_http_info(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], request_body : Annotated[List[object], Field(description="Add containers and their scan results")], **kwargs) -> ApiResponse: # noqa: E501 + def add_container_sans_by_system_id_with_http_info( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + request_body: Annotated[List[object], Field(description="Add containers and their scan results")], + **kwargs, + ) -> ApiResponse: """Add one or many containers and their scan results # noqa: E501 Add containers and their scan results in the assets module for a system `systemId`. **Request Body Required Fields** - `containerId` - `containerName` - `time` - Bench Marks Object Array `benchmarks` - `benchmark` - Results Object Array `results` - `ruleId` - `status` - `lastSeen` **Example Request Body Required Fields** ``` [ { \"containerId\": \"container identification\", \"containerName\": \"container name\", \"time\": Datetime of scan/result (1648217219), \"benchmarks\": [ { \"benchmark\": \"RHEL_8_STIG\", \"results\": [ { \"ruleId\": \"rule identification\", \"status\": [Pass,Fail,Other,Not Reviewed,Not Checked,Not Applicable], \"lastSeen\": Unix date format (1648217219) }, { \"ruleId\": \"rule identification\", \"status\": [Pass,Fail,Other,Not Reviewed,Not Checked,Not Applicable], \"lastSeen\": Unix date format (1648217219) } ] } ] } ] ```` # noqa: E501 @@ -251,7 +261,12 @@ def add_container_sans_by_system_id_with_http_info(self, system_id : Annotated[S _request_auth=_params.get('_request_auth')) @validate_call - def delete_container_sans(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], container_resources_delete_body_inner : Annotated[List[ContainerResourcesDeleteBodyInner], Field(description="Delete the given Container Scan Id")], **kwargs) -> ContainersResponseDelete: # noqa: E501 + def delete_container_sans( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + container_resources_delete_body_inner: Annotated[List[ContainerResourcesDeleteBodyInner], Field(description="Delete the given Container Scan Id")], + **kwargs, + ) -> ContainersResponseDelete: """Remove one or many containers in a system # noqa: E501 Removes container scan resources and their scan results in the assets module for a system `systemId` # noqa: E501 @@ -283,7 +298,12 @@ def delete_container_sans(self, system_id : Annotated[StrictInt, Field(descripti return self.delete_container_sans_with_http_info(system_id, container_resources_delete_body_inner, **kwargs) # noqa: E501 @validate_call - def delete_container_sans_with_http_info(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], container_resources_delete_body_inner : Annotated[List[ContainerResourcesDeleteBodyInner], Field(description="Delete the given Container Scan Id")], **kwargs) -> ApiResponse: # noqa: E501 + def delete_container_sans_with_http_info( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + container_resources_delete_body_inner: Annotated[List[ContainerResourcesDeleteBodyInner], Field(description="Delete the given Container Scan Id")], + **kwargs, + ) -> ApiResponse: """Remove one or many containers in a system # noqa: E501 Removes container scan resources and their scan results in the assets module for a system `systemId` # noqa: E501 diff --git a/src/python_client/emass_client/api/controls_api.py b/src/python_client/emass_client/api/controls_api.py index 1d2cf4fe..03ebaee8 100644 --- a/src/python_client/emass_client/api/controls_api.py +++ b/src/python_client/emass_client/api/controls_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. @@ -87,7 +87,12 @@ def __init__(self, api_client=None) -> None: self.api_client = api_client @validate_call - def get_system_controls(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], acronyms : Annotated[Optional[StrictStr], Field(description="**Acronym**: The system acronym(s) being queried (single value or comma delimited values).")] = None, **kwargs) -> ControlsResponseGet: # noqa: E501 + def get_system_controls( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + acronyms: Annotated[Optional[StrictStr], Field(description="**Acronym**: The system acronym(s) being queried (single value or comma delimited values).")] = None, + **kwargs, + ) -> ControlsResponseGet: """Get control information in a system for one or many controls # noqa: E501 Returns system control information for matching `systemId` path parameter # noqa: E501 @@ -119,7 +124,12 @@ def get_system_controls(self, system_id : Annotated[StrictInt, Field(description return self.get_system_controls_with_http_info(system_id, acronyms, **kwargs) # noqa: E501 @validate_call - def get_system_controls_with_http_info(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], acronyms : Annotated[Optional[StrictStr], Field(description="**Acronym**: The system acronym(s) being queried (single value or comma delimited values).")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_system_controls_with_http_info( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + acronyms: Annotated[Optional[StrictStr], Field(description="**Acronym**: The system acronym(s) being queried (single value or comma delimited values).")] = None, + **kwargs, + ) -> ApiResponse: """Get control information in a system for one or many controls # noqa: E501 Returns system control information for matching `systemId` path parameter # noqa: E501 @@ -242,7 +252,12 @@ def get_system_controls_with_http_info(self, system_id : Annotated[StrictInt, Fi _request_auth=_params.get('_request_auth')) @validate_call - def update_control_by_system_id(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], request_body : Annotated[List[object], Field(description="Update an existing control by Id")], **kwargs) -> ControlsResponsePut: # noqa: E501 + def update_control_by_system_id( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + request_body: Annotated[List[object], Field(description="Update an existing control by Id")], + **kwargs, + ) -> ControlsResponsePut: """Update control information in a system for one or many controls # noqa: E501 Update a Control for given `systemId`
**Request Body Required Fields** - `acronym` - `responsibleEntities` - `controlDesignation` - `estimatedCompletionDate` - `implementationNarrative` The following optional fields (plus the **Request Body Required Fields**) are required based on the Implementation Status `implementationStatus` value
| Value | Required Fields |--------------------------|--------------------------------------------------- | Planned or Implemented | `slcmCriticality`, `slcmFrequency`, `slcmMethod`, `slcmReporting`, `slcmTracking`, `slcmComments` | Not Applicable | `naJustification` | Manually Inherited | `commonControlProvider`, `slcmCriticality`, `slcmFrequency`, `slcmMethod`, `slcmReporting`, `slcmTracking`, `slcmComments` If the Implementation Status `implementationStatus` value is `Inherited`, only the following fields can be updated: - `controlDesignation` - `commonnControlProvider` **NOTES:** - Implementation Plan information cannot be saved if the these fields exceed 2,000 character limits: - `naJustification`,`responsibleEntities`,`implementationNarrative`,`slcmCriticality` - `slcmFrequency`,`slcmMethod`,`slcmReporting`,`slcmTracking`,`slcmComments` - Implementation Plan information cannot be updated if Security Control does not exist in the system record. # noqa: E501 @@ -274,7 +289,12 @@ def update_control_by_system_id(self, system_id : Annotated[StrictInt, Field(des return self.update_control_by_system_id_with_http_info(system_id, request_body, **kwargs) # noqa: E501 @validate_call - def update_control_by_system_id_with_http_info(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], request_body : Annotated[List[object], Field(description="Update an existing control by Id")], **kwargs) -> ApiResponse: # noqa: E501 + def update_control_by_system_id_with_http_info( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + request_body: Annotated[List[object], Field(description="Update an existing control by Id")], + **kwargs, + ) -> ApiResponse: """Update control information in a system for one or many controls # noqa: E501 Update a Control for given `systemId`
**Request Body Required Fields** - `acronym` - `responsibleEntities` - `controlDesignation` - `estimatedCompletionDate` - `implementationNarrative` The following optional fields (plus the **Request Body Required Fields**) are required based on the Implementation Status `implementationStatus` value
| Value | Required Fields |--------------------------|--------------------------------------------------- | Planned or Implemented | `slcmCriticality`, `slcmFrequency`, `slcmMethod`, `slcmReporting`, `slcmTracking`, `slcmComments` | Not Applicable | `naJustification` | Manually Inherited | `commonControlProvider`, `slcmCriticality`, `slcmFrequency`, `slcmMethod`, `slcmReporting`, `slcmTracking`, `slcmComments` If the Implementation Status `implementationStatus` value is `Inherited`, only the following fields can be updated: - `controlDesignation` - `commonnControlProvider` **NOTES:** - Implementation Plan information cannot be saved if the these fields exceed 2,000 character limits: - `naJustification`,`responsibleEntities`,`implementationNarrative`,`slcmCriticality` - `slcmFrequency`,`slcmMethod`,`slcmReporting`,`slcmTracking`,`slcmComments` - Implementation Plan information cannot be updated if Security Control does not exist in the system record. # noqa: E501 diff --git a/src/python_client/emass_client/api/enterprise_artifacts_dashboards_api.py b/src/python_client/emass_client/api/enterprise_artifacts_dashboards_api.py index c282b773..8b14cc82 100644 --- a/src/python_client/emass_client/api/enterprise_artifacts_dashboards_api.py +++ b/src/python_client/emass_client/api/enterprise_artifacts_dashboards_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. @@ -84,7 +84,14 @@ def __init__(self, api_client=None) -> None: self.api_client = api_client @validate_call - def get_system_artifacts_details(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 + def get_system_artifacts_details( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> object: """System Artifacts Details # noqa: E501 Get system Artifacts details information. # noqa: E501 @@ -120,7 +127,14 @@ def get_system_artifacts_details(self, org_id : Annotated[StrictInt, Field(descr return self.get_system_artifacts_details_with_http_info(org_id, excludeinherited, page_index, page_size, **kwargs) # noqa: E501 @validate_call - def get_system_artifacts_details_with_http_info(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_system_artifacts_details_with_http_info( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> ApiResponse: """System Artifacts Details # noqa: E501 Get system Artifacts details information. # noqa: E501 @@ -255,7 +269,14 @@ def get_system_artifacts_details_with_http_info(self, org_id : Annotated[StrictI _request_auth=_params.get('_request_auth')) @validate_call - def get_system_artifacts_summary(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 + def get_system_artifacts_summary( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> object: """System Artifacts Summary # noqa: E501 Get system Artifacts summary information. # noqa: E501 @@ -291,7 +312,14 @@ def get_system_artifacts_summary(self, org_id : Annotated[StrictInt, Field(descr return self.get_system_artifacts_summary_with_http_info(org_id, excludeinherited, page_index, page_size, **kwargs) # noqa: E501 @validate_call - def get_system_artifacts_summary_with_http_info(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_system_artifacts_summary_with_http_info( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> ApiResponse: """System Artifacts Summary # noqa: E501 Get system Artifacts summary information. # noqa: E501 diff --git a/src/python_client/emass_client/api/enterprise_poam_dashboards_api.py b/src/python_client/emass_client/api/enterprise_poam_dashboards_api.py index 217882e5..0b001462 100644 --- a/src/python_client/emass_client/api/enterprise_poam_dashboards_api.py +++ b/src/python_client/emass_client/api/enterprise_poam_dashboards_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. @@ -84,7 +84,14 @@ def __init__(self, api_client=None) -> None: self.api_client = api_client @validate_call - def get_system_poam_details(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 + def get_system_poam_details( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> object: """System POA&M Details # noqa: E501 Get system POA&Ms details dashboard information. # noqa: E501 @@ -120,7 +127,14 @@ def get_system_poam_details(self, org_id : Annotated[StrictInt, Field(descriptio return self.get_system_poam_details_with_http_info(org_id, excludeinherited, page_index, page_size, **kwargs) # noqa: E501 @validate_call - def get_system_poam_details_with_http_info(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_system_poam_details_with_http_info( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> ApiResponse: """System POA&M Details # noqa: E501 Get system POA&Ms details dashboard information. # noqa: E501 @@ -255,7 +269,14 @@ def get_system_poam_details_with_http_info(self, org_id : Annotated[StrictInt, F _request_auth=_params.get('_request_auth')) @validate_call - def get_system_poam_summary(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 + def get_system_poam_summary( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> object: """System POA&M Summary # noqa: E501 Get systems POA&Ms summary dashboard information. # noqa: E501 @@ -291,7 +312,14 @@ def get_system_poam_summary(self, org_id : Annotated[StrictInt, Field(descriptio return self.get_system_poam_summary_with_http_info(org_id, excludeinherited, page_index, page_size, **kwargs) # noqa: E501 @validate_call - def get_system_poam_summary_with_http_info(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_system_poam_summary_with_http_info( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> ApiResponse: """System POA&M Summary # noqa: E501 Get systems POA&Ms summary dashboard information. # noqa: E501 diff --git a/src/python_client/emass_client/api/enterprise_security_controls_dashboards_api.py b/src/python_client/emass_client/api/enterprise_security_controls_dashboards_api.py index 28d37fd1..62c40147 100644 --- a/src/python_client/emass_client/api/enterprise_security_controls_dashboards_api.py +++ b/src/python_client/emass_client/api/enterprise_security_controls_dashboards_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. @@ -84,7 +84,14 @@ def __init__(self, api_client=None) -> None: self.api_client = api_client @validate_call - def get_system_assessment_procedures_details(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 + def get_system_assessment_procedures_details( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> object: """System Assessment Procedures Details # noqa: E501 Get systems assessement procdures details dashboard information. # noqa: E501 @@ -120,7 +127,14 @@ def get_system_assessment_procedures_details(self, org_id : Annotated[StrictInt, return self.get_system_assessment_procedures_details_with_http_info(org_id, excludeinherited, page_index, page_size, **kwargs) # noqa: E501 @validate_call - def get_system_assessment_procedures_details_with_http_info(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_system_assessment_procedures_details_with_http_info( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> ApiResponse: """System Assessment Procedures Details # noqa: E501 Get systems assessement procdures details dashboard information. # noqa: E501 @@ -255,7 +269,14 @@ def get_system_assessment_procedures_details_with_http_info(self, org_id : Annot _request_auth=_params.get('_request_auth')) @validate_call - def get_system_control_compliance_summary(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 + def get_system_control_compliance_summary( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> object: """System Control Compliance Summary # noqa: E501 Get systems control compliance summary dashboard information. # noqa: E501 @@ -291,7 +312,14 @@ def get_system_control_compliance_summary(self, org_id : Annotated[StrictInt, Fi return self.get_system_control_compliance_summary_with_http_info(org_id, excludeinherited, page_index, page_size, **kwargs) # noqa: E501 @validate_call - def get_system_control_compliance_summary_with_http_info(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_system_control_compliance_summary_with_http_info( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> ApiResponse: """System Control Compliance Summary # noqa: E501 Get systems control compliance summary dashboard information. # noqa: E501 @@ -426,7 +454,14 @@ def get_system_control_compliance_summary_with_http_info(self, org_id : Annotate _request_auth=_params.get('_request_auth')) @validate_call - def get_system_security_control_details(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 + def get_system_security_control_details( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> object: """System Control Compliance Details # noqa: E501 Get systems security control details dashboard information. # noqa: E501 @@ -462,7 +497,14 @@ def get_system_security_control_details(self, org_id : Annotated[StrictInt, Fiel return self.get_system_security_control_details_with_http_info(org_id, excludeinherited, page_index, page_size, **kwargs) # noqa: E501 @validate_call - def get_system_security_control_details_with_http_info(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_system_security_control_details_with_http_info( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> ApiResponse: """System Control Compliance Details # noqa: E501 Get systems security control details dashboard information. # noqa: E501 diff --git a/src/python_client/emass_client/api/enterprise_sensor_based_hardware_resources_dashboards_api.py b/src/python_client/emass_client/api/enterprise_sensor_based_hardware_resources_dashboards_api.py index 401e0085..397ee300 100644 --- a/src/python_client/emass_client/api/enterprise_sensor_based_hardware_resources_dashboards_api.py +++ b/src/python_client/emass_client/api/enterprise_sensor_based_hardware_resources_dashboards_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. @@ -84,7 +84,14 @@ def __init__(self, api_client=None) -> None: self.api_client = api_client @validate_call - def get_system_sensor_hardware_details(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 + def get_system_sensor_hardware_details( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> object: """System Sensor Hardware Details # noqa: E501 Get system sensor hardware details dashboard information. # noqa: E501 @@ -120,7 +127,14 @@ def get_system_sensor_hardware_details(self, org_id : Annotated[StrictInt, Field return self.get_system_sensor_hardware_details_with_http_info(org_id, excludeinherited, page_index, page_size, **kwargs) # noqa: E501 @validate_call - def get_system_sensor_hardware_details_with_http_info(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_system_sensor_hardware_details_with_http_info( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> ApiResponse: """System Sensor Hardware Details # noqa: E501 Get system sensor hardware details dashboard information. # noqa: E501 @@ -255,7 +269,14 @@ def get_system_sensor_hardware_details_with_http_info(self, org_id : Annotated[S _request_auth=_params.get('_request_auth')) @validate_call - def get_system_sensor_hardware_summary(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 + def get_system_sensor_hardware_summary( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> object: """System Sensor Hardware Summary # noqa: E501 Get system sensor hardware summary dashboard information. # noqa: E501 @@ -291,7 +312,14 @@ def get_system_sensor_hardware_summary(self, org_id : Annotated[StrictInt, Field return self.get_system_sensor_hardware_summary_with_http_info(org_id, excludeinherited, page_index, page_size, **kwargs) # noqa: E501 @validate_call - def get_system_sensor_hardware_summary_with_http_info(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_system_sensor_hardware_summary_with_http_info( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> ApiResponse: """System Sensor Hardware Summary # noqa: E501 Get system sensor hardware summary dashboard information. # noqa: E501 diff --git a/src/python_client/emass_client/api/enterprise_sensor_based_software_resources_dashboards_api.py b/src/python_client/emass_client/api/enterprise_sensor_based_software_resources_dashboards_api.py index 7ca3fcce..f0e144a8 100644 --- a/src/python_client/emass_client/api/enterprise_sensor_based_software_resources_dashboards_api.py +++ b/src/python_client/emass_client/api/enterprise_sensor_based_software_resources_dashboards_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. @@ -84,7 +84,14 @@ def __init__(self, api_client=None) -> None: self.api_client = api_client @validate_call - def get_system_sensor_software_counts(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 + def get_system_sensor_software_counts( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> object: """System Sensor Software Counts # noqa: E501 Get system sensor hardsoftwareware count dashboard information. # noqa: E501 @@ -120,7 +127,14 @@ def get_system_sensor_software_counts(self, org_id : Annotated[StrictInt, Field( return self.get_system_sensor_software_counts_with_http_info(org_id, excludeinherited, page_index, page_size, **kwargs) # noqa: E501 @validate_call - def get_system_sensor_software_counts_with_http_info(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_system_sensor_software_counts_with_http_info( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> ApiResponse: """System Sensor Software Counts # noqa: E501 Get system sensor hardsoftwareware count dashboard information. # noqa: E501 @@ -255,7 +269,14 @@ def get_system_sensor_software_counts_with_http_info(self, org_id : Annotated[St _request_auth=_params.get('_request_auth')) @validate_call - def get_system_sensor_software_details(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 + def get_system_sensor_software_details( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> object: """System Sensor Software Details # noqa: E501 Get system sensor hardsoftwareware details dashboard information. # noqa: E501 @@ -291,7 +312,14 @@ def get_system_sensor_software_details(self, org_id : Annotated[StrictInt, Field return self.get_system_sensor_software_details_with_http_info(org_id, excludeinherited, page_index, page_size, **kwargs) # noqa: E501 @validate_call - def get_system_sensor_software_details_with_http_info(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_system_sensor_software_details_with_http_info( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> ApiResponse: """System Sensor Software Details # noqa: E501 Get system sensor hardsoftwareware details dashboard information. # noqa: E501 @@ -426,7 +454,14 @@ def get_system_sensor_software_details_with_http_info(self, org_id : Annotated[S _request_auth=_params.get('_request_auth')) @validate_call - def get_system_sensor_software_summary(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 + def get_system_sensor_software_summary( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> object: """System Sensor Software Summary # noqa: E501 Get system sensor software summary dashboard information. # noqa: E501 @@ -462,7 +497,14 @@ def get_system_sensor_software_summary(self, org_id : Annotated[StrictInt, Field return self.get_system_sensor_software_summary_with_http_info(org_id, excludeinherited, page_index, page_size, **kwargs) # noqa: E501 @validate_call - def get_system_sensor_software_summary_with_http_info(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_system_sensor_software_summary_with_http_info( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> ApiResponse: """System Sensor Software Summary # noqa: E501 Get system sensor software summary dashboard information. # noqa: E501 diff --git a/src/python_client/emass_client/api/enterprise_terms_conditions_dashboards_api.py b/src/python_client/emass_client/api/enterprise_terms_conditions_dashboards_api.py index e0772a25..3e9ee49b 100644 --- a/src/python_client/emass_client/api/enterprise_terms_conditions_dashboards_api.py +++ b/src/python_client/emass_client/api/enterprise_terms_conditions_dashboards_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. @@ -84,7 +84,14 @@ def __init__(self, api_client=None) -> None: self.api_client = api_client @validate_call - def get_system_terms_conditions_details(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 + def get_system_terms_conditions_details( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> object: """System Terms Conditions Details # noqa: E501 Get systems terms conditions details dashboard information. # noqa: E501 @@ -120,7 +127,14 @@ def get_system_terms_conditions_details(self, org_id : Annotated[StrictInt, Fiel return self.get_system_terms_conditions_details_with_http_info(org_id, excludeinherited, page_index, page_size, **kwargs) # noqa: E501 @validate_call - def get_system_terms_conditions_details_with_http_info(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_system_terms_conditions_details_with_http_info( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> ApiResponse: """System Terms Conditions Details # noqa: E501 Get systems terms conditions details dashboard information. # noqa: E501 @@ -255,7 +269,14 @@ def get_system_terms_conditions_details_with_http_info(self, org_id : Annotated[ _request_auth=_params.get('_request_auth')) @validate_call - def get_system_terms_conditions_summary(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 + def get_system_terms_conditions_summary( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> object: """System Terms Conditions Summary # noqa: E501 Get systems terms conditions summary dashboard information. # noqa: E501 @@ -291,7 +312,14 @@ def get_system_terms_conditions_summary(self, org_id : Annotated[StrictInt, Fiel return self.get_system_terms_conditions_summary_with_http_info(org_id, excludeinherited, page_index, page_size, **kwargs) # noqa: E501 @validate_call - def get_system_terms_conditions_summary_with_http_info(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_system_terms_conditions_summary_with_http_info( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> ApiResponse: """System Terms Conditions Summary # noqa: E501 Get systems terms conditions summary dashboard information. # noqa: E501 diff --git a/src/python_client/emass_client/api/enterprise_vulnerability_dashboards_api.py b/src/python_client/emass_client/api/enterprise_vulnerability_dashboards_api.py index 6f1313db..3526f0b2 100644 --- a/src/python_client/emass_client/api/enterprise_vulnerability_dashboards_api.py +++ b/src/python_client/emass_client/api/enterprise_vulnerability_dashboards_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. @@ -84,7 +84,14 @@ def __init__(self, api_client=None) -> None: self.api_client = api_client @validate_call - def get_system_device_findings_details(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 + def get_system_device_findings_details( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> object: """System Device Findings Details # noqa: E501 Get ssystem device findings details dashboard information. # noqa: E501 @@ -120,7 +127,14 @@ def get_system_device_findings_details(self, org_id : Annotated[StrictInt, Field return self.get_system_device_findings_details_with_http_info(org_id, excludeinherited, page_index, page_size, **kwargs) # noqa: E501 @validate_call - def get_system_device_findings_details_with_http_info(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_system_device_findings_details_with_http_info( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> ApiResponse: """System Device Findings Details # noqa: E501 Get ssystem device findings details dashboard information. # noqa: E501 @@ -255,7 +269,14 @@ def get_system_device_findings_details_with_http_info(self, org_id : Annotated[S _request_auth=_params.get('_request_auth')) @validate_call - def get_system_device_findings_summary(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 + def get_system_device_findings_summary( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> object: """System Device Findings Summary # noqa: E501 Get system device findings summary dashboard information. # noqa: E501 @@ -291,7 +312,14 @@ def get_system_device_findings_summary(self, org_id : Annotated[StrictInt, Field return self.get_system_device_findings_summary_with_http_info(org_id, excludeinherited, page_index, page_size, **kwargs) # noqa: E501 @validate_call - def get_system_device_findings_summary_with_http_info(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_system_device_findings_summary_with_http_info( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> ApiResponse: """System Device Findings Summary # noqa: E501 Get system device findings summary dashboard information. # noqa: E501 @@ -426,7 +454,14 @@ def get_system_device_findings_summary_with_http_info(self, org_id : Annotated[S _request_auth=_params.get('_request_auth')) @validate_call - def get_system_vulnerability_summary(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 + def get_system_vulnerability_summary( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> object: """System Vulnerability Summary # noqa: E501 Get system vulnerability summary dashboard information. # noqa: E501 @@ -462,7 +497,14 @@ def get_system_vulnerability_summary(self, org_id : Annotated[StrictInt, Field(d return self.get_system_vulnerability_summary_with_http_info(org_id, excludeinherited, page_index, page_size, **kwargs) # noqa: E501 @validate_call - def get_system_vulnerability_summary_with_http_info(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_system_vulnerability_summary_with_http_info( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> ApiResponse: """System Vulnerability Summary # noqa: E501 Get system vulnerability summary dashboard information. # noqa: E501 diff --git a/src/python_client/emass_client/api/fisma_inventory_summary_dashboards_api.py b/src/python_client/emass_client/api/fisma_inventory_summary_dashboards_api.py index a0ff7dda..02367b64 100644 --- a/src/python_client/emass_client/api/fisma_inventory_summary_dashboards_api.py +++ b/src/python_client/emass_client/api/fisma_inventory_summary_dashboards_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. @@ -84,7 +84,14 @@ def __init__(self, api_client=None) -> None: self.api_client = api_client @validate_call - def get_va_system_fisma_invetory_crypto_summary(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 + def get_va_system_fisma_invetory_crypto_summary( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> object: """VA System FISMA Inventory Crypto Summary # noqa: E501 Get VA system FISMA inventory crypto summary dashboard information. # noqa: E501 @@ -120,7 +127,14 @@ def get_va_system_fisma_invetory_crypto_summary(self, org_id : Annotated[StrictI return self.get_va_system_fisma_invetory_crypto_summary_with_http_info(org_id, excludeinherited, page_index, page_size, **kwargs) # noqa: E501 @validate_call - def get_va_system_fisma_invetory_crypto_summary_with_http_info(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_va_system_fisma_invetory_crypto_summary_with_http_info( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> ApiResponse: """VA System FISMA Inventory Crypto Summary # noqa: E501 Get VA system FISMA inventory crypto summary dashboard information. # noqa: E501 @@ -255,7 +269,14 @@ def get_va_system_fisma_invetory_crypto_summary_with_http_info(self, org_id : An _request_auth=_params.get('_request_auth')) @validate_call - def get_va_system_fisma_invetory_summary(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 + def get_va_system_fisma_invetory_summary( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> object: """VA System FISMA Inventory Summary # noqa: E501 Get VA system FISMA inventory summary dashboard information. # noqa: E501 @@ -291,7 +312,14 @@ def get_va_system_fisma_invetory_summary(self, org_id : Annotated[StrictInt, Fie return self.get_va_system_fisma_invetory_summary_with_http_info(org_id, excludeinherited, page_index, page_size, **kwargs) # noqa: E501 @validate_call - def get_va_system_fisma_invetory_summary_with_http_info(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_va_system_fisma_invetory_summary_with_http_info( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> ApiResponse: """VA System FISMA Inventory Summary # noqa: E501 Get VA system FISMA inventory summary dashboard information. # noqa: E501 diff --git a/src/python_client/emass_client/api/hardware_baseline_dashboards_api.py b/src/python_client/emass_client/api/hardware_baseline_dashboards_api.py index 092481e9..d43649a0 100644 --- a/src/python_client/emass_client/api/hardware_baseline_dashboards_api.py +++ b/src/python_client/emass_client/api/hardware_baseline_dashboards_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. @@ -84,7 +84,14 @@ def __init__(self, api_client=None) -> None: self.api_client = api_client @validate_call - def get_system_hardware_details(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 + def get_system_hardware_details( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> object: """System Hardware Details # noqa: E501 Get system hardware details dashboard information. # noqa: E501 @@ -120,7 +127,14 @@ def get_system_hardware_details(self, org_id : Annotated[StrictInt, Field(descri return self.get_system_hardware_details_with_http_info(org_id, excludeinherited, page_index, page_size, **kwargs) # noqa: E501 @validate_call - def get_system_hardware_details_with_http_info(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_system_hardware_details_with_http_info( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> ApiResponse: """System Hardware Details # noqa: E501 Get system hardware details dashboard information. # noqa: E501 @@ -255,7 +269,14 @@ def get_system_hardware_details_with_http_info(self, org_id : Annotated[StrictIn _request_auth=_params.get('_request_auth')) @validate_call - def get_system_hardware_summary(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 + def get_system_hardware_summary( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> object: """System Hardware Summary # noqa: E501 Get system hardware summary dashboard information. # noqa: E501 @@ -291,7 +312,14 @@ def get_system_hardware_summary(self, org_id : Annotated[StrictInt, Field(descri return self.get_system_hardware_summary_with_http_info(org_id, excludeinherited, page_index, page_size, **kwargs) # noqa: E501 @validate_call - def get_system_hardware_summary_with_http_info(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_system_hardware_summary_with_http_info( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> ApiResponse: """System Hardware Summary # noqa: E501 Get system hardware summary dashboard information. # noqa: E501 diff --git a/src/python_client/emass_client/api/milestones_api.py b/src/python_client/emass_client/api/milestones_api.py index 13585acd..4c63586f 100644 --- a/src/python_client/emass_client/api/milestones_api.py +++ b/src/python_client/emass_client/api/milestones_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. @@ -91,7 +91,13 @@ def __init__(self, api_client=None) -> None: self.api_client = api_client @validate_call - def add_milestone_by_system_id_and_poam_id(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], poam_id : Annotated[StrictInt, Field(description="**POA&M Id**: The unique POA&M record identifier.")], request_body : Annotated[List[object], Field(description="Add milestones to an existing system poam")], **kwargs) -> MilestoneResponsePost: # noqa: E501 + def add_milestone_by_system_id_and_poam_id( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + poam_id: Annotated[StrictInt, Field(description="**POA&M Id**: The unique POA&M record identifier.")], + request_body: Annotated[List[object], Field(description="Add milestones to an existing system poam")], + **kwargs, + ) -> MilestoneResponsePost: """Add milestones to one or many POA&M items in a system # noqa: E501 Adds a milestone for given `systemId` and `poamId` path parameters **Request Body Required Fields** - `description` - `scheduledCompletionDate` # noqa: E501 @@ -125,7 +131,13 @@ def add_milestone_by_system_id_and_poam_id(self, system_id : Annotated[StrictInt return self.add_milestone_by_system_id_and_poam_id_with_http_info(system_id, poam_id, request_body, **kwargs) # noqa: E501 @validate_call - def add_milestone_by_system_id_and_poam_id_with_http_info(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], poam_id : Annotated[StrictInt, Field(description="**POA&M Id**: The unique POA&M record identifier.")], request_body : Annotated[List[object], Field(description="Add milestones to an existing system poam")], **kwargs) -> ApiResponse: # noqa: E501 + def add_milestone_by_system_id_and_poam_id_with_http_info( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + poam_id: Annotated[StrictInt, Field(description="**POA&M Id**: The unique POA&M record identifier.")], + request_body: Annotated[List[object], Field(description="Add milestones to an existing system poam")], + **kwargs, + ) -> ApiResponse: """Add milestones to one or many POA&M items in a system # noqa: E501 Adds a milestone for given `systemId` and `poamId` path parameters **Request Body Required Fields** - `description` - `scheduledCompletionDate` # noqa: E501 @@ -262,7 +274,13 @@ def add_milestone_by_system_id_and_poam_id_with_http_info(self, system_id : Anno _request_auth=_params.get('_request_auth')) @validate_call - def delete_milestone(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], poam_id : Annotated[StrictInt, Field(description="**POA&M Id**: The unique POA&M record identifier.")], milestones_request_delete_body_inner : Annotated[List[MilestonesRequestDeleteBodyInner], Field(description="Delete the given Milestone Id")], **kwargs) -> MilestoneResponseDelete: # noqa: E501 + def delete_milestone( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + poam_id: Annotated[StrictInt, Field(description="**POA&M Id**: The unique POA&M record identifier.")], + milestones_request_delete_body_inner: Annotated[List[MilestonesRequestDeleteBodyInner], Field(description="Delete the given Milestone Id")], + **kwargs, + ) -> MilestoneResponseDelete: """Remove milestones in a system for one or many POA&M items # noqa: E501 Remove the POA&M matching `systemId` and `poamId` for path parameters and `milstoneId` provide in the Requst Body **Notes**
To delete a milestone the record must be inactive by having the field isActive set to false (`isActive=false`). # noqa: E501 @@ -296,7 +314,13 @@ def delete_milestone(self, system_id : Annotated[StrictInt, Field(description="* return self.delete_milestone_with_http_info(system_id, poam_id, milestones_request_delete_body_inner, **kwargs) # noqa: E501 @validate_call - def delete_milestone_with_http_info(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], poam_id : Annotated[StrictInt, Field(description="**POA&M Id**: The unique POA&M record identifier.")], milestones_request_delete_body_inner : Annotated[List[MilestonesRequestDeleteBodyInner], Field(description="Delete the given Milestone Id")], **kwargs) -> ApiResponse: # noqa: E501 + def delete_milestone_with_http_info( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + poam_id: Annotated[StrictInt, Field(description="**POA&M Id**: The unique POA&M record identifier.")], + milestones_request_delete_body_inner: Annotated[List[MilestonesRequestDeleteBodyInner], Field(description="Delete the given Milestone Id")], + **kwargs, + ) -> ApiResponse: """Remove milestones in a system for one or many POA&M items # noqa: E501 Remove the POA&M matching `systemId` and `poamId` for path parameters and `milstoneId` provide in the Requst Body **Notes**
To delete a milestone the record must be inactive by having the field isActive set to false (`isActive=false`). # noqa: E501 @@ -430,7 +454,14 @@ def delete_milestone_with_http_info(self, system_id : Annotated[StrictInt, Field _request_auth=_params.get('_request_auth')) @validate_call - def get_system_milestones_by_poam_id(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], poam_id : Annotated[StrictInt, Field(description="**POA&M Id**: The unique POA&M record identifier.")], scheduled_completion_date_start : Annotated[Optional[StrictStr], Field(description="**Date Started**: Filter query by the scheduled completion start date (Unix date format).")] = None, scheduled_completion_date_end : Annotated[Optional[StrictStr], Field(description="**Date Ended**: Filter query by the scheduled completion start date (Unix date format).")] = None, **kwargs) -> MilestoneResponseGet: # noqa: E501 + def get_system_milestones_by_poam_id( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + poam_id: Annotated[StrictInt, Field(description="**POA&M Id**: The unique POA&M record identifier.")], + scheduled_completion_date_start: Annotated[Optional[StrictStr], Field(description="**Date Started**: Filter query by the scheduled completion start date (Unix date format).")] = None, + scheduled_completion_date_end: Annotated[Optional[StrictStr], Field(description="**Date Ended**: Filter query by the scheduled completion start date (Unix date format).")] = None, + **kwargs, + ) -> MilestoneResponseGet: """Get milestones in one or many POA&M items in a system # noqa: E501 Returns system containing milestones for matching parameters. # noqa: E501 @@ -466,7 +497,14 @@ def get_system_milestones_by_poam_id(self, system_id : Annotated[StrictInt, Fiel return self.get_system_milestones_by_poam_id_with_http_info(system_id, poam_id, scheduled_completion_date_start, scheduled_completion_date_end, **kwargs) # noqa: E501 @validate_call - def get_system_milestones_by_poam_id_with_http_info(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], poam_id : Annotated[StrictInt, Field(description="**POA&M Id**: The unique POA&M record identifier.")], scheduled_completion_date_start : Annotated[Optional[StrictStr], Field(description="**Date Started**: Filter query by the scheduled completion start date (Unix date format).")] = None, scheduled_completion_date_end : Annotated[Optional[StrictStr], Field(description="**Date Ended**: Filter query by the scheduled completion start date (Unix date format).")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_system_milestones_by_poam_id_with_http_info( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + poam_id: Annotated[StrictInt, Field(description="**POA&M Id**: The unique POA&M record identifier.")], + scheduled_completion_date_start: Annotated[Optional[StrictStr], Field(description="**Date Started**: Filter query by the scheduled completion start date (Unix date format).")] = None, + scheduled_completion_date_end: Annotated[Optional[StrictStr], Field(description="**Date Ended**: Filter query by the scheduled completion start date (Unix date format).")] = None, + **kwargs, + ) -> ApiResponse: """Get milestones in one or many POA&M items in a system # noqa: E501 Returns system containing milestones for matching parameters. # noqa: E501 @@ -601,7 +639,13 @@ def get_system_milestones_by_poam_id_with_http_info(self, system_id : Annotated[ _request_auth=_params.get('_request_auth')) @validate_call - def get_system_milestones_by_poam_id_and_milestone_id(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], poam_id : Annotated[StrictInt, Field(description="**POA&M Id**: The unique POA&M record identifier.")], milestone_id : Annotated[StrictInt, Field(description="**Milestone Id**: The unique milestone record identifier.")], **kwargs) -> MilestoneResponseGetMilestone: # noqa: E501 + def get_system_milestones_by_poam_id_and_milestone_id( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + poam_id: Annotated[StrictInt, Field(description="**POA&M Id**: The unique POA&M record identifier.")], + milestone_id: Annotated[StrictInt, Field(description="**Milestone Id**: The unique milestone record identifier.")], + **kwargs, + ) -> MilestoneResponseGetMilestone: """Get milestone by ID in POA&M item in a system # noqa: E501 Returns systems containing milestones for matching parameters. # noqa: E501 @@ -635,7 +679,13 @@ def get_system_milestones_by_poam_id_and_milestone_id(self, system_id : Annotate return self.get_system_milestones_by_poam_id_and_milestone_id_with_http_info(system_id, poam_id, milestone_id, **kwargs) # noqa: E501 @validate_call - def get_system_milestones_by_poam_id_and_milestone_id_with_http_info(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], poam_id : Annotated[StrictInt, Field(description="**POA&M Id**: The unique POA&M record identifier.")], milestone_id : Annotated[StrictInt, Field(description="**Milestone Id**: The unique milestone record identifier.")], **kwargs) -> ApiResponse: # noqa: E501 + def get_system_milestones_by_poam_id_and_milestone_id_with_http_info( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + poam_id: Annotated[StrictInt, Field(description="**POA&M Id**: The unique POA&M record identifier.")], + milestone_id: Annotated[StrictInt, Field(description="**Milestone Id**: The unique milestone record identifier.")], + **kwargs, + ) -> ApiResponse: """Get milestone by ID in POA&M item in a system # noqa: E501 Returns systems containing milestones for matching parameters. # noqa: E501 @@ -764,7 +814,13 @@ def get_system_milestones_by_poam_id_and_milestone_id_with_http_info(self, syste _request_auth=_params.get('_request_auth')) @validate_call - def update_milestone_by_system_id_and_poam_id(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], poam_id : Annotated[StrictInt, Field(description="**POA&M Id**: The unique POA&M record identifier.")], request_body : Annotated[List[object], Field(description="Update milestones for an existing system poam")], **kwargs) -> MilestoneResponsePut: # noqa: E501 + def update_milestone_by_system_id_and_poam_id( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + poam_id: Annotated[StrictInt, Field(description="**POA&M Id**: The unique POA&M record identifier.")], + request_body: Annotated[List[object], Field(description="Update milestones for an existing system poam")], + **kwargs, + ) -> MilestoneResponsePut: """Update one or many POA&M items in a system # noqa: E501 Updates a milestone for given `systemId` and `poamId` path parameters **Request Body Required Fields** - `milestoneId` - `description` - `scheduledCompletionDate` # noqa: E501 @@ -798,7 +854,13 @@ def update_milestone_by_system_id_and_poam_id(self, system_id : Annotated[Strict return self.update_milestone_by_system_id_and_poam_id_with_http_info(system_id, poam_id, request_body, **kwargs) # noqa: E501 @validate_call - def update_milestone_by_system_id_and_poam_id_with_http_info(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], poam_id : Annotated[StrictInt, Field(description="**POA&M Id**: The unique POA&M record identifier.")], request_body : Annotated[List[object], Field(description="Update milestones for an existing system poam")], **kwargs) -> ApiResponse: # noqa: E501 + def update_milestone_by_system_id_and_poam_id_with_http_info( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + poam_id: Annotated[StrictInt, Field(description="**POA&M Id**: The unique POA&M record identifier.")], + request_body: Annotated[List[object], Field(description="Update milestones for an existing system poam")], + **kwargs, + ) -> ApiResponse: """Update one or many POA&M items in a system # noqa: E501 Updates a milestone for given `systemId` and `poamId` path parameters **Request Body Required Fields** - `milestoneId` - `description` - `scheduledCompletionDate` # noqa: E501 diff --git a/src/python_client/emass_client/api/pac_api.py b/src/python_client/emass_client/api/pac_api.py index 936ec807..4cafdda3 100644 --- a/src/python_client/emass_client/api/pac_api.py +++ b/src/python_client/emass_client/api/pac_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. @@ -87,7 +87,12 @@ def __init__(self, api_client=None) -> None: self.api_client = api_client @validate_call - def add_system_pac(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], request_body : Annotated[List[object], Field(description="Add system package to PAC for review")], **kwargs) -> PacResponsePost: # noqa: E501 + def add_system_pac( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + request_body: Annotated[List[object], Field(description="Add system package to PAC for review")], + **kwargs, + ) -> PacResponsePost: """Initiate system workflow for review # noqa: E501 Adds a Package Approval Chain (PAC) for given `systemId` path parameter **Request Body Required Fields** - `workflow` - `name` - `comments` # noqa: E501 @@ -119,7 +124,12 @@ def add_system_pac(self, system_id : Annotated[StrictInt, Field(description="**S return self.add_system_pac_with_http_info(system_id, request_body, **kwargs) # noqa: E501 @validate_call - def add_system_pac_with_http_info(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], request_body : Annotated[List[object], Field(description="Add system package to PAC for review")], **kwargs) -> ApiResponse: # noqa: E501 + def add_system_pac_with_http_info( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + request_body: Annotated[List[object], Field(description="Add system package to PAC for review")], + **kwargs, + ) -> ApiResponse: """Initiate system workflow for review # noqa: E501 Adds a Package Approval Chain (PAC) for given `systemId` path parameter **Request Body Required Fields** - `workflow` - `name` - `comments` # noqa: E501 @@ -250,7 +260,11 @@ def add_system_pac_with_http_info(self, system_id : Annotated[StrictInt, Field(d _request_auth=_params.get('_request_auth')) @validate_call - def get_system_pac(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], **kwargs) -> PacResponseGet: # noqa: E501 + def get_system_pac( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + **kwargs, + ) -> PacResponseGet: """Get status of active workflows in a system # noqa: E501 Returns the location of a system's package in the Package Approval Chain (PAC) for matching `systemId` path parameter **Notes:** - If the indicated system has any active workflows, the response will include information such as the workflow type and the current stage of each workflow. - If there are no active workflows, then a null data member will be returned. # noqa: E501 @@ -280,7 +294,11 @@ def get_system_pac(self, system_id : Annotated[StrictInt, Field(description="**S return self.get_system_pac_with_http_info(system_id, **kwargs) # noqa: E501 @validate_call - def get_system_pac_with_http_info(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], **kwargs) -> ApiResponse: # noqa: E501 + def get_system_pac_with_http_info( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + **kwargs, + ) -> ApiResponse: """Get status of active workflows in a system # noqa: E501 Returns the location of a system's package in the Package Approval Chain (PAC) for matching `systemId` path parameter **Notes:** - If the indicated system has any active workflows, the response will include information such as the workflow type and the current stage of each workflow. - If there are no active workflows, then a null data member will be returned. # noqa: E501 diff --git a/src/python_client/emass_client/api/poam_api.py b/src/python_client/emass_client/api/poam_api.py index 7c1b7a1b..d91cc373 100644 --- a/src/python_client/emass_client/api/poam_api.py +++ b/src/python_client/emass_client/api/poam_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. @@ -91,7 +91,12 @@ def __init__(self, api_client=None) -> None: self.api_client = api_client @validate_call - def add_poam_by_system_id(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], request_body : Annotated[List[object], Field(description="Add POA&M(s) to a system (systemID)")], **kwargs) -> PoamResponsePost: # noqa: E501 + def add_poam_by_system_id( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + request_body: Annotated[List[object], Field(description="Add POA&M(s) to a system (systemID)")], + **kwargs, + ) -> PoamResponsePost: """Add one or many POA&M items in a system # noqa: E501 Add a POA&M for given `systemId`
**Request Body Required Fields** - `status` - `vulnerabilityDescription` - `sourceIdentVuln` - `pocOrganization` - `resources` **Note**
If a POC email is supplied, the application will attempt to locate a user already registered within the application and pre-populate any information not explicitly supplied in the request. If no such user is found, these fields are **required** within the request.
`pocFirstName`, `pocLastName`, `pocPhoneNumber`
# noqa: E501 @@ -123,7 +128,12 @@ def add_poam_by_system_id(self, system_id : Annotated[StrictInt, Field(descripti return self.add_poam_by_system_id_with_http_info(system_id, request_body, **kwargs) # noqa: E501 @validate_call - def add_poam_by_system_id_with_http_info(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], request_body : Annotated[List[object], Field(description="Add POA&M(s) to a system (systemID)")], **kwargs) -> ApiResponse: # noqa: E501 + def add_poam_by_system_id_with_http_info( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + request_body: Annotated[List[object], Field(description="Add POA&M(s) to a system (systemID)")], + **kwargs, + ) -> ApiResponse: """Add one or many POA&M items in a system # noqa: E501 Add a POA&M for given `systemId`
**Request Body Required Fields** - `status` - `vulnerabilityDescription` - `sourceIdentVuln` - `pocOrganization` - `resources` **Note**
If a POC email is supplied, the application will attempt to locate a user already registered within the application and pre-populate any information not explicitly supplied in the request. If no such user is found, these fields are **required** within the request.
`pocFirstName`, `pocLastName`, `pocPhoneNumber`
# noqa: E501 @@ -254,7 +264,12 @@ def add_poam_by_system_id_with_http_info(self, system_id : Annotated[StrictInt, _request_auth=_params.get('_request_auth')) @validate_call - def delete_poam(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], poam_request_delete_body_inner : Annotated[List[PoamRequestDeleteBodyInner], Field(description="Delete the given POA&M Id")], **kwargs) -> PoamResponseDelete: # noqa: E501 + def delete_poam( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + poam_request_delete_body_inner: Annotated[List[PoamRequestDeleteBodyInner], Field(description="Delete the given POA&M Id")], + **kwargs, + ) -> PoamResponseDelete: """Remove one or many POA&M items in a system # noqa: E501 Remove the POA&M matching `systemId` path parameter and `poamId` Request Body
# noqa: E501 @@ -286,7 +301,12 @@ def delete_poam(self, system_id : Annotated[StrictInt, Field(description="**Syst return self.delete_poam_with_http_info(system_id, poam_request_delete_body_inner, **kwargs) # noqa: E501 @validate_call - def delete_poam_with_http_info(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], poam_request_delete_body_inner : Annotated[List[PoamRequestDeleteBodyInner], Field(description="Delete the given POA&M Id")], **kwargs) -> ApiResponse: # noqa: E501 + def delete_poam_with_http_info( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + poam_request_delete_body_inner: Annotated[List[PoamRequestDeleteBodyInner], Field(description="Delete the given POA&M Id")], + **kwargs, + ) -> ApiResponse: """Remove one or many POA&M items in a system # noqa: E501 Remove the POA&M matching `systemId` path parameter and `poamId` Request Body
# noqa: E501 @@ -414,7 +434,17 @@ def delete_poam_with_http_info(self, system_id : Annotated[StrictInt, Field(desc _request_auth=_params.get('_request_auth')) @validate_call - def get_system_poams(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], scheduled_completion_date_start : Annotated[Optional[StrictStr], Field(description="**Date Started**: Filter query by the scheduled completion start date (Unix date format).")] = None, scheduled_completion_date_end : Annotated[Optional[StrictStr], Field(description="**Date Ended**: Filter query by the scheduled completion start date (Unix date format).")] = None, control_acronyms : Annotated[Optional[StrictStr], Field(description="**Control Acronym**: Filter query by given system acronym (single value or comma separated).")] = None, assessment_procedures : Annotated[Optional[StrictStr], Field(description="**Assessment Procedure**: Filter query by given Security Control Assessment Procedure (single value or comma separated).")] = None, ccis : Annotated[Optional[StrictStr], Field(description="**CCI System**: Filter query by Control Correlation Identifiers (CCIs) (single value or comma separated).")] = None, system_only : Annotated[Optional[StrictBool], Field(description="**Systems Only**: Indicates that only system(s) information is retrieved.")] = None, **kwargs) -> PoamResponseGetSystems: # noqa: E501 + def get_system_poams( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + scheduled_completion_date_start: Annotated[Optional[StrictStr], Field(description="**Date Started**: Filter query by the scheduled completion start date (Unix date format).")] = None, + scheduled_completion_date_end: Annotated[Optional[StrictStr], Field(description="**Date Ended**: Filter query by the scheduled completion start date (Unix date format).")] = None, + control_acronyms: Annotated[Optional[StrictStr], Field(description="**Control Acronym**: Filter query by given system acronym (single value or comma separated).")] = None, + assessment_procedures: Annotated[Optional[StrictStr], Field(description="**Assessment Procedure**: Filter query by given Security Control Assessment Procedure (single value or comma separated).")] = None, + ccis: Annotated[Optional[StrictStr], Field(description="**CCI System**: Filter query by Control Correlation Identifiers (CCIs) (single value or comma separated).")] = None, + system_only: Annotated[Optional[StrictBool], Field(description="**Systems Only**: Indicates that only system(s) information is retrieved.")] = None, + **kwargs, + ) -> PoamResponseGetSystems: """Get one or many POA&M items in a system # noqa: E501 Returns system(s) containing POA&M items for matching parameters. # noqa: E501 @@ -456,7 +486,17 @@ def get_system_poams(self, system_id : Annotated[StrictInt, Field(description="* return self.get_system_poams_with_http_info(system_id, scheduled_completion_date_start, scheduled_completion_date_end, control_acronyms, assessment_procedures, ccis, system_only, **kwargs) # noqa: E501 @validate_call - def get_system_poams_with_http_info(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], scheduled_completion_date_start : Annotated[Optional[StrictStr], Field(description="**Date Started**: Filter query by the scheduled completion start date (Unix date format).")] = None, scheduled_completion_date_end : Annotated[Optional[StrictStr], Field(description="**Date Ended**: Filter query by the scheduled completion start date (Unix date format).")] = None, control_acronyms : Annotated[Optional[StrictStr], Field(description="**Control Acronym**: Filter query by given system acronym (single value or comma separated).")] = None, assessment_procedures : Annotated[Optional[StrictStr], Field(description="**Assessment Procedure**: Filter query by given Security Control Assessment Procedure (single value or comma separated).")] = None, ccis : Annotated[Optional[StrictStr], Field(description="**CCI System**: Filter query by Control Correlation Identifiers (CCIs) (single value or comma separated).")] = None, system_only : Annotated[Optional[StrictBool], Field(description="**Systems Only**: Indicates that only system(s) information is retrieved.")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_system_poams_with_http_info( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + scheduled_completion_date_start: Annotated[Optional[StrictStr], Field(description="**Date Started**: Filter query by the scheduled completion start date (Unix date format).")] = None, + scheduled_completion_date_end: Annotated[Optional[StrictStr], Field(description="**Date Ended**: Filter query by the scheduled completion start date (Unix date format).")] = None, + control_acronyms: Annotated[Optional[StrictStr], Field(description="**Control Acronym**: Filter query by given system acronym (single value or comma separated).")] = None, + assessment_procedures: Annotated[Optional[StrictStr], Field(description="**Assessment Procedure**: Filter query by given Security Control Assessment Procedure (single value or comma separated).")] = None, + ccis: Annotated[Optional[StrictStr], Field(description="**CCI System**: Filter query by Control Correlation Identifiers (CCIs) (single value or comma separated).")] = None, + system_only: Annotated[Optional[StrictBool], Field(description="**Systems Only**: Indicates that only system(s) information is retrieved.")] = None, + **kwargs, + ) -> ApiResponse: """Get one or many POA&M items in a system # noqa: E501 Returns system(s) containing POA&M items for matching parameters. # noqa: E501 @@ -609,7 +649,12 @@ def get_system_poams_with_http_info(self, system_id : Annotated[StrictInt, Field _request_auth=_params.get('_request_auth')) @validate_call - def get_system_poams_by_poam_id(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], poam_id : Annotated[StrictInt, Field(description="**POA&M Id**: The unique POA&M record identifier.")], **kwargs) -> PoamResponseGetPoams: # noqa: E501 + def get_system_poams_by_poam_id( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + poam_id: Annotated[StrictInt, Field(description="**POA&M Id**: The unique POA&M record identifier.")], + **kwargs, + ) -> PoamResponseGetPoams: """Get POA&M item by ID in a system # noqa: E501 Returns system(s) containing POA&M items for matching parameters. # noqa: E501 @@ -641,7 +686,12 @@ def get_system_poams_by_poam_id(self, system_id : Annotated[StrictInt, Field(des return self.get_system_poams_by_poam_id_with_http_info(system_id, poam_id, **kwargs) # noqa: E501 @validate_call - def get_system_poams_by_poam_id_with_http_info(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], poam_id : Annotated[StrictInt, Field(description="**POA&M Id**: The unique POA&M record identifier.")], **kwargs) -> ApiResponse: # noqa: E501 + def get_system_poams_by_poam_id_with_http_info( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + poam_id: Annotated[StrictInt, Field(description="**POA&M Id**: The unique POA&M record identifier.")], + **kwargs, + ) -> ApiResponse: """Get POA&M item by ID in a system # noqa: E501 Returns system(s) containing POA&M items for matching parameters. # noqa: E501 @@ -764,7 +814,12 @@ def get_system_poams_by_poam_id_with_http_info(self, system_id : Annotated[Stric _request_auth=_params.get('_request_auth')) @validate_call - def update_poam_by_system_id(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], request_body : Annotated[List[object], Field(description="Update an existing control by Id")], **kwargs) -> PoamResponsePut: # noqa: E501 + def update_poam_by_system_id( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + request_body: Annotated[List[object], Field(description="Update an existing control by Id")], + **kwargs, + ) -> PoamResponsePut: """Update one or many POA&M items in a system # noqa: E501 Update a POA&M for given `systemId`
**Request Body Required Fields** - `poamId` - `displayPoamId` - `status` - `vulnerabilityDescription` - `sourceIdentVuln` - `pocOrganization` - `reviewStatus` **Notes** - If a POC email is supplied, the application will attempt to locate a user already registered within the application and pre-populate any information not explicitly supplied in the request. If no such user is found, these fields are **required** within the request.
`pocOrganization`, `pocFirstName`, `pocLastName`, `pocEmail`, `pocPhoneNumber`
- To prevent uploading duplicate/undesired milestones through the POA&M PUT we must include an `isActive` field for the milestone and set it to equal to false `(isActive=false)`. # noqa: E501 @@ -796,7 +851,12 @@ def update_poam_by_system_id(self, system_id : Annotated[StrictInt, Field(descri return self.update_poam_by_system_id_with_http_info(system_id, request_body, **kwargs) # noqa: E501 @validate_call - def update_poam_by_system_id_with_http_info(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], request_body : Annotated[List[object], Field(description="Update an existing control by Id")], **kwargs) -> ApiResponse: # noqa: E501 + def update_poam_by_system_id_with_http_info( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + request_body: Annotated[List[object], Field(description="Update an existing control by Id")], + **kwargs, + ) -> ApiResponse: """Update one or many POA&M items in a system # noqa: E501 Update a POA&M for given `systemId`
**Request Body Required Fields** - `poamId` - `displayPoamId` - `status` - `vulnerabilityDescription` - `sourceIdentVuln` - `pocOrganization` - `reviewStatus` **Notes** - If a POC email is supplied, the application will attempt to locate a user already registered within the application and pre-populate any information not explicitly supplied in the request. If no such user is found, these fields are **required** within the request.
`pocOrganization`, `pocFirstName`, `pocLastName`, `pocEmail`, `pocPhoneNumber`
- To prevent uploading duplicate/undesired milestones through the POA&M PUT we must include an `isActive` field for the milestone and set it to equal to false `(isActive=false)`. # noqa: E501 diff --git a/src/python_client/emass_client/api/ports_and_protocols_dashboards_api.py b/src/python_client/emass_client/api/ports_and_protocols_dashboards_api.py index 5eafa9a6..40be74b2 100644 --- a/src/python_client/emass_client/api/ports_and_protocols_dashboards_api.py +++ b/src/python_client/emass_client/api/ports_and_protocols_dashboards_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. @@ -84,7 +84,14 @@ def __init__(self, api_client=None) -> None: self.api_client = api_client @validate_call - def get_system_ports_protocols_details(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 + def get_system_ports_protocols_details( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> object: """System Ports/Protocols Details # noqa: E501 Get system ports and protocols details dashboard information. # noqa: E501 @@ -120,7 +127,14 @@ def get_system_ports_protocols_details(self, org_id : Annotated[StrictInt, Field return self.get_system_ports_protocols_details_with_http_info(org_id, excludeinherited, page_index, page_size, **kwargs) # noqa: E501 @validate_call - def get_system_ports_protocols_details_with_http_info(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_system_ports_protocols_details_with_http_info( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> ApiResponse: """System Ports/Protocols Details # noqa: E501 Get system ports and protocols details dashboard information. # noqa: E501 @@ -255,7 +269,14 @@ def get_system_ports_protocols_details_with_http_info(self, org_id : Annotated[S _request_auth=_params.get('_request_auth')) @validate_call - def get_system_ports_protocols_summary(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 + def get_system_ports_protocols_summary( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> object: """System Ports/Protocols Summary # noqa: E501 Get system ports and protocols summary dashboard information. # noqa: E501 @@ -291,7 +312,14 @@ def get_system_ports_protocols_summary(self, org_id : Annotated[StrictInt, Field return self.get_system_ports_protocols_summary_with_http_info(org_id, excludeinherited, page_index, page_size, **kwargs) # noqa: E501 @validate_call - def get_system_ports_protocols_summary_with_http_info(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_system_ports_protocols_summary_with_http_info( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> ApiResponse: """System Ports/Protocols Summary # noqa: E501 Get system ports and protocols summary dashboard information. # noqa: E501 diff --git a/src/python_client/emass_client/api/privacy_compliance_dashboards_api.py b/src/python_client/emass_client/api/privacy_compliance_dashboards_api.py index b09a5a39..f2132d7c 100644 --- a/src/python_client/emass_client/api/privacy_compliance_dashboards_api.py +++ b/src/python_client/emass_client/api/privacy_compliance_dashboards_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. @@ -84,7 +84,14 @@ def __init__(self, api_client=None) -> None: self.api_client = api_client @validate_call - def get_system_privacy_summary(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 + def get_system_privacy_summary( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> object: """System Privacy Summary # noqa: E501 Get user system privacy summary dashboard information. # noqa: E501 @@ -120,7 +127,14 @@ def get_system_privacy_summary(self, org_id : Annotated[StrictInt, Field(descrip return self.get_system_privacy_summary_with_http_info(org_id, excludeinherited, page_index, page_size, **kwargs) # noqa: E501 @validate_call - def get_system_privacy_summary_with_http_info(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_system_privacy_summary_with_http_info( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> ApiResponse: """System Privacy Summary # noqa: E501 Get user system privacy summary dashboard information. # noqa: E501 @@ -255,7 +269,14 @@ def get_system_privacy_summary_with_http_info(self, org_id : Annotated[StrictInt _request_auth=_params.get('_request_auth')) @validate_call - def get_va_omb_fsma_saop_summary(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 + def get_va_omb_fsma_saop_summary( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> object: """VA OMB FISMA SAOP Summary # noqa: E501 Get VA OMB-FISMA SAOP summary dashboard information. # noqa: E501 @@ -291,7 +312,14 @@ def get_va_omb_fsma_saop_summary(self, org_id : Annotated[StrictInt, Field(descr return self.get_va_omb_fsma_saop_summary_with_http_info(org_id, excludeinherited, page_index, page_size, **kwargs) # noqa: E501 @validate_call - def get_va_omb_fsma_saop_summary_with_http_info(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_va_omb_fsma_saop_summary_with_http_info( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> ApiResponse: """VA OMB FISMA SAOP Summary # noqa: E501 Get VA OMB-FISMA SAOP summary dashboard information. # noqa: E501 diff --git a/src/python_client/emass_client/api/registration_api.py b/src/python_client/emass_client/api/registration_api.py index 2ac22305..3af0c1b5 100644 --- a/src/python_client/emass_client/api/registration_api.py +++ b/src/python_client/emass_client/api/registration_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. @@ -79,7 +79,10 @@ def __init__(self, api_client=None) -> None: self.api_client = api_client @validate_call - def register_user(self, **kwargs) -> Register: # noqa: E501 + def register_user( + self, + **kwargs, + ) -> Register: """Register user certificate and obtain an API key # noqa: E501 Returns the API Key (api-key) that must be provided in the request header for all endpoint calls. # noqa: E501 @@ -107,7 +110,10 @@ def register_user(self, **kwargs) -> Register: # noqa: E501 return self.register_user_with_http_info(**kwargs) # noqa: E501 @validate_call - def register_user_with_http_info(self, **kwargs) -> ApiResponse: # noqa: E501 + def register_user_with_http_info( + self, + **kwargs, + ) -> ApiResponse: """Register user certificate and obtain an API key # noqa: E501 Returns the API Key (api-key) that must be provided in the request header for all endpoint calls. # noqa: E501 diff --git a/src/python_client/emass_client/api/software_baseline_dashboards_api.py b/src/python_client/emass_client/api/software_baseline_dashboards_api.py index 5018b866..c851f76c 100644 --- a/src/python_client/emass_client/api/software_baseline_dashboards_api.py +++ b/src/python_client/emass_client/api/software_baseline_dashboards_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. @@ -84,7 +84,14 @@ def __init__(self, api_client=None) -> None: self.api_client = api_client @validate_call - def get_system_software_details(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 + def get_system_software_details( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> object: """System Software Details # noqa: E501 Get system software details dashboard information. # noqa: E501 @@ -120,7 +127,14 @@ def get_system_software_details(self, org_id : Annotated[StrictInt, Field(descri return self.get_system_software_details_with_http_info(org_id, excludeinherited, page_index, page_size, **kwargs) # noqa: E501 @validate_call - def get_system_software_details_with_http_info(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_system_software_details_with_http_info( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> ApiResponse: """System Software Details # noqa: E501 Get system software details dashboard information. # noqa: E501 @@ -255,7 +269,14 @@ def get_system_software_details_with_http_info(self, org_id : Annotated[StrictIn _request_auth=_params.get('_request_auth')) @validate_call - def get_system_software_summary(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 + def get_system_software_summary( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> object: """System Software Summary # noqa: E501 Get system software summary dashboard information. # noqa: E501 @@ -291,7 +312,14 @@ def get_system_software_summary(self, org_id : Annotated[StrictInt, Field(descri return self.get_system_software_summary_with_http_info(org_id, excludeinherited, page_index, page_size, **kwargs) # noqa: E501 @validate_call - def get_system_software_summary_with_http_info(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_system_software_summary_with_http_info( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> ApiResponse: """System Software Summary # noqa: E501 Get system software summary dashboard information. # noqa: E501 diff --git a/src/python_client/emass_client/api/static_code_scans_api.py b/src/python_client/emass_client/api/static_code_scans_api.py index df393bf0..a448555c 100644 --- a/src/python_client/emass_client/api/static_code_scans_api.py +++ b/src/python_client/emass_client/api/static_code_scans_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. @@ -84,7 +84,12 @@ def __init__(self, api_client=None) -> None: self.api_client = api_client @validate_call - def add_static_code_scans_by_system_id(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], static_code_request_post_body : Annotated[StaticCodeRequestPostBody, Field(description="Add static code scans or Clear static code scans")], **kwargs) -> StaticCodeResponsePost: # noqa: E501 + def add_static_code_scans_by_system_id( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + static_code_request_post_body: Annotated[StaticCodeRequestPostBody, Field(description="Add static code scans or Clear static code scans")], + **kwargs, + ) -> StaticCodeResponsePost: """Upload static code scans or Clear static code scans # noqa: E501 Upload or clear application scan findings into a system's `systemId` assets module. **Request Body Required Fields** - Application Object (`application`) - `applicationName` - `version` - Application Findings Object Array (`applicationFindings`) - `codeCheckName` - `count` - `scanDate` - `cweId` **Note:** To clear an application's findings, use only the field `clearFindings` as the Request body and set it to true. Example: ``` [ { \"application\": { \"applicationName\": \"application name\", \"version\": \"application version\" }, \"applicationFindings\": [ { \"clearFindings\": true } ] } ] ``` # noqa: E501 @@ -116,7 +121,12 @@ def add_static_code_scans_by_system_id(self, system_id : Annotated[StrictInt, Fi return self.add_static_code_scans_by_system_id_with_http_info(system_id, static_code_request_post_body, **kwargs) # noqa: E501 @validate_call - def add_static_code_scans_by_system_id_with_http_info(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], static_code_request_post_body : Annotated[StaticCodeRequestPostBody, Field(description="Add static code scans or Clear static code scans")], **kwargs) -> ApiResponse: # noqa: E501 + def add_static_code_scans_by_system_id_with_http_info( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + static_code_request_post_body: Annotated[StaticCodeRequestPostBody, Field(description="Add static code scans or Clear static code scans")], + **kwargs, + ) -> ApiResponse: """Upload static code scans or Clear static code scans # noqa: E501 Upload or clear application scan findings into a system's `systemId` assets module. **Request Body Required Fields** - Application Object (`application`) - `applicationName` - `version` - Application Findings Object Array (`applicationFindings`) - `codeCheckName` - `count` - `scanDate` - `cweId` **Note:** To clear an application's findings, use only the field `clearFindings` as the Request body and set it to true. Example: ``` [ { \"application\": { \"applicationName\": \"application name\", \"version\": \"application version\" }, \"applicationFindings\": [ { \"clearFindings\": true } ] } ] ``` # noqa: E501 diff --git a/src/python_client/emass_client/api/system_a20_summary_dashboard_api.py b/src/python_client/emass_client/api/system_a20_summary_dashboard_api.py index 827bb80d..bab74e55 100644 --- a/src/python_client/emass_client/api/system_a20_summary_dashboard_api.py +++ b/src/python_client/emass_client/api/system_a20_summary_dashboard_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. @@ -84,7 +84,14 @@ def __init__(self, api_client=None) -> None: self.api_client = api_client @validate_call - def get_va_system_a2_summary(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 + def get_va_system_a2_summary( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> object: """VA System A2.0 Summary # noqa: E501 Get VA system A2.0 summary dashboard information. # noqa: E501 @@ -120,7 +127,14 @@ def get_va_system_a2_summary(self, org_id : Annotated[StrictInt, Field(descripti return self.get_va_system_a2_summary_with_http_info(org_id, excludeinherited, page_index, page_size, **kwargs) # noqa: E501 @validate_call - def get_va_system_a2_summary_with_http_info(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_va_system_a2_summary_with_http_info( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> ApiResponse: """VA System A2.0 Summary # noqa: E501 Get VA system A2.0 summary dashboard information. # noqa: E501 diff --git a/src/python_client/emass_client/api/system_aa_summary_dashboard_api.py b/src/python_client/emass_client/api/system_aa_summary_dashboard_api.py index b8410674..47646426 100644 --- a/src/python_client/emass_client/api/system_aa_summary_dashboard_api.py +++ b/src/python_client/emass_client/api/system_aa_summary_dashboard_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. @@ -84,7 +84,14 @@ def __init__(self, api_client=None) -> None: self.api_client = api_client @validate_call - def get_va_system_aa_summary(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 + def get_va_system_aa_summary( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> object: """VA System A&A Summary # noqa: E501 Get VA system A&A summary dashboard information. # noqa: E501 @@ -120,7 +127,14 @@ def get_va_system_aa_summary(self, org_id : Annotated[StrictInt, Field(descripti return self.get_va_system_aa_summary_with_http_info(org_id, excludeinherited, page_index, page_size, **kwargs) # noqa: E501 @validate_call - def get_va_system_aa_summary_with_http_info(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_va_system_aa_summary_with_http_info( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> ApiResponse: """VA System A&A Summary # noqa: E501 Get VA system A&A summary dashboard information. # noqa: E501 diff --git a/src/python_client/emass_client/api/system_associations_dashboard_api.py b/src/python_client/emass_client/api/system_associations_dashboard_api.py index d5dcef1d..d198ee04 100644 --- a/src/python_client/emass_client/api/system_associations_dashboard_api.py +++ b/src/python_client/emass_client/api/system_associations_dashboard_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. @@ -84,7 +84,14 @@ def __init__(self, api_client=None) -> None: self.api_client = api_client @validate_call - def get_system_associations_details(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 + def get_system_associations_details( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> object: """System Associations Details # noqa: E501 Get system associations details dashboard information. # noqa: E501 @@ -120,7 +127,14 @@ def get_system_associations_details(self, org_id : Annotated[StrictInt, Field(de return self.get_system_associations_details_with_http_info(org_id, excludeinherited, page_index, page_size, **kwargs) # noqa: E501 @validate_call - def get_system_associations_details_with_http_info(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_system_associations_details_with_http_info( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> ApiResponse: """System Associations Details # noqa: E501 Get system associations details dashboard information. # noqa: E501 diff --git a/src/python_client/emass_client/api/system_conmon_integration_status_dashboard_api.py b/src/python_client/emass_client/api/system_conmon_integration_status_dashboard_api.py index 9732fb0b..d348eedd 100644 --- a/src/python_client/emass_client/api/system_conmon_integration_status_dashboard_api.py +++ b/src/python_client/emass_client/api/system_conmon_integration_status_dashboard_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. @@ -84,7 +84,14 @@ def __init__(self, api_client=None) -> None: self.api_client = api_client @validate_call - def get_system_common_integration_status_summary(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 + def get_system_common_integration_status_summary( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> object: """System CONMON Integration Status # noqa: E501 Get system CONMON integration status dashboard information. # noqa: E501 @@ -120,7 +127,14 @@ def get_system_common_integration_status_summary(self, org_id : Annotated[Strict return self.get_system_common_integration_status_summary_with_http_info(org_id, excludeinherited, page_index, page_size, **kwargs) # noqa: E501 @validate_call - def get_system_common_integration_status_summary_with_http_info(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_system_common_integration_status_summary_with_http_info( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> ApiResponse: """System CONMON Integration Status # noqa: E501 Get system CONMON integration status dashboard information. # noqa: E501 diff --git a/src/python_client/emass_client/api/system_pl109_reporting_summary_dashboard_api.py b/src/python_client/emass_client/api/system_pl109_reporting_summary_dashboard_api.py index 3d23c190..379e2fdc 100644 --- a/src/python_client/emass_client/api/system_pl109_reporting_summary_dashboard_api.py +++ b/src/python_client/emass_client/api/system_pl109_reporting_summary_dashboard_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. @@ -84,7 +84,14 @@ def __init__(self, api_client=None) -> None: self.api_client = api_client @validate_call - def get_va_system_pl109_reporting_summary(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 + def get_va_system_pl109_reporting_summary( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> object: """VA System P.L. 109 Reporting Summary # noqa: E501 Get VA system P.L. 109 reporting summary dashboard information. # noqa: E501 @@ -120,7 +127,14 @@ def get_va_system_pl109_reporting_summary(self, org_id : Annotated[StrictInt, Fi return self.get_va_system_pl109_reporting_summary_with_http_info(org_id, excludeinherited, page_index, page_size, **kwargs) # noqa: E501 @validate_call - def get_va_system_pl109_reporting_summary_with_http_info(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_va_system_pl109_reporting_summary_with_http_info( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> ApiResponse: """VA System P.L. 109 Reporting Summary # noqa: E501 Get VA system P.L. 109 reporting summary dashboard information. # noqa: E501 diff --git a/src/python_client/emass_client/api/system_roles_api.py b/src/python_client/emass_client/api/system_roles_api.py index 86d712d6..06904fee 100644 --- a/src/python_client/emass_client/api/system_roles_api.py +++ b/src/python_client/emass_client/api/system_roles_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. @@ -86,7 +86,10 @@ def __init__(self, api_client=None) -> None: self.api_client = api_client @validate_call - def get_system_roles(self, **kwargs) -> SystemRolesResponse: # noqa: E501 + def get_system_roles( + self, + **kwargs, + ) -> SystemRolesResponse: """Get available roles # noqa: E501 Returns all available roles # noqa: E501 @@ -114,7 +117,10 @@ def get_system_roles(self, **kwargs) -> SystemRolesResponse: # noqa: E501 return self.get_system_roles_with_http_info(**kwargs) # noqa: E501 @validate_call - def get_system_roles_with_http_info(self, **kwargs) -> ApiResponse: # noqa: E501 + def get_system_roles_with_http_info( + self, + **kwargs, + ) -> ApiResponse: """Get available roles # noqa: E501 Returns all available roles # noqa: E501 @@ -225,7 +231,13 @@ def get_system_roles_with_http_info(self, **kwargs) -> ApiResponse: # noqa: E50 _request_auth=_params.get('_request_auth')) @validate_call - def get_system_roles_by_category_id(self, role_category : Annotated[StrictStr, Field(description="**Role Category**: The system role category been queried")], role : Annotated[StrictStr, Field(description="**Role**: Accepts single value from options available at base system-roles endpoint e.g., SCA.")], policy : Annotated[Optional[StrictStr], Field(description="**System Policy**: Filter query by system policy. If no value is specified, the default returns RMF policy information for dual-policy systems.")] = None, **kwargs) -> SystemRolesCategoryResponse: # noqa: E501 + def get_system_roles_by_category_id( + self, + role_category: Annotated[StrictStr, Field(description="**Role Category**: The system role category been queried")], + role: Annotated[StrictStr, Field(description="**Role**: Accepts single value from options available at base system-roles endpoint e.g., SCA.")], + policy: Annotated[Optional[StrictStr], Field(description="**System Policy**: Filter query by system policy. If no value is specified, the default returns RMF policy information for dual-policy systems.")] = None, + **kwargs, + ) -> SystemRolesCategoryResponse: """Get system roles # noqa: E501 Returns the role(s) data matching parameters. # noqa: E501 @@ -259,7 +271,13 @@ def get_system_roles_by_category_id(self, role_category : Annotated[StrictStr, F return self.get_system_roles_by_category_id_with_http_info(role_category, role, policy, **kwargs) # noqa: E501 @validate_call - def get_system_roles_by_category_id_with_http_info(self, role_category : Annotated[StrictStr, Field(description="**Role Category**: The system role category been queried")], role : Annotated[StrictStr, Field(description="**Role**: Accepts single value from options available at base system-roles endpoint e.g., SCA.")], policy : Annotated[Optional[StrictStr], Field(description="**System Policy**: Filter query by system policy. If no value is specified, the default returns RMF policy information for dual-policy systems.")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_system_roles_by_category_id_with_http_info( + self, + role_category: Annotated[StrictStr, Field(description="**Role Category**: The system role category been queried")], + role: Annotated[StrictStr, Field(description="**Role**: Accepts single value from options available at base system-roles endpoint e.g., SCA.")], + policy: Annotated[Optional[StrictStr], Field(description="**System Policy**: Filter query by system policy. If no value is specified, the default returns RMF policy information for dual-policy systems.")] = None, + **kwargs, + ) -> ApiResponse: """Get system roles # noqa: E501 Returns the role(s) data matching parameters. # noqa: E501 diff --git a/src/python_client/emass_client/api/system_status_dashboard_api.py b/src/python_client/emass_client/api/system_status_dashboard_api.py index 759369cd..25b89802 100644 --- a/src/python_client/emass_client/api/system_status_dashboard_api.py +++ b/src/python_client/emass_client/api/system_status_dashboard_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. @@ -84,7 +84,14 @@ def __init__(self, api_client=None) -> None: self.api_client = api_client @validate_call - def get_system_status_details(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 + def get_system_status_details( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> object: """System Status Details # noqa: E501 Get systems status detail dashboard information. # noqa: E501 @@ -120,7 +127,14 @@ def get_system_status_details(self, org_id : Annotated[StrictInt, Field(descript return self.get_system_status_details_with_http_info(org_id, excludeinherited, page_index, page_size, **kwargs) # noqa: E501 @validate_call - def get_system_status_details_with_http_info(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_system_status_details_with_http_info( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> ApiResponse: """System Status Details # noqa: E501 Get systems status detail dashboard information. # noqa: E501 diff --git a/src/python_client/emass_client/api/systems_api.py b/src/python_client/emass_client/api/systems_api.py index dac981ed..30ebb3a0 100644 --- a/src/python_client/emass_client/api/systems_api.py +++ b/src/python_client/emass_client/api/systems_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. @@ -86,7 +86,13 @@ def __init__(self, api_client=None) -> None: self.api_client = api_client @validate_call - def get_system(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], include_package : Annotated[Optional[StrictBool], Field(description="**Include Package**: Indicates if additional packages information are retrieved for queried system. If no value is specified, the default returns false to not include package information")] = None, policy : Annotated[Optional[StrictStr], Field(description="**System Policy**: Filter query by system policy. If no value is specified, the default returns RMF policy information for dual-policy systems.")] = None, **kwargs) -> SystemResponse: # noqa: E501 + def get_system( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + include_package: Annotated[Optional[StrictBool], Field(description="**Include Package**: Indicates if additional packages information are retrieved for queried system. If no value is specified, the default returns false to not include package information")] = None, + policy: Annotated[Optional[StrictStr], Field(description="**System Policy**: Filter query by system policy. If no value is specified, the default returns RMF policy information for dual-policy systems.")] = None, + **kwargs, + ) -> SystemResponse: """Get system information for a specific system # noqa: E501 Returns the system matching provided parameters # noqa: E501 @@ -120,7 +126,13 @@ def get_system(self, system_id : Annotated[StrictInt, Field(description="**Syste return self.get_system_with_http_info(system_id, include_package, policy, **kwargs) # noqa: E501 @validate_call - def get_system_with_http_info(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], include_package : Annotated[Optional[StrictBool], Field(description="**Include Package**: Indicates if additional packages information are retrieved for queried system. If no value is specified, the default returns false to not include package information")] = None, policy : Annotated[Optional[StrictStr], Field(description="**System Policy**: Filter query by system policy. If no value is specified, the default returns RMF policy information for dual-policy systems.")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_system_with_http_info( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + include_package: Annotated[Optional[StrictBool], Field(description="**Include Package**: Indicates if additional packages information are retrieved for queried system. If no value is specified, the default returns false to not include package information")] = None, + policy: Annotated[Optional[StrictStr], Field(description="**System Policy**: Filter query by system policy. If no value is specified, the default returns RMF policy information for dual-policy systems.")] = None, + **kwargs, + ) -> ApiResponse: """Get system information for a specific system # noqa: E501 Returns the system matching provided parameters # noqa: E501 @@ -249,7 +261,18 @@ def get_system_with_http_info(self, system_id : Annotated[StrictInt, Field(descr _request_auth=_params.get('_request_auth')) @validate_call - def get_systems(self, coams_id : Annotated[Optional[StrictStr], Field(description="**COAMS ID**: Filter query by Cyber Operational Attributes Management System (COAMS).")] = None, ditpr_id : Annotated[Optional[StrictStr], Field(description="**DITPR ID**: Filter query by DoD Information Technology (IT) Portfolio Repository (DITPR).")] = None, include_decommissioned : Annotated[Optional[StrictBool], Field(description="**Include Decommissioned Systems**: Indicates if decommissioned systems are retrieved. If no value is specified, the default returns true to include decommissioned systems.")] = None, include_ditpr_metrics : Annotated[Optional[StrictBool], Field(description="**Include DITPR**: Indicates if DITPR metrics are retrieved. This query string parameter cannot be used in conjunction with the following parameters: - includePackage - ditprId - coamsId If no value is specified, the default returns false to not include DITPR Metrics.")] = None, include_package : Annotated[Optional[StrictBool], Field(description="**Include Package**: Indicates if additional packages information are retrieved for queried system. If no value is specified, the default returns false to not include package information")] = None, policy : Annotated[Optional[StrictStr], Field(description="**System Policy**: Filter query by system policy. If no value is specified, the default returns RMF policy information for dual-policy systems.")] = None, registration_type : Annotated[Optional[StrictStr], Field(description="**Registration Type**: Filter record by selected registration type (single value or comma delimited values). *Available values:* assessAndAuthorize, assessOnly, guest, regular, functional, cloudServiceProvider, commonControlProvider ")] = None, reports_for_scorecard : Annotated[Optional[StrictBool], Field(description="**DoD Cyber Hygiene Scorecard**: Used to filter results to only return systems that report to the DoD Cyber Hygiene Scorecard.")] = None, **kwargs) -> SystemsResponse: # noqa: E501 + def get_systems( + self, + coams_id: Annotated[Optional[StrictStr], Field(description="**COAMS ID**: Filter query by Cyber Operational Attributes Management System (COAMS).")] = None, + ditpr_id: Annotated[Optional[StrictStr], Field(description="**DITPR ID**: Filter query by DoD Information Technology (IT) Portfolio Repository (DITPR).")] = None, + include_decommissioned: Annotated[Optional[StrictBool], Field(description="**Include Decommissioned Systems**: Indicates if decommissioned systems are retrieved. If no value is specified, the default returns true to include decommissioned systems.")] = None, + include_ditpr_metrics: Annotated[Optional[StrictBool], Field(description="**Include DITPR**: Indicates if DITPR metrics are retrieved. This query string parameter cannot be used in conjunction with the following parameters: - includePackage - ditprId - coamsId If no value is specified, the default returns false to not include DITPR Metrics.")] = None, + include_package: Annotated[Optional[StrictBool], Field(description="**Include Package**: Indicates if additional packages information are retrieved for queried system. If no value is specified, the default returns false to not include package information")] = None, + policy: Annotated[Optional[StrictStr], Field(description="**System Policy**: Filter query by system policy. If no value is specified, the default returns RMF policy information for dual-policy systems.")] = None, + registration_type: Annotated[Optional[StrictStr], Field(description="**Registration Type**: Filter record by selected registration type (single value or comma delimited values). *Available values:* assessAndAuthorize, assessOnly, guest, regular, functional, cloudServiceProvider, commonControlProvider ")] = None, + reports_for_scorecard: Annotated[Optional[StrictBool], Field(description="**DoD Cyber Hygiene Scorecard**: Used to filter results to only return systems that report to the DoD Cyber Hygiene Scorecard.")] = None, + **kwargs, + ) -> SystemsResponse: """Get system information # noqa: E501 Returns all system(s) that match the query parameters # noqa: E501 @@ -293,7 +316,18 @@ def get_systems(self, coams_id : Annotated[Optional[StrictStr], Field(descriptio return self.get_systems_with_http_info(coams_id, ditpr_id, include_decommissioned, include_ditpr_metrics, include_package, policy, registration_type, reports_for_scorecard, **kwargs) # noqa: E501 @validate_call - def get_systems_with_http_info(self, coams_id : Annotated[Optional[StrictStr], Field(description="**COAMS ID**: Filter query by Cyber Operational Attributes Management System (COAMS).")] = None, ditpr_id : Annotated[Optional[StrictStr], Field(description="**DITPR ID**: Filter query by DoD Information Technology (IT) Portfolio Repository (DITPR).")] = None, include_decommissioned : Annotated[Optional[StrictBool], Field(description="**Include Decommissioned Systems**: Indicates if decommissioned systems are retrieved. If no value is specified, the default returns true to include decommissioned systems.")] = None, include_ditpr_metrics : Annotated[Optional[StrictBool], Field(description="**Include DITPR**: Indicates if DITPR metrics are retrieved. This query string parameter cannot be used in conjunction with the following parameters: - includePackage - ditprId - coamsId If no value is specified, the default returns false to not include DITPR Metrics.")] = None, include_package : Annotated[Optional[StrictBool], Field(description="**Include Package**: Indicates if additional packages information are retrieved for queried system. If no value is specified, the default returns false to not include package information")] = None, policy : Annotated[Optional[StrictStr], Field(description="**System Policy**: Filter query by system policy. If no value is specified, the default returns RMF policy information for dual-policy systems.")] = None, registration_type : Annotated[Optional[StrictStr], Field(description="**Registration Type**: Filter record by selected registration type (single value or comma delimited values). *Available values:* assessAndAuthorize, assessOnly, guest, regular, functional, cloudServiceProvider, commonControlProvider ")] = None, reports_for_scorecard : Annotated[Optional[StrictBool], Field(description="**DoD Cyber Hygiene Scorecard**: Used to filter results to only return systems that report to the DoD Cyber Hygiene Scorecard.")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_systems_with_http_info( + self, + coams_id: Annotated[Optional[StrictStr], Field(description="**COAMS ID**: Filter query by Cyber Operational Attributes Management System (COAMS).")] = None, + ditpr_id: Annotated[Optional[StrictStr], Field(description="**DITPR ID**: Filter query by DoD Information Technology (IT) Portfolio Repository (DITPR).")] = None, + include_decommissioned: Annotated[Optional[StrictBool], Field(description="**Include Decommissioned Systems**: Indicates if decommissioned systems are retrieved. If no value is specified, the default returns true to include decommissioned systems.")] = None, + include_ditpr_metrics: Annotated[Optional[StrictBool], Field(description="**Include DITPR**: Indicates if DITPR metrics are retrieved. This query string parameter cannot be used in conjunction with the following parameters: - includePackage - ditprId - coamsId If no value is specified, the default returns false to not include DITPR Metrics.")] = None, + include_package: Annotated[Optional[StrictBool], Field(description="**Include Package**: Indicates if additional packages information are retrieved for queried system. If no value is specified, the default returns false to not include package information")] = None, + policy: Annotated[Optional[StrictStr], Field(description="**System Policy**: Filter query by system policy. If no value is specified, the default returns RMF policy information for dual-policy systems.")] = None, + registration_type: Annotated[Optional[StrictStr], Field(description="**Registration Type**: Filter record by selected registration type (single value or comma delimited values). *Available values:* assessAndAuthorize, assessOnly, guest, regular, functional, cloudServiceProvider, commonControlProvider ")] = None, + reports_for_scorecard: Annotated[Optional[StrictBool], Field(description="**DoD Cyber Hygiene Scorecard**: Used to filter results to only return systems that report to the DoD Cyber Hygiene Scorecard.")] = None, + **kwargs, + ) -> ApiResponse: """Get system information # noqa: E501 Returns all system(s) that match the query parameters # noqa: E501 diff --git a/src/python_client/emass_client/api/test_api.py b/src/python_client/emass_client/api/test_api.py index 26db03e9..baeab6fe 100644 --- a/src/python_client/emass_client/api/test_api.py +++ b/src/python_client/emass_client/api/test_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. @@ -79,7 +79,10 @@ def __init__(self, api_client=None) -> None: self.api_client = api_client @validate_call - def test_connection(self, **kwargs) -> Test: # noqa: E501 + def test_connection( + self, + **kwargs, + ) -> Test: """Test connection to the API # noqa: E501 Tests the endpoint connection # noqa: E501 @@ -107,7 +110,10 @@ def test_connection(self, **kwargs) -> Test: # noqa: E501 return self.test_connection_with_http_info(**kwargs) # noqa: E501 @validate_call - def test_connection_with_http_info(self, **kwargs) -> ApiResponse: # noqa: E501 + def test_connection_with_http_info( + self, + **kwargs, + ) -> ApiResponse: """Test connection to the API # noqa: E501 Tests the endpoint connection # noqa: E501 diff --git a/src/python_client/emass_client/api/test_results_api.py b/src/python_client/emass_client/api/test_results_api.py index b1012a52..b168ced4 100644 --- a/src/python_client/emass_client/api/test_results_api.py +++ b/src/python_client/emass_client/api/test_results_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. @@ -87,7 +87,12 @@ def __init__(self, api_client=None) -> None: self.api_client = api_client @validate_call - def add_test_results_by_system_id(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], request_body : Annotated[List[object], Field(description="Add test results to a system (systemId)")], **kwargs) -> TestResultsResponsePost: # noqa: E501 + def add_test_results_by_system_id( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + request_body: Annotated[List[object], Field(description="Add test results to a system (systemId)")], + **kwargs, + ) -> TestResultsResponsePost: """Add one or many test results in a system # noqa: E501 Adds test results for given `systemId` **Request Body Required Fields** - `testedBy` - `testDate` - `description` - `complianceStatus` - `assessmentProcedure` # noqa: E501 @@ -119,7 +124,12 @@ def add_test_results_by_system_id(self, system_id : Annotated[StrictInt, Field(d return self.add_test_results_by_system_id_with_http_info(system_id, request_body, **kwargs) # noqa: E501 @validate_call - def add_test_results_by_system_id_with_http_info(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], request_body : Annotated[List[object], Field(description="Add test results to a system (systemId)")], **kwargs) -> ApiResponse: # noqa: E501 + def add_test_results_by_system_id_with_http_info( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + request_body: Annotated[List[object], Field(description="Add test results to a system (systemId)")], + **kwargs, + ) -> ApiResponse: """Add one or many test results in a system # noqa: E501 Adds test results for given `systemId` **Request Body Required Fields** - `testedBy` - `testDate` - `description` - `complianceStatus` - `assessmentProcedure` # noqa: E501 @@ -250,7 +260,15 @@ def add_test_results_by_system_id_with_http_info(self, system_id : Annotated[Str _request_auth=_params.get('_request_auth')) @validate_call - def get_system_test_results(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], control_acronyms : Annotated[Optional[StrictStr], Field(description="**Control Acronym**: Filter query by given system acronym (single value or comma separated).")] = None, assessment_procedures : Annotated[Optional[StrictStr], Field(description="**Assessment Procedure**: Filter query by given Security Control Assessment Procedure (single value or comma separated).")] = None, ccis : Annotated[Optional[StrictStr], Field(description="**CCI System**: Filter query by Control Correlation Identifiers (CCIs) (single value or comma separated).")] = None, latest_only : Annotated[Optional[StrictBool], Field(description="**Latest Results Only**: Indicates that only the latest test resultes are retrieved.")] = None, **kwargs) -> TestResultsResponseGet: # noqa: E501 + def get_system_test_results( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + control_acronyms: Annotated[Optional[StrictStr], Field(description="**Control Acronym**: Filter query by given system acronym (single value or comma separated).")] = None, + assessment_procedures: Annotated[Optional[StrictStr], Field(description="**Assessment Procedure**: Filter query by given Security Control Assessment Procedure (single value or comma separated).")] = None, + ccis: Annotated[Optional[StrictStr], Field(description="**CCI System**: Filter query by Control Correlation Identifiers (CCIs) (single value or comma separated).")] = None, + latest_only: Annotated[Optional[StrictBool], Field(description="**Latest Results Only**: Indicates that only the latest test resultes are retrieved.")] = None, + **kwargs, + ) -> TestResultsResponseGet: """Get one or many test results in a system # noqa: E501 Returns system test results information for matching parameters.
# noqa: E501 @@ -288,7 +306,15 @@ def get_system_test_results(self, system_id : Annotated[StrictInt, Field(descrip return self.get_system_test_results_with_http_info(system_id, control_acronyms, assessment_procedures, ccis, latest_only, **kwargs) # noqa: E501 @validate_call - def get_system_test_results_with_http_info(self, system_id : Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], control_acronyms : Annotated[Optional[StrictStr], Field(description="**Control Acronym**: Filter query by given system acronym (single value or comma separated).")] = None, assessment_procedures : Annotated[Optional[StrictStr], Field(description="**Assessment Procedure**: Filter query by given Security Control Assessment Procedure (single value or comma separated).")] = None, ccis : Annotated[Optional[StrictStr], Field(description="**CCI System**: Filter query by Control Correlation Identifiers (CCIs) (single value or comma separated).")] = None, latest_only : Annotated[Optional[StrictBool], Field(description="**Latest Results Only**: Indicates that only the latest test resultes are retrieved.")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_system_test_results_with_http_info( + self, + system_id: Annotated[StrictInt, Field(description="**System Id**: The unique system record identifier.")], + control_acronyms: Annotated[Optional[StrictStr], Field(description="**Control Acronym**: Filter query by given system acronym (single value or comma separated).")] = None, + assessment_procedures: Annotated[Optional[StrictStr], Field(description="**Assessment Procedure**: Filter query by given Security Control Assessment Procedure (single value or comma separated).")] = None, + ccis: Annotated[Optional[StrictStr], Field(description="**CCI System**: Filter query by Control Correlation Identifiers (CCIs) (single value or comma separated).")] = None, + latest_only: Annotated[Optional[StrictBool], Field(description="**Latest Results Only**: Indicates that only the latest test resultes are retrieved.")] = None, + **kwargs, + ) -> ApiResponse: """Get one or many test results in a system # noqa: E501 Returns system test results information for matching parameters.
# noqa: E501 diff --git a/src/python_client/emass_client/api/threat_risks_dashboards_api.py b/src/python_client/emass_client/api/threat_risks_dashboards_api.py index c853c322..05c848ce 100644 --- a/src/python_client/emass_client/api/threat_risks_dashboards_api.py +++ b/src/python_client/emass_client/api/threat_risks_dashboards_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. @@ -84,7 +84,14 @@ def __init__(self, api_client=None) -> None: self.api_client = api_client @validate_call - def get_va_system_threat_architecture_details(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 + def get_va_system_threat_architecture_details( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> object: """VA System Threat Architecture Details # noqa: E501 Get VA system threat architecture details dashboard information. # noqa: E501 @@ -120,7 +127,14 @@ def get_va_system_threat_architecture_details(self, org_id : Annotated[StrictInt return self.get_va_system_threat_architecture_details_with_http_info(org_id, excludeinherited, page_index, page_size, **kwargs) # noqa: E501 @validate_call - def get_va_system_threat_architecture_details_with_http_info(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_va_system_threat_architecture_details_with_http_info( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> ApiResponse: """VA System Threat Architecture Details # noqa: E501 Get VA system threat architecture details dashboard information. # noqa: E501 @@ -255,7 +269,14 @@ def get_va_system_threat_architecture_details_with_http_info(self, org_id : Anno _request_auth=_params.get('_request_auth')) @validate_call - def get_va_system_threat_risk_summary(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 + def get_va_system_threat_risk_summary( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> object: """VA System Threat Risks Summary # noqa: E501 Get VA system threat risk summary dashboard information. # noqa: E501 @@ -291,7 +312,14 @@ def get_va_system_threat_risk_summary(self, org_id : Annotated[StrictInt, Field( return self.get_va_system_threat_risk_summary_with_http_info(org_id, excludeinherited, page_index, page_size, **kwargs) # noqa: E501 @validate_call - def get_va_system_threat_risk_summary_with_http_info(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_va_system_threat_risk_summary_with_http_info( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> ApiResponse: """VA System Threat Risks Summary # noqa: E501 Get VA system threat risk summary dashboard information. # noqa: E501 @@ -426,7 +454,14 @@ def get_va_system_threat_risk_summary_with_http_info(self, org_id : Annotated[St _request_auth=_params.get('_request_auth')) @validate_call - def get_va_system_threat_source_details(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 + def get_va_system_threat_source_details( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> object: """VA System Threat Sources Details # noqa: E501 Get VA system threat source details dashboard information. # noqa: E501 @@ -462,7 +497,14 @@ def get_va_system_threat_source_details(self, org_id : Annotated[StrictInt, Fiel return self.get_va_system_threat_source_details_with_http_info(org_id, excludeinherited, page_index, page_size, **kwargs) # noqa: E501 @validate_call - def get_va_system_threat_source_details_with_http_info(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_va_system_threat_source_details_with_http_info( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> ApiResponse: """VA System Threat Sources Details # noqa: E501 Get VA system threat source details dashboard information. # noqa: E501 diff --git a/src/python_client/emass_client/api/users_dashboard_api.py b/src/python_client/emass_client/api/users_dashboard_api.py index 7b37eb52..322b8274 100644 --- a/src/python_client/emass_client/api/users_dashboard_api.py +++ b/src/python_client/emass_client/api/users_dashboard_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. @@ -84,7 +84,14 @@ def __init__(self, api_client=None) -> None: self.api_client = api_client @validate_call - def get_user_system_assignments_details(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> object: # noqa: E501 + def get_user_system_assignments_details( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> object: """User System Assignments Details # noqa: E501 Get user system assignments details dashboard information. # noqa: E501 @@ -120,7 +127,14 @@ def get_user_system_assignments_details(self, org_id : Annotated[StrictInt, Fiel return self.get_user_system_assignments_details_with_http_info(org_id, excludeinherited, page_index, page_size, **kwargs) # noqa: E501 @validate_call - def get_user_system_assignments_details_with_http_info(self, org_id : Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], excludeinherited : Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, page_size : Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_user_system_assignments_details_with_http_info( + self, + org_id: Annotated[StrictInt, Field(description="**Organization Id**: The unique organization identifier.")], + excludeinherited: Annotated[Optional[StrictBool], Field(description="**Exclude Inherited**: If no value is specified, the default returns false to include inherited data. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**Page Index**: If no value is specified, the default returns results from the first page with an index of 0. ")] = None, + page_size: Annotated[Optional[StrictInt], Field(description="**Page Size**: If no value is specified, the default returns 20000 per page. ")] = None, + **kwargs, + ) -> ApiResponse: """User System Assignments Details # noqa: E501 Get user system assignments details dashboard information. # noqa: E501 diff --git a/src/python_client/emass_client/api/workflow_definitions_api.py b/src/python_client/emass_client/api/workflow_definitions_api.py index feeb1c38..32b050bd 100644 --- a/src/python_client/emass_client/api/workflow_definitions_api.py +++ b/src/python_client/emass_client/api/workflow_definitions_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. @@ -85,7 +85,12 @@ def __init__(self, api_client=None) -> None: self.api_client = api_client @validate_call - def get_workflow_definitions(self, include_inactive : Annotated[Optional[StrictBool], Field(description="**Include Inactive**: If no value is specified, the default returns false to not include outdated workflow definitions.")] = None, registration_type : Annotated[Optional[StrictStr], Field(description="**Registration Type**: Filter record by selected registration type (single value or comma delimited values). *Available values:* assessAndAuthorize, assessOnly, guest, regular, functional, cloudServiceProvider, commonControlProvider ")] = None, **kwargs) -> WorkflowDefinitionResponseGet: # noqa: E501 + def get_workflow_definitions( + self, + include_inactive: Annotated[Optional[StrictBool], Field(description="**Include Inactive**: If no value is specified, the default returns false to not include outdated workflow definitions.")] = None, + registration_type: Annotated[Optional[StrictStr], Field(description="**Registration Type**: Filter record by selected registration type (single value or comma delimited values). *Available values:* assessAndAuthorize, assessOnly, guest, regular, functional, cloudServiceProvider, commonControlProvider ")] = None, + **kwargs, + ) -> WorkflowDefinitionResponseGet: """Get workflow definitions in a site # noqa: E501 View all workflow schemas available on the eMASS instance filtered by status `includeInactive` and registration type `registrationType`. # noqa: E501 @@ -117,7 +122,12 @@ def get_workflow_definitions(self, include_inactive : Annotated[Optional[StrictB return self.get_workflow_definitions_with_http_info(include_inactive, registration_type, **kwargs) # noqa: E501 @validate_call - def get_workflow_definitions_with_http_info(self, include_inactive : Annotated[Optional[StrictBool], Field(description="**Include Inactive**: If no value is specified, the default returns false to not include outdated workflow definitions.")] = None, registration_type : Annotated[Optional[StrictStr], Field(description="**Registration Type**: Filter record by selected registration type (single value or comma delimited values). *Available values:* assessAndAuthorize, assessOnly, guest, regular, functional, cloudServiceProvider, commonControlProvider ")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_workflow_definitions_with_http_info( + self, + include_inactive: Annotated[Optional[StrictBool], Field(description="**Include Inactive**: If no value is specified, the default returns false to not include outdated workflow definitions.")] = None, + registration_type: Annotated[Optional[StrictStr], Field(description="**Registration Type**: Filter record by selected registration type (single value or comma delimited values). *Available values:* assessAndAuthorize, assessOnly, guest, regular, functional, cloudServiceProvider, commonControlProvider ")] = None, + **kwargs, + ) -> ApiResponse: """Get workflow definitions in a site # noqa: E501 View all workflow schemas available on the eMASS instance filtered by status `includeInactive` and registration type `registrationType`. # noqa: E501 diff --git a/src/python_client/emass_client/api/workflow_instances_api.py b/src/python_client/emass_client/api/workflow_instances_api.py index 66591f09..c8d842de 100644 --- a/src/python_client/emass_client/api/workflow_instances_api.py +++ b/src/python_client/emass_client/api/workflow_instances_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. @@ -86,7 +86,15 @@ def __init__(self, api_client=None) -> None: self.api_client = api_client @validate_call - def get_system_workflow_instances(self, include_comments : Annotated[Optional[StrictBool], Field(description="**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. ")] = None, include_decommission_systems : Annotated[Optional[StrictBool], Field(description="**Include Decommission Systems**: If no value is specified, the default returns false to exclude decommissioned systems. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**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. ")] = None, since_date : Annotated[Optional[StrictStr], Field(description="**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. ")] = None, status : Annotated[Optional[StrictStr], Field(description="**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. ")] = None, **kwargs) -> WorkflowInstancesResponseGet: # noqa: E501 + def get_system_workflow_instances( + self, + include_comments: Annotated[Optional[StrictBool], Field(description="**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. ")] = None, + include_decommission_systems: Annotated[Optional[StrictBool], Field(description="**Include Decommission Systems**: If no value is specified, the default returns false to exclude decommissioned systems. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**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. ")] = None, + since_date: Annotated[Optional[StrictStr], Field(description="**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. ")] = None, + status: Annotated[Optional[StrictStr], Field(description="**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. ")] = None, + **kwargs, + ) -> WorkflowInstancesResponseGet: """Get workflow instances in a site # noqa: E501 View detailed information on all active and historical workflows filtered by provided parameters. # noqa: E501 @@ -124,7 +132,15 @@ def get_system_workflow_instances(self, include_comments : Annotated[Optional[St return self.get_system_workflow_instances_with_http_info(include_comments, include_decommission_systems, page_index, since_date, status, **kwargs) # noqa: E501 @validate_call - def get_system_workflow_instances_with_http_info(self, include_comments : Annotated[Optional[StrictBool], Field(description="**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. ")] = None, include_decommission_systems : Annotated[Optional[StrictBool], Field(description="**Include Decommission Systems**: If no value is specified, the default returns false to exclude decommissioned systems. ")] = None, page_index : Annotated[Optional[StrictInt], Field(description="**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. ")] = None, since_date : Annotated[Optional[StrictStr], Field(description="**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. ")] = None, status : Annotated[Optional[StrictStr], Field(description="**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. ")] = None, **kwargs) -> ApiResponse: # noqa: E501 + def get_system_workflow_instances_with_http_info( + self, + include_comments: Annotated[Optional[StrictBool], Field(description="**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. ")] = None, + include_decommission_systems: Annotated[Optional[StrictBool], Field(description="**Include Decommission Systems**: If no value is specified, the default returns false to exclude decommissioned systems. ")] = None, + page_index: Annotated[Optional[StrictInt], Field(description="**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. ")] = None, + since_date: Annotated[Optional[StrictStr], Field(description="**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. ")] = None, + status: Annotated[Optional[StrictStr], Field(description="**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. ")] = None, + **kwargs, + ) -> ApiResponse: """Get workflow instances in a site # noqa: E501 View detailed information on all active and historical workflows filtered by provided parameters. # noqa: E501 @@ -265,7 +281,11 @@ def get_system_workflow_instances_with_http_info(self, include_comments : Annota _request_auth=_params.get('_request_auth')) @validate_call - def get_system_workflow_instances_by_workflow_instance_id(self, workflow_instance_id : Annotated[StrictInt, Field(description="**Workflow Instance Id**: The unique workflow definition identifier.")], **kwargs) -> WorkflowInstanceResponseGet: # noqa: E501 + def get_system_workflow_instances_by_workflow_instance_id( + self, + workflow_instance_id: Annotated[StrictInt, Field(description="**Workflow Instance Id**: The unique workflow definition identifier.")], + **kwargs, + ) -> WorkflowInstanceResponseGet: """Get workflow instance by ID # noqa: E501 View detailed historical workflow information for `workflowInstanceId`. # noqa: E501 @@ -295,7 +315,11 @@ def get_system_workflow_instances_by_workflow_instance_id(self, workflow_instanc return self.get_system_workflow_instances_by_workflow_instance_id_with_http_info(workflow_instance_id, **kwargs) # noqa: E501 @validate_call - def get_system_workflow_instances_by_workflow_instance_id_with_http_info(self, workflow_instance_id : Annotated[StrictInt, Field(description="**Workflow Instance Id**: The unique workflow definition identifier.")], **kwargs) -> ApiResponse: # noqa: E501 + def get_system_workflow_instances_by_workflow_instance_id_with_http_info( + self, + workflow_instance_id: Annotated[StrictInt, Field(description="**Workflow Instance Id**: The unique workflow definition identifier.")], + **kwargs, + ) -> ApiResponse: """Get workflow instance by ID # noqa: E501 View detailed historical workflow information for `workflowInstanceId`. # noqa: E501 diff --git a/src/python_client/emass_client/api_client.py b/src/python_client/emass_client/api_client.py index 8c3db3ee..35f4de6d 100644 --- a/src/python_client/emass_client/api_client.py +++ b/src/python_client/emass_client/api_client.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. @@ -113,7 +113,7 @@ def __init__(self, configuration=None, header_name=None, header_value=None, self.default_headers[header_name] = header_value self.cookie = cookie # Set default User-Agent. - self.user_agent = 'OpenAPI-Generator/3.11.1/python' + self.user_agent = 'OpenAPI-Generator/3.12.0/python' self.client_side_validation = configuration.client_side_validation def __enter__(self): diff --git a/src/python_client/emass_client/configuration.py b/src/python_client/emass_client/configuration.py index 13d2f43c..9d962b13 100644 --- a/src/python_client/emass_client/configuration.py +++ b/src/python_client/emass_client/configuration.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. @@ -452,7 +452,7 @@ def to_debug_report(self): "OS: {env}\n"\ "Python Version: {pyversion}\n"\ "Version of the API: v3.12\n"\ - "SDK Package Version: 3.11.1".\ + "SDK Package Version: 3.12.0".\ format(env=sys.platform, pyversion=sys.version) def get_host_settings(self): diff --git a/src/python_client/emass_client/exceptions.py b/src/python_client/emass_client/exceptions.py index f80b9aba..1f547c8d 100644 --- a/src/python_client/emass_client/exceptions.py +++ b/src/python_client/emass_client/exceptions.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/__init__.py b/src/python_client/emass_client/models/__init__.py index a59f2011..e1861940 100644 --- a/src/python_client/emass_client/models/__init__.py +++ b/src/python_client/emass_client/models/__init__.py @@ -10,8 +10,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/artifacts_get.py b/src/python_client/emass_client/models/artifacts_get.py index 7279a3c6..9771fb19 100644 --- a/src/python_client/emass_client/models/artifacts_get.py +++ b/src/python_client/emass_client/models/artifacts_get.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/artifacts_request_delete_body_inner.py b/src/python_client/emass_client/models/artifacts_request_delete_body_inner.py index d291d487..5810af66 100644 --- a/src/python_client/emass_client/models/artifacts_request_delete_body_inner.py +++ b/src/python_client/emass_client/models/artifacts_request_delete_body_inner.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/artifacts_response_del.py b/src/python_client/emass_client/models/artifacts_response_del.py index e785021e..0d5e84a8 100644 --- a/src/python_client/emass_client/models/artifacts_response_del.py +++ b/src/python_client/emass_client/models/artifacts_response_del.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/artifacts_response_del_data_inner.py b/src/python_client/emass_client/models/artifacts_response_del_data_inner.py index 04091ac7..a9c2a45b 100644 --- a/src/python_client/emass_client/models/artifacts_response_del_data_inner.py +++ b/src/python_client/emass_client/models/artifacts_response_del_data_inner.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/artifacts_response_get.py b/src/python_client/emass_client/models/artifacts_response_get.py index 51ccfccb..f938db81 100644 --- a/src/python_client/emass_client/models/artifacts_response_get.py +++ b/src/python_client/emass_client/models/artifacts_response_get.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/artifacts_response_put_post.py b/src/python_client/emass_client/models/artifacts_response_put_post.py index 04791cca..2d49d56e 100644 --- a/src/python_client/emass_client/models/artifacts_response_put_post.py +++ b/src/python_client/emass_client/models/artifacts_response_put_post.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/artifacts_response_put_post_data_inner.py b/src/python_client/emass_client/models/artifacts_response_put_post_data_inner.py index 29c5bb2d..b5562f8c 100644 --- a/src/python_client/emass_client/models/artifacts_response_put_post_data_inner.py +++ b/src/python_client/emass_client/models/artifacts_response_put_post_data_inner.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/cac_get.py b/src/python_client/emass_client/models/cac_get.py index 762cd1d5..885046ef 100644 --- a/src/python_client/emass_client/models/cac_get.py +++ b/src/python_client/emass_client/models/cac_get.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/cac_response_get.py b/src/python_client/emass_client/models/cac_response_get.py index f23d57e7..721e7313 100644 --- a/src/python_client/emass_client/models/cac_response_get.py +++ b/src/python_client/emass_client/models/cac_response_get.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/cac_response_post.py b/src/python_client/emass_client/models/cac_response_post.py index 64e3b63b..ce367e82 100644 --- a/src/python_client/emass_client/models/cac_response_post.py +++ b/src/python_client/emass_client/models/cac_response_post.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/cac_response_post_data_inner.py b/src/python_client/emass_client/models/cac_response_post_data_inner.py index 71b7664c..b358fbe5 100644 --- a/src/python_client/emass_client/models/cac_response_post_data_inner.py +++ b/src/python_client/emass_client/models/cac_response_post_data_inner.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/cloud_resources_delete.py b/src/python_client/emass_client/models/cloud_resources_delete.py index 8ebaf705..48b04907 100644 --- a/src/python_client/emass_client/models/cloud_resources_delete.py +++ b/src/python_client/emass_client/models/cloud_resources_delete.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/cloud_resources_delete_body_inner.py b/src/python_client/emass_client/models/cloud_resources_delete_body_inner.py index 35b34f56..3e01e37e 100644 --- a/src/python_client/emass_client/models/cloud_resources_delete_body_inner.py +++ b/src/python_client/emass_client/models/cloud_resources_delete_body_inner.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/cloud_resources_post_delete.py b/src/python_client/emass_client/models/cloud_resources_post_delete.py index 5a8574ad..5f8474ab 100644 --- a/src/python_client/emass_client/models/cloud_resources_post_delete.py +++ b/src/python_client/emass_client/models/cloud_resources_post_delete.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/cloud_resources_response_post.py b/src/python_client/emass_client/models/cloud_resources_response_post.py index 4e7cf0de..89bd60c6 100644 --- a/src/python_client/emass_client/models/cloud_resources_response_post.py +++ b/src/python_client/emass_client/models/cloud_resources_response_post.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/cmmc_get.py b/src/python_client/emass_client/models/cmmc_get.py index dd20f3a5..0ae69a3d 100644 --- a/src/python_client/emass_client/models/cmmc_get.py +++ b/src/python_client/emass_client/models/cmmc_get.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/cmmc_response_get.py b/src/python_client/emass_client/models/cmmc_response_get.py index 7491f365..5b796c90 100644 --- a/src/python_client/emass_client/models/cmmc_response_get.py +++ b/src/python_client/emass_client/models/cmmc_response_get.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/connectivity_ccsd.py b/src/python_client/emass_client/models/connectivity_ccsd.py index f1a5018b..23d72d80 100644 --- a/src/python_client/emass_client/models/connectivity_ccsd.py +++ b/src/python_client/emass_client/models/connectivity_ccsd.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/container_resources_delete_body_inner.py b/src/python_client/emass_client/models/container_resources_delete_body_inner.py index f3735e79..36341ff9 100644 --- a/src/python_client/emass_client/models/container_resources_delete_body_inner.py +++ b/src/python_client/emass_client/models/container_resources_delete_body_inner.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/containers_resources_post_delete.py b/src/python_client/emass_client/models/containers_resources_post_delete.py index f5951975..6b6ba611 100644 --- a/src/python_client/emass_client/models/containers_resources_post_delete.py +++ b/src/python_client/emass_client/models/containers_resources_post_delete.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/containers_response_delete.py b/src/python_client/emass_client/models/containers_response_delete.py index 85918707..ce97d325 100644 --- a/src/python_client/emass_client/models/containers_response_delete.py +++ b/src/python_client/emass_client/models/containers_response_delete.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/containers_response_post.py b/src/python_client/emass_client/models/containers_response_post.py index 2ae0a81c..6e40246d 100644 --- a/src/python_client/emass_client/models/containers_response_post.py +++ b/src/python_client/emass_client/models/containers_response_post.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/controls_get.py b/src/python_client/emass_client/models/controls_get.py index 71a87d96..7d1691ec 100644 --- a/src/python_client/emass_client/models/controls_get.py +++ b/src/python_client/emass_client/models/controls_get.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/controls_put.py b/src/python_client/emass_client/models/controls_put.py index 5973ac71..3b7c788f 100644 --- a/src/python_client/emass_client/models/controls_put.py +++ b/src/python_client/emass_client/models/controls_put.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/controls_response_get.py b/src/python_client/emass_client/models/controls_response_get.py index 585b0adf..522eacf8 100644 --- a/src/python_client/emass_client/models/controls_response_get.py +++ b/src/python_client/emass_client/models/controls_response_get.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/controls_response_put.py b/src/python_client/emass_client/models/controls_response_put.py index a96ac96c..07048a23 100644 --- a/src/python_client/emass_client/models/controls_response_put.py +++ b/src/python_client/emass_client/models/controls_response_put.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/dashboard_mock_response.py b/src/python_client/emass_client/models/dashboard_mock_response.py index 14ddb12b..a5b7dc0b 100644 --- a/src/python_client/emass_client/models/dashboard_mock_response.py +++ b/src/python_client/emass_client/models/dashboard_mock_response.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/dashboard_mock_response_pagination.py b/src/python_client/emass_client/models/dashboard_mock_response_pagination.py index b51b42d2..8a6aafe8 100644 --- a/src/python_client/emass_client/models/dashboard_mock_response_pagination.py +++ b/src/python_client/emass_client/models/dashboard_mock_response_pagination.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/definition_transitions.py b/src/python_client/emass_client/models/definition_transitions.py index 9f703a99..719fccad 100644 --- a/src/python_client/emass_client/models/definition_transitions.py +++ b/src/python_client/emass_client/models/definition_transitions.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/instances_transitions.py b/src/python_client/emass_client/models/instances_transitions.py index a744500f..6554c5ba 100644 --- a/src/python_client/emass_client/models/instances_transitions.py +++ b/src/python_client/emass_client/models/instances_transitions.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/milestone_response_delete.py b/src/python_client/emass_client/models/milestone_response_delete.py index 92dad9ec..2ec44ea1 100644 --- a/src/python_client/emass_client/models/milestone_response_delete.py +++ b/src/python_client/emass_client/models/milestone_response_delete.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/milestone_response_get.py b/src/python_client/emass_client/models/milestone_response_get.py index 7a2f597f..9c797efa 100644 --- a/src/python_client/emass_client/models/milestone_response_get.py +++ b/src/python_client/emass_client/models/milestone_response_get.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/milestone_response_get_milestone.py b/src/python_client/emass_client/models/milestone_response_get_milestone.py index 65d90d92..1ac92250 100644 --- a/src/python_client/emass_client/models/milestone_response_get_milestone.py +++ b/src/python_client/emass_client/models/milestone_response_get_milestone.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/milestone_response_post.py b/src/python_client/emass_client/models/milestone_response_post.py index 1e313aa0..d67a4b3d 100644 --- a/src/python_client/emass_client/models/milestone_response_post.py +++ b/src/python_client/emass_client/models/milestone_response_post.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/milestone_response_put.py b/src/python_client/emass_client/models/milestone_response_put.py index cf607ddc..ae7119b6 100644 --- a/src/python_client/emass_client/models/milestone_response_put.py +++ b/src/python_client/emass_client/models/milestone_response_put.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/milestones_get.py b/src/python_client/emass_client/models/milestones_get.py index 2dfa12d1..3f744a96 100644 --- a/src/python_client/emass_client/models/milestones_get.py +++ b/src/python_client/emass_client/models/milestones_get.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/milestones_put_post_delete.py b/src/python_client/emass_client/models/milestones_put_post_delete.py index 168a6709..1caa9a1f 100644 --- a/src/python_client/emass_client/models/milestones_put_post_delete.py +++ b/src/python_client/emass_client/models/milestones_put_post_delete.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/milestones_request_delete_body_inner.py b/src/python_client/emass_client/models/milestones_request_delete_body_inner.py index 28a1362d..32e5b322 100644 --- a/src/python_client/emass_client/models/milestones_request_delete_body_inner.py +++ b/src/python_client/emass_client/models/milestones_request_delete_body_inner.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/milestones_required_post.py b/src/python_client/emass_client/models/milestones_required_post.py index 441a0403..257e0d1b 100644 --- a/src/python_client/emass_client/models/milestones_required_post.py +++ b/src/python_client/emass_client/models/milestones_required_post.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/milestones_required_put.py b/src/python_client/emass_client/models/milestones_required_put.py index f3c01d49..ed10eea6 100644 --- a/src/python_client/emass_client/models/milestones_required_put.py +++ b/src/python_client/emass_client/models/milestones_required_put.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/mock_object.py b/src/python_client/emass_client/models/mock_object.py index 230cd0c4..253ba373 100644 --- a/src/python_client/emass_client/models/mock_object.py +++ b/src/python_client/emass_client/models/mock_object.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/pac_get.py b/src/python_client/emass_client/models/pac_get.py index 320216dd..78459f63 100644 --- a/src/python_client/emass_client/models/pac_get.py +++ b/src/python_client/emass_client/models/pac_get.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/pac_post.py b/src/python_client/emass_client/models/pac_post.py index 25c6094d..b894ceb4 100644 --- a/src/python_client/emass_client/models/pac_post.py +++ b/src/python_client/emass_client/models/pac_post.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/pac_response_get.py b/src/python_client/emass_client/models/pac_response_get.py index 2ffd91e6..523bf73b 100644 --- a/src/python_client/emass_client/models/pac_response_get.py +++ b/src/python_client/emass_client/models/pac_response_get.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/pac_response_post.py b/src/python_client/emass_client/models/pac_response_post.py index a3098f04..231d7da6 100644 --- a/src/python_client/emass_client/models/pac_response_post.py +++ b/src/python_client/emass_client/models/pac_response_post.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/poam_get.py b/src/python_client/emass_client/models/poam_get.py index 0358ed52..07548c6a 100644 --- a/src/python_client/emass_client/models/poam_get.py +++ b/src/python_client/emass_client/models/poam_get.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/poam_post_put_del.py b/src/python_client/emass_client/models/poam_post_put_del.py index fa75f3bb..f9493446 100644 --- a/src/python_client/emass_client/models/poam_post_put_del.py +++ b/src/python_client/emass_client/models/poam_post_put_del.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/poam_request_delete_body_inner.py b/src/python_client/emass_client/models/poam_request_delete_body_inner.py index a02e7a11..86d6d424 100644 --- a/src/python_client/emass_client/models/poam_request_delete_body_inner.py +++ b/src/python_client/emass_client/models/poam_request_delete_body_inner.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/poam_response_delete.py b/src/python_client/emass_client/models/poam_response_delete.py index caf516d9..9b8d47a6 100644 --- a/src/python_client/emass_client/models/poam_response_delete.py +++ b/src/python_client/emass_client/models/poam_response_delete.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/poam_response_get_poams.py b/src/python_client/emass_client/models/poam_response_get_poams.py index ea7c7fd0..22d8f380 100644 --- a/src/python_client/emass_client/models/poam_response_get_poams.py +++ b/src/python_client/emass_client/models/poam_response_get_poams.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/poam_response_get_systems.py b/src/python_client/emass_client/models/poam_response_get_systems.py index ba97f105..d4ad6c5b 100644 --- a/src/python_client/emass_client/models/poam_response_get_systems.py +++ b/src/python_client/emass_client/models/poam_response_get_systems.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/poam_response_post.py b/src/python_client/emass_client/models/poam_response_post.py index bdc8aba7..262d75b5 100644 --- a/src/python_client/emass_client/models/poam_response_post.py +++ b/src/python_client/emass_client/models/poam_response_post.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/poam_response_put.py b/src/python_client/emass_client/models/poam_response_put.py index 2c155d26..2968579d 100644 --- a/src/python_client/emass_client/models/poam_response_put.py +++ b/src/python_client/emass_client/models/poam_response_put.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/register.py b/src/python_client/emass_client/models/register.py index a9e1f292..3e2a65b8 100644 --- a/src/python_client/emass_client/models/register.py +++ b/src/python_client/emass_client/models/register.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/register_data.py b/src/python_client/emass_client/models/register_data.py index 92be3f6a..5b37e66a 100644 --- a/src/python_client/emass_client/models/register_data.py +++ b/src/python_client/emass_client/models/register_data.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/register_user_request_post_body.py b/src/python_client/emass_client/models/register_user_request_post_body.py index 62b40bd1..d70b4aa8 100644 --- a/src/python_client/emass_client/models/register_user_request_post_body.py +++ b/src/python_client/emass_client/models/register_user_request_post_body.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/response200.py b/src/python_client/emass_client/models/response200.py index 39dbf4e0..e41b4b68 100644 --- a/src/python_client/emass_client/models/response200.py +++ b/src/python_client/emass_client/models/response200.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/response201.py b/src/python_client/emass_client/models/response201.py index ac2917d0..f14cb9c9 100644 --- a/src/python_client/emass_client/models/response201.py +++ b/src/python_client/emass_client/models/response201.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/response201_meta.py b/src/python_client/emass_client/models/response201_meta.py index d06c1b8f..a25d6d9d 100644 --- a/src/python_client/emass_client/models/response201_meta.py +++ b/src/python_client/emass_client/models/response201_meta.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/response400.py b/src/python_client/emass_client/models/response400.py index af2b37f2..b0458bcb 100644 --- a/src/python_client/emass_client/models/response400.py +++ b/src/python_client/emass_client/models/response400.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/response400_meta.py b/src/python_client/emass_client/models/response400_meta.py index c7e518b2..5c9a7f52 100644 --- a/src/python_client/emass_client/models/response400_meta.py +++ b/src/python_client/emass_client/models/response400_meta.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/response401.py b/src/python_client/emass_client/models/response401.py index 5dc75353..32f51e06 100644 --- a/src/python_client/emass_client/models/response401.py +++ b/src/python_client/emass_client/models/response401.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/response401_meta.py b/src/python_client/emass_client/models/response401_meta.py index 0da62bc8..ad793b21 100644 --- a/src/python_client/emass_client/models/response401_meta.py +++ b/src/python_client/emass_client/models/response401_meta.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/response403.py b/src/python_client/emass_client/models/response403.py index d48d5a2f..452e551f 100644 --- a/src/python_client/emass_client/models/response403.py +++ b/src/python_client/emass_client/models/response403.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/response403_meta.py b/src/python_client/emass_client/models/response403_meta.py index 2bd45e13..a7f87773 100644 --- a/src/python_client/emass_client/models/response403_meta.py +++ b/src/python_client/emass_client/models/response403_meta.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/response404.py b/src/python_client/emass_client/models/response404.py index 6f7f4bf3..1b0a6d97 100644 --- a/src/python_client/emass_client/models/response404.py +++ b/src/python_client/emass_client/models/response404.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/response405.py b/src/python_client/emass_client/models/response405.py index 161598f3..c8ed6827 100644 --- a/src/python_client/emass_client/models/response405.py +++ b/src/python_client/emass_client/models/response405.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/response405_meta.py b/src/python_client/emass_client/models/response405_meta.py index a06a598e..3705e318 100644 --- a/src/python_client/emass_client/models/response405_meta.py +++ b/src/python_client/emass_client/models/response405_meta.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/response411.py b/src/python_client/emass_client/models/response411.py index e24164e0..0d90a714 100644 --- a/src/python_client/emass_client/models/response411.py +++ b/src/python_client/emass_client/models/response411.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/response411_meta.py b/src/python_client/emass_client/models/response411_meta.py index 432df3af..75b36bc0 100644 --- a/src/python_client/emass_client/models/response411_meta.py +++ b/src/python_client/emass_client/models/response411_meta.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/response490.py b/src/python_client/emass_client/models/response490.py index 64c40f5a..850920b5 100644 --- a/src/python_client/emass_client/models/response490.py +++ b/src/python_client/emass_client/models/response490.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/response490_meta.py b/src/python_client/emass_client/models/response490_meta.py index 86043dfd..af20c6c4 100644 --- a/src/python_client/emass_client/models/response490_meta.py +++ b/src/python_client/emass_client/models/response490_meta.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/response500.py b/src/python_client/emass_client/models/response500.py index 1a1e5a8b..60643f9d 100644 --- a/src/python_client/emass_client/models/response500.py +++ b/src/python_client/emass_client/models/response500.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/response500_meta.py b/src/python_client/emass_client/models/response500_meta.py index a658235d..5ee1eec2 100644 --- a/src/python_client/emass_client/models/response500_meta.py +++ b/src/python_client/emass_client/models/response500_meta.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/role_category.py b/src/python_client/emass_client/models/role_category.py index 06774e99..c171c4fa 100644 --- a/src/python_client/emass_client/models/role_category.py +++ b/src/python_client/emass_client/models/role_category.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/roles.py b/src/python_client/emass_client/models/roles.py index 43a1cbfa..fe4fbec0 100644 --- a/src/python_client/emass_client/models/roles.py +++ b/src/python_client/emass_client/models/roles.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/ssps.py b/src/python_client/emass_client/models/ssps.py index c33fe3b8..0570d4d8 100644 --- a/src/python_client/emass_client/models/ssps.py +++ b/src/python_client/emass_client/models/ssps.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/stage.py b/src/python_client/emass_client/models/stage.py index 05dc4052..bab53bc9 100644 --- a/src/python_client/emass_client/models/stage.py +++ b/src/python_client/emass_client/models/stage.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/static_code_application_post.py b/src/python_client/emass_client/models/static_code_application_post.py index a94db0b3..58bcc4ae 100644 --- a/src/python_client/emass_client/models/static_code_application_post.py +++ b/src/python_client/emass_client/models/static_code_application_post.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/static_code_post.py b/src/python_client/emass_client/models/static_code_post.py index efd7e196..9df7ac2f 100644 --- a/src/python_client/emass_client/models/static_code_post.py +++ b/src/python_client/emass_client/models/static_code_post.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/static_code_request_post_body.py b/src/python_client/emass_client/models/static_code_request_post_body.py index 839efd0c..935582f7 100644 --- a/src/python_client/emass_client/models/static_code_request_post_body.py +++ b/src/python_client/emass_client/models/static_code_request_post_body.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/static_code_request_post_body_application.py b/src/python_client/emass_client/models/static_code_request_post_body_application.py index 3c125d74..894c4289 100644 --- a/src/python_client/emass_client/models/static_code_request_post_body_application.py +++ b/src/python_client/emass_client/models/static_code_request_post_body_application.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/static_code_response_post.py b/src/python_client/emass_client/models/static_code_response_post.py index da392bfe..77a945e9 100644 --- a/src/python_client/emass_client/models/static_code_response_post.py +++ b/src/python_client/emass_client/models/static_code_response_post.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/success200_response.py b/src/python_client/emass_client/models/success200_response.py index 7112a071..401c4b1d 100644 --- a/src/python_client/emass_client/models/success200_response.py +++ b/src/python_client/emass_client/models/success200_response.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/success200_response_data_inner.py b/src/python_client/emass_client/models/success200_response_data_inner.py index 5b1c1403..454e4a69 100644 --- a/src/python_client/emass_client/models/success200_response_data_inner.py +++ b/src/python_client/emass_client/models/success200_response_data_inner.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/system_response.py b/src/python_client/emass_client/models/system_response.py index 91084910..8184967b 100644 --- a/src/python_client/emass_client/models/system_response.py +++ b/src/python_client/emass_client/models/system_response.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/system_roles_category_response.py b/src/python_client/emass_client/models/system_roles_category_response.py index 696db82b..8a2724f4 100644 --- a/src/python_client/emass_client/models/system_roles_category_response.py +++ b/src/python_client/emass_client/models/system_roles_category_response.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/system_roles_response.py b/src/python_client/emass_client/models/system_roles_response.py index 5ad693c1..f9ef7453 100644 --- a/src/python_client/emass_client/models/system_roles_response.py +++ b/src/python_client/emass_client/models/system_roles_response.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/system_roles_response_data_inner.py b/src/python_client/emass_client/models/system_roles_response_data_inner.py index a0b182e8..e32d381a 100644 --- a/src/python_client/emass_client/models/system_roles_response_data_inner.py +++ b/src/python_client/emass_client/models/system_roles_response_data_inner.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/systems.py b/src/python_client/emass_client/models/systems.py index 8403e10b..ce7f7fac 100644 --- a/src/python_client/emass_client/models/systems.py +++ b/src/python_client/emass_client/models/systems.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/systems_response.py b/src/python_client/emass_client/models/systems_response.py index 00c9d083..71b1d7e4 100644 --- a/src/python_client/emass_client/models/systems_response.py +++ b/src/python_client/emass_client/models/systems_response.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/test.py b/src/python_client/emass_client/models/test.py index c505e102..f392457c 100644 --- a/src/python_client/emass_client/models/test.py +++ b/src/python_client/emass_client/models/test.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/test_data.py b/src/python_client/emass_client/models/test_data.py index 775aaabf..f8a37e85 100644 --- a/src/python_client/emass_client/models/test_data.py +++ b/src/python_client/emass_client/models/test_data.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/test_results_get.py b/src/python_client/emass_client/models/test_results_get.py index 391ad044..9a77dcc3 100644 --- a/src/python_client/emass_client/models/test_results_get.py +++ b/src/python_client/emass_client/models/test_results_get.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/test_results_post.py b/src/python_client/emass_client/models/test_results_post.py index d747f8df..599b369d 100644 --- a/src/python_client/emass_client/models/test_results_post.py +++ b/src/python_client/emass_client/models/test_results_post.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/test_results_response_get.py b/src/python_client/emass_client/models/test_results_response_get.py index 81573b73..5e79731a 100644 --- a/src/python_client/emass_client/models/test_results_response_get.py +++ b/src/python_client/emass_client/models/test_results_response_get.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/test_results_response_post.py b/src/python_client/emass_client/models/test_results_response_post.py index d6fbec7a..21d0a016 100644 --- a/src/python_client/emass_client/models/test_results_response_post.py +++ b/src/python_client/emass_client/models/test_results_response_post.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/users.py b/src/python_client/emass_client/models/users.py index ef5f561b..b81d61e0 100644 --- a/src/python_client/emass_client/models/users.py +++ b/src/python_client/emass_client/models/users.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/workflow_definition_get.py b/src/python_client/emass_client/models/workflow_definition_get.py index 7a437e15..cac0ed8f 100644 --- a/src/python_client/emass_client/models/workflow_definition_get.py +++ b/src/python_client/emass_client/models/workflow_definition_get.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/workflow_definition_response_get.py b/src/python_client/emass_client/models/workflow_definition_response_get.py index ae6b9978..1f5a0136 100644 --- a/src/python_client/emass_client/models/workflow_definition_response_get.py +++ b/src/python_client/emass_client/models/workflow_definition_response_get.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/workflow_instance_get.py b/src/python_client/emass_client/models/workflow_instance_get.py index d449719e..c8e6c921 100644 --- a/src/python_client/emass_client/models/workflow_instance_get.py +++ b/src/python_client/emass_client/models/workflow_instance_get.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/workflow_instance_response_get.py b/src/python_client/emass_client/models/workflow_instance_response_get.py index 78a3c956..98e17752 100644 --- a/src/python_client/emass_client/models/workflow_instance_response_get.py +++ b/src/python_client/emass_client/models/workflow_instance_response_get.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/workflow_instances_get.py b/src/python_client/emass_client/models/workflow_instances_get.py index 21578eb9..05482358 100644 --- a/src/python_client/emass_client/models/workflow_instances_get.py +++ b/src/python_client/emass_client/models/workflow_instances_get.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/workflow_instances_response_get.py b/src/python_client/emass_client/models/workflow_instances_response_get.py index 434ded19..db9f73bc 100644 --- a/src/python_client/emass_client/models/workflow_instances_response_get.py +++ b/src/python_client/emass_client/models/workflow_instances_response_get.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/models/workflow_instances_response_get_pagination.py b/src/python_client/emass_client/models/workflow_instances_response_get_pagination.py index 6bbc2ba6..f53f4a8c 100644 --- a/src/python_client/emass_client/models/workflow_instances_response_get_pagination.py +++ b/src/python_client/emass_client/models/workflow_instances_response_get_pagination.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/emass_client/rest.py b/src/python_client/emass_client/rest.py index 9f068074..775b7f40 100644 --- a/src/python_client/emass_client/rest.py +++ b/src/python_client/emass_client/rest.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/pyproject.toml b/src/python_client/pyproject.toml index eba1e1a4..4efd832e 100644 --- a/src/python_client/pyproject.toml +++ b/src/python_client/pyproject.toml @@ -1,6 +1,6 @@ [tool.poetry] name = "emass_client" -version = "3.11.1" +version = "3.12.0" description = "Enterprise Mission Assurance Support Service (eMASS)" authors = ["eMASS Tier III support "] license = "Apache-2.0" diff --git a/src/python_client/setup.py b/src/python_client/setup.py index 68475daf..df4a97fb 100644 --- a/src/python_client/setup.py +++ b/src/python_client/setup.py @@ -9,7 +9,7 @@ # prerequisite: setuptools # http://pypi.python.org/pypi/setuptools NAME = "emass_client_api" -VERSION = "3.11.1" +VERSION = "3.12.0" PYTHON_REQUIRES = ">=3.7" REQUIRES = [ "urllib3 >= 1.25.3", @@ -41,8 +41,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_artifacts_api.py b/src/python_client/test/test_artifacts_api.py index 7544d3fb..b55fe1e1 100644 --- a/src/python_client/test/test_artifacts_api.py +++ b/src/python_client/test/test_artifacts_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_artifacts_export_api.py b/src/python_client/test/test_artifacts_export_api.py index eb8a1c46..c4d04820 100644 --- a/src/python_client/test/test_artifacts_export_api.py +++ b/src/python_client/test/test_artifacts_export_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_artifacts_get.py b/src/python_client/test/test_artifacts_get.py index fb9ed8c3..2df9755c 100644 --- a/src/python_client/test/test_artifacts_get.py +++ b/src/python_client/test/test_artifacts_get.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_artifacts_request_delete_body_inner.py b/src/python_client/test/test_artifacts_request_delete_body_inner.py index 054443a8..edb8adb1 100644 --- a/src/python_client/test/test_artifacts_request_delete_body_inner.py +++ b/src/python_client/test/test_artifacts_request_delete_body_inner.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_artifacts_response_del.py b/src/python_client/test/test_artifacts_response_del.py index 89de45b1..44fa062d 100644 --- a/src/python_client/test/test_artifacts_response_del.py +++ b/src/python_client/test/test_artifacts_response_del.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_artifacts_response_del_data_inner.py b/src/python_client/test/test_artifacts_response_del_data_inner.py index 532cbdc8..c4f66d3d 100644 --- a/src/python_client/test/test_artifacts_response_del_data_inner.py +++ b/src/python_client/test/test_artifacts_response_del_data_inner.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_artifacts_response_get.py b/src/python_client/test/test_artifacts_response_get.py index c753ddd9..f52a34dd 100644 --- a/src/python_client/test/test_artifacts_response_get.py +++ b/src/python_client/test/test_artifacts_response_get.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_artifacts_response_put_post.py b/src/python_client/test/test_artifacts_response_put_post.py index e4144595..ce8be2af 100644 --- a/src/python_client/test/test_artifacts_response_put_post.py +++ b/src/python_client/test/test_artifacts_response_put_post.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_artifacts_response_put_post_data_inner.py b/src/python_client/test/test_artifacts_response_put_post_data_inner.py index d5737b7f..2ba52140 100644 --- a/src/python_client/test/test_artifacts_response_put_post_data_inner.py +++ b/src/python_client/test/test_artifacts_response_put_post_data_inner.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_cac_api.py b/src/python_client/test/test_cac_api.py index 60d0d7a0..13ea0162 100644 --- a/src/python_client/test/test_cac_api.py +++ b/src/python_client/test/test_cac_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_cac_get.py b/src/python_client/test/test_cac_get.py index 875ace19..739404a6 100644 --- a/src/python_client/test/test_cac_get.py +++ b/src/python_client/test/test_cac_get.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_cac_response_get.py b/src/python_client/test/test_cac_response_get.py index b8f28d6d..e38e5df4 100644 --- a/src/python_client/test/test_cac_response_get.py +++ b/src/python_client/test/test_cac_response_get.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_cac_response_post.py b/src/python_client/test/test_cac_response_post.py index 2c915dd4..ff1a0e6d 100644 --- a/src/python_client/test/test_cac_response_post.py +++ b/src/python_client/test/test_cac_response_post.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_cac_response_post_data_inner.py b/src/python_client/test/test_cac_response_post_data_inner.py index c92807b3..365e6b5b 100644 --- a/src/python_client/test/test_cac_response_post_data_inner.py +++ b/src/python_client/test/test_cac_response_post_data_inner.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_cloud_resource_results_api.py b/src/python_client/test/test_cloud_resource_results_api.py index ccd687c8..3efaecf8 100644 --- a/src/python_client/test/test_cloud_resource_results_api.py +++ b/src/python_client/test/test_cloud_resource_results_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_cloud_resources_delete.py b/src/python_client/test/test_cloud_resources_delete.py index 8b0b732b..ef8e0347 100644 --- a/src/python_client/test/test_cloud_resources_delete.py +++ b/src/python_client/test/test_cloud_resources_delete.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_cloud_resources_delete_body_inner.py b/src/python_client/test/test_cloud_resources_delete_body_inner.py index cc07894b..32bf078a 100644 --- a/src/python_client/test/test_cloud_resources_delete_body_inner.py +++ b/src/python_client/test/test_cloud_resources_delete_body_inner.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_cloud_resources_post_delete.py b/src/python_client/test/test_cloud_resources_post_delete.py index 869eafb1..19157bc9 100644 --- a/src/python_client/test/test_cloud_resources_post_delete.py +++ b/src/python_client/test/test_cloud_resources_post_delete.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_cloud_resources_response_post.py b/src/python_client/test/test_cloud_resources_response_post.py index 1d0a2037..5d1bb217 100644 --- a/src/python_client/test/test_cloud_resources_response_post.py +++ b/src/python_client/test/test_cloud_resources_response_post.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_cmmc_assessments_api.py b/src/python_client/test/test_cmmc_assessments_api.py index f515fbc8..e8ea8065 100644 --- a/src/python_client/test/test_cmmc_assessments_api.py +++ b/src/python_client/test/test_cmmc_assessments_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_cmmc_get.py b/src/python_client/test/test_cmmc_get.py index 540f5d31..0b12f018 100644 --- a/src/python_client/test/test_cmmc_get.py +++ b/src/python_client/test/test_cmmc_get.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_cmmc_response_get.py b/src/python_client/test/test_cmmc_response_get.py index 66a77cbf..bb77eb2c 100644 --- a/src/python_client/test/test_cmmc_response_get.py +++ b/src/python_client/test/test_cmmc_response_get.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_connectivity_ccsd.py b/src/python_client/test/test_connectivity_ccsd.py index baa436ad..2d172c00 100644 --- a/src/python_client/test/test_connectivity_ccsd.py +++ b/src/python_client/test/test_connectivity_ccsd.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_container_resources_delete_body_inner.py b/src/python_client/test/test_container_resources_delete_body_inner.py index 35fd078c..37739875 100644 --- a/src/python_client/test/test_container_resources_delete_body_inner.py +++ b/src/python_client/test/test_container_resources_delete_body_inner.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_container_scan_results_api.py b/src/python_client/test/test_container_scan_results_api.py index 94e29ab0..e8ee2487 100644 --- a/src/python_client/test/test_container_scan_results_api.py +++ b/src/python_client/test/test_container_scan_results_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_containers_resources_post_delete.py b/src/python_client/test/test_containers_resources_post_delete.py index 2041e8d6..ebad32db 100644 --- a/src/python_client/test/test_containers_resources_post_delete.py +++ b/src/python_client/test/test_containers_resources_post_delete.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_containers_response_delete.py b/src/python_client/test/test_containers_response_delete.py index 41f9dde1..b2a28dbe 100644 --- a/src/python_client/test/test_containers_response_delete.py +++ b/src/python_client/test/test_containers_response_delete.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_containers_response_post.py b/src/python_client/test/test_containers_response_post.py index e1fd3055..fa929fb8 100644 --- a/src/python_client/test/test_containers_response_post.py +++ b/src/python_client/test/test_containers_response_post.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_controls_api.py b/src/python_client/test/test_controls_api.py index 4a021a00..205e2c80 100644 --- a/src/python_client/test/test_controls_api.py +++ b/src/python_client/test/test_controls_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_controls_get.py b/src/python_client/test/test_controls_get.py index b7a057b6..beea6316 100644 --- a/src/python_client/test/test_controls_get.py +++ b/src/python_client/test/test_controls_get.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_controls_put.py b/src/python_client/test/test_controls_put.py index 45d2978f..e88d122c 100644 --- a/src/python_client/test/test_controls_put.py +++ b/src/python_client/test/test_controls_put.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_controls_response_get.py b/src/python_client/test/test_controls_response_get.py index be6b66b2..c407cde5 100644 --- a/src/python_client/test/test_controls_response_get.py +++ b/src/python_client/test/test_controls_response_get.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_controls_response_put.py b/src/python_client/test/test_controls_response_put.py index 5678e907..03b49328 100644 --- a/src/python_client/test/test_controls_response_put.py +++ b/src/python_client/test/test_controls_response_put.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_dashboard_mock_response.py b/src/python_client/test/test_dashboard_mock_response.py index 980f04e4..e295b245 100644 --- a/src/python_client/test/test_dashboard_mock_response.py +++ b/src/python_client/test/test_dashboard_mock_response.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_dashboard_mock_response_pagination.py b/src/python_client/test/test_dashboard_mock_response_pagination.py index fc49cec9..791282ca 100644 --- a/src/python_client/test/test_dashboard_mock_response_pagination.py +++ b/src/python_client/test/test_dashboard_mock_response_pagination.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_definition_transitions.py b/src/python_client/test/test_definition_transitions.py index a640696a..d767c9d9 100644 --- a/src/python_client/test/test_definition_transitions.py +++ b/src/python_client/test/test_definition_transitions.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_enterprise_artifacts_dashboards_api.py b/src/python_client/test/test_enterprise_artifacts_dashboards_api.py index 2e4aa369..691bdafa 100644 --- a/src/python_client/test/test_enterprise_artifacts_dashboards_api.py +++ b/src/python_client/test/test_enterprise_artifacts_dashboards_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_enterprise_poam_dashboards_api.py b/src/python_client/test/test_enterprise_poam_dashboards_api.py index 95570d22..3e18a965 100644 --- a/src/python_client/test/test_enterprise_poam_dashboards_api.py +++ b/src/python_client/test/test_enterprise_poam_dashboards_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_enterprise_security_controls_dashboards_api.py b/src/python_client/test/test_enterprise_security_controls_dashboards_api.py index 9d997897..4c883b79 100644 --- a/src/python_client/test/test_enterprise_security_controls_dashboards_api.py +++ b/src/python_client/test/test_enterprise_security_controls_dashboards_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_enterprise_sensor_based_hardware_resources_dashboards_api.py b/src/python_client/test/test_enterprise_sensor_based_hardware_resources_dashboards_api.py index 37ddd964..2f62c779 100644 --- a/src/python_client/test/test_enterprise_sensor_based_hardware_resources_dashboards_api.py +++ b/src/python_client/test/test_enterprise_sensor_based_hardware_resources_dashboards_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_enterprise_sensor_based_software_resources_dashboards_api.py b/src/python_client/test/test_enterprise_sensor_based_software_resources_dashboards_api.py index a05cb6be..52194649 100644 --- a/src/python_client/test/test_enterprise_sensor_based_software_resources_dashboards_api.py +++ b/src/python_client/test/test_enterprise_sensor_based_software_resources_dashboards_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_enterprise_terms_conditions_dashboards_api.py b/src/python_client/test/test_enterprise_terms_conditions_dashboards_api.py index 3792a7db..b2683e56 100644 --- a/src/python_client/test/test_enterprise_terms_conditions_dashboards_api.py +++ b/src/python_client/test/test_enterprise_terms_conditions_dashboards_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_enterprise_vulnerability_dashboards_api.py b/src/python_client/test/test_enterprise_vulnerability_dashboards_api.py index 8538f112..9284a066 100644 --- a/src/python_client/test/test_enterprise_vulnerability_dashboards_api.py +++ b/src/python_client/test/test_enterprise_vulnerability_dashboards_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_fisma_inventory_summary_dashboards_api.py b/src/python_client/test/test_fisma_inventory_summary_dashboards_api.py index f0466834..0bae2a07 100644 --- a/src/python_client/test/test_fisma_inventory_summary_dashboards_api.py +++ b/src/python_client/test/test_fisma_inventory_summary_dashboards_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_hardware_baseline_dashboards_api.py b/src/python_client/test/test_hardware_baseline_dashboards_api.py index 013f014e..43b5f591 100644 --- a/src/python_client/test/test_hardware_baseline_dashboards_api.py +++ b/src/python_client/test/test_hardware_baseline_dashboards_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_instances_transitions.py b/src/python_client/test/test_instances_transitions.py index c08ae1c5..8ead6185 100644 --- a/src/python_client/test/test_instances_transitions.py +++ b/src/python_client/test/test_instances_transitions.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_milestone_response_delete.py b/src/python_client/test/test_milestone_response_delete.py index df945f87..64467725 100644 --- a/src/python_client/test/test_milestone_response_delete.py +++ b/src/python_client/test/test_milestone_response_delete.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_milestone_response_get.py b/src/python_client/test/test_milestone_response_get.py index 7f9af620..da7a2950 100644 --- a/src/python_client/test/test_milestone_response_get.py +++ b/src/python_client/test/test_milestone_response_get.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_milestone_response_get_milestone.py b/src/python_client/test/test_milestone_response_get_milestone.py index a641c249..351ad3a1 100644 --- a/src/python_client/test/test_milestone_response_get_milestone.py +++ b/src/python_client/test/test_milestone_response_get_milestone.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_milestone_response_post.py b/src/python_client/test/test_milestone_response_post.py index 90487dd4..5533d83b 100644 --- a/src/python_client/test/test_milestone_response_post.py +++ b/src/python_client/test/test_milestone_response_post.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_milestone_response_put.py b/src/python_client/test/test_milestone_response_put.py index 27ad9743..1f2234ce 100644 --- a/src/python_client/test/test_milestone_response_put.py +++ b/src/python_client/test/test_milestone_response_put.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_milestones_api.py b/src/python_client/test/test_milestones_api.py index 16a84f48..779caa5a 100644 --- a/src/python_client/test/test_milestones_api.py +++ b/src/python_client/test/test_milestones_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_milestones_get.py b/src/python_client/test/test_milestones_get.py index 31fdeb59..aad0c826 100644 --- a/src/python_client/test/test_milestones_get.py +++ b/src/python_client/test/test_milestones_get.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_milestones_put_post_delete.py b/src/python_client/test/test_milestones_put_post_delete.py index c48426ea..885be683 100644 --- a/src/python_client/test/test_milestones_put_post_delete.py +++ b/src/python_client/test/test_milestones_put_post_delete.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_milestones_request_delete_body_inner.py b/src/python_client/test/test_milestones_request_delete_body_inner.py index c84dd2ff..4b92ade0 100644 --- a/src/python_client/test/test_milestones_request_delete_body_inner.py +++ b/src/python_client/test/test_milestones_request_delete_body_inner.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_milestones_required_post.py b/src/python_client/test/test_milestones_required_post.py index f3e104e5..10379560 100644 --- a/src/python_client/test/test_milestones_required_post.py +++ b/src/python_client/test/test_milestones_required_post.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_milestones_required_put.py b/src/python_client/test/test_milestones_required_put.py index 5f4f93a0..ed878f9f 100644 --- a/src/python_client/test/test_milestones_required_put.py +++ b/src/python_client/test/test_milestones_required_put.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_mock_object.py b/src/python_client/test/test_mock_object.py index 2cb343e1..9a80d9b4 100644 --- a/src/python_client/test/test_mock_object.py +++ b/src/python_client/test/test_mock_object.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_pac_api.py b/src/python_client/test/test_pac_api.py index dd2184e4..d615826c 100644 --- a/src/python_client/test/test_pac_api.py +++ b/src/python_client/test/test_pac_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_pac_get.py b/src/python_client/test/test_pac_get.py index 41ead85a..6af3c4db 100644 --- a/src/python_client/test/test_pac_get.py +++ b/src/python_client/test/test_pac_get.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_pac_post.py b/src/python_client/test/test_pac_post.py index 3d9f0d3b..1eb181d1 100644 --- a/src/python_client/test/test_pac_post.py +++ b/src/python_client/test/test_pac_post.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_pac_response_get.py b/src/python_client/test/test_pac_response_get.py index dae1bfce..4c9f4ac0 100644 --- a/src/python_client/test/test_pac_response_get.py +++ b/src/python_client/test/test_pac_response_get.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_pac_response_post.py b/src/python_client/test/test_pac_response_post.py index 19a33164..7135875b 100644 --- a/src/python_client/test/test_pac_response_post.py +++ b/src/python_client/test/test_pac_response_post.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_poam_api.py b/src/python_client/test/test_poam_api.py index 62079c4c..505b8e3b 100644 --- a/src/python_client/test/test_poam_api.py +++ b/src/python_client/test/test_poam_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_poam_get.py b/src/python_client/test/test_poam_get.py index a029455c..9fccc02c 100644 --- a/src/python_client/test/test_poam_get.py +++ b/src/python_client/test/test_poam_get.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_poam_post_put_del.py b/src/python_client/test/test_poam_post_put_del.py index 1c811116..d8559a28 100644 --- a/src/python_client/test/test_poam_post_put_del.py +++ b/src/python_client/test/test_poam_post_put_del.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_poam_request_delete_body_inner.py b/src/python_client/test/test_poam_request_delete_body_inner.py index 060020ea..68e2b9ba 100644 --- a/src/python_client/test/test_poam_request_delete_body_inner.py +++ b/src/python_client/test/test_poam_request_delete_body_inner.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_poam_response_delete.py b/src/python_client/test/test_poam_response_delete.py index 52f9a8c0..74c017a0 100644 --- a/src/python_client/test/test_poam_response_delete.py +++ b/src/python_client/test/test_poam_response_delete.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_poam_response_get_poams.py b/src/python_client/test/test_poam_response_get_poams.py index 15277f36..9148fe9a 100644 --- a/src/python_client/test/test_poam_response_get_poams.py +++ b/src/python_client/test/test_poam_response_get_poams.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_poam_response_get_systems.py b/src/python_client/test/test_poam_response_get_systems.py index 5bd69303..3df0e192 100644 --- a/src/python_client/test/test_poam_response_get_systems.py +++ b/src/python_client/test/test_poam_response_get_systems.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_poam_response_post.py b/src/python_client/test/test_poam_response_post.py index 0bac73e2..3bbb4a21 100644 --- a/src/python_client/test/test_poam_response_post.py +++ b/src/python_client/test/test_poam_response_post.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_poam_response_put.py b/src/python_client/test/test_poam_response_put.py index 3ab34498..606f6494 100644 --- a/src/python_client/test/test_poam_response_put.py +++ b/src/python_client/test/test_poam_response_put.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_ports_and_protocols_dashboards_api.py b/src/python_client/test/test_ports_and_protocols_dashboards_api.py index ccf6a84c..f84962d1 100644 --- a/src/python_client/test/test_ports_and_protocols_dashboards_api.py +++ b/src/python_client/test/test_ports_and_protocols_dashboards_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_privacy_compliance_dashboards_api.py b/src/python_client/test/test_privacy_compliance_dashboards_api.py index f3c31ead..dc4bf511 100644 --- a/src/python_client/test/test_privacy_compliance_dashboards_api.py +++ b/src/python_client/test/test_privacy_compliance_dashboards_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_register.py b/src/python_client/test/test_register.py index 50f92882..c144d76e 100644 --- a/src/python_client/test/test_register.py +++ b/src/python_client/test/test_register.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_register_data.py b/src/python_client/test/test_register_data.py index be34a912..7321b144 100644 --- a/src/python_client/test/test_register_data.py +++ b/src/python_client/test/test_register_data.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_register_user_request_post_body.py b/src/python_client/test/test_register_user_request_post_body.py index 40b5c408..162bb0aa 100644 --- a/src/python_client/test/test_register_user_request_post_body.py +++ b/src/python_client/test/test_register_user_request_post_body.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_registration_api.py b/src/python_client/test/test_registration_api.py index 199f0ddc..64f73dcf 100644 --- a/src/python_client/test/test_registration_api.py +++ b/src/python_client/test/test_registration_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_response200.py b/src/python_client/test/test_response200.py index 1b66f49a..31b31492 100644 --- a/src/python_client/test/test_response200.py +++ b/src/python_client/test/test_response200.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_response201.py b/src/python_client/test/test_response201.py index 1d48602b..657ca968 100644 --- a/src/python_client/test/test_response201.py +++ b/src/python_client/test/test_response201.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_response201_meta.py b/src/python_client/test/test_response201_meta.py index 6a403270..b3d66b93 100644 --- a/src/python_client/test/test_response201_meta.py +++ b/src/python_client/test/test_response201_meta.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_response400.py b/src/python_client/test/test_response400.py index 44d5fd4e..3e5f9c94 100644 --- a/src/python_client/test/test_response400.py +++ b/src/python_client/test/test_response400.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_response400_meta.py b/src/python_client/test/test_response400_meta.py index 8ac88b3e..7aa70205 100644 --- a/src/python_client/test/test_response400_meta.py +++ b/src/python_client/test/test_response400_meta.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_response401.py b/src/python_client/test/test_response401.py index 0a56d89a..f5d4d047 100644 --- a/src/python_client/test/test_response401.py +++ b/src/python_client/test/test_response401.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_response401_meta.py b/src/python_client/test/test_response401_meta.py index a9b2cca3..994f753e 100644 --- a/src/python_client/test/test_response401_meta.py +++ b/src/python_client/test/test_response401_meta.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_response403.py b/src/python_client/test/test_response403.py index 59170773..f0d45d6d 100644 --- a/src/python_client/test/test_response403.py +++ b/src/python_client/test/test_response403.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_response403_meta.py b/src/python_client/test/test_response403_meta.py index 8822e64b..da81bbdb 100644 --- a/src/python_client/test/test_response403_meta.py +++ b/src/python_client/test/test_response403_meta.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_response404.py b/src/python_client/test/test_response404.py index 1c595a9c..3c47f4f0 100644 --- a/src/python_client/test/test_response404.py +++ b/src/python_client/test/test_response404.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_response405.py b/src/python_client/test/test_response405.py index 7ff57b5c..43a8e023 100644 --- a/src/python_client/test/test_response405.py +++ b/src/python_client/test/test_response405.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_response405_meta.py b/src/python_client/test/test_response405_meta.py index 95953c7f..1ff7a128 100644 --- a/src/python_client/test/test_response405_meta.py +++ b/src/python_client/test/test_response405_meta.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_response411.py b/src/python_client/test/test_response411.py index 62d85fb2..6a770983 100644 --- a/src/python_client/test/test_response411.py +++ b/src/python_client/test/test_response411.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_response411_meta.py b/src/python_client/test/test_response411_meta.py index 51d04629..eead9b37 100644 --- a/src/python_client/test/test_response411_meta.py +++ b/src/python_client/test/test_response411_meta.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_response490.py b/src/python_client/test/test_response490.py index ffadf983..16cd6333 100644 --- a/src/python_client/test/test_response490.py +++ b/src/python_client/test/test_response490.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_response490_meta.py b/src/python_client/test/test_response490_meta.py index 6ff203d2..39ace598 100644 --- a/src/python_client/test/test_response490_meta.py +++ b/src/python_client/test/test_response490_meta.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_response500.py b/src/python_client/test/test_response500.py index 0445766a..6040f2c2 100644 --- a/src/python_client/test/test_response500.py +++ b/src/python_client/test/test_response500.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_response500_meta.py b/src/python_client/test/test_response500_meta.py index d5c55dfe..5bd6d324 100644 --- a/src/python_client/test/test_response500_meta.py +++ b/src/python_client/test/test_response500_meta.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_role_category.py b/src/python_client/test/test_role_category.py index 2c4a47b3..b58d69ee 100644 --- a/src/python_client/test/test_role_category.py +++ b/src/python_client/test/test_role_category.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_roles.py b/src/python_client/test/test_roles.py index 7991702c..32e6b9f8 100644 --- a/src/python_client/test/test_roles.py +++ b/src/python_client/test/test_roles.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_software_baseline_dashboards_api.py b/src/python_client/test/test_software_baseline_dashboards_api.py index aa125a47..e538a10d 100644 --- a/src/python_client/test/test_software_baseline_dashboards_api.py +++ b/src/python_client/test/test_software_baseline_dashboards_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_ssps.py b/src/python_client/test/test_ssps.py index 9b288c40..072a59ac 100644 --- a/src/python_client/test/test_ssps.py +++ b/src/python_client/test/test_ssps.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_stage.py b/src/python_client/test/test_stage.py index 9ee69ace..2d8bc793 100644 --- a/src/python_client/test/test_stage.py +++ b/src/python_client/test/test_stage.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_static_code_application_post.py b/src/python_client/test/test_static_code_application_post.py index 5648f970..335c78fc 100644 --- a/src/python_client/test/test_static_code_application_post.py +++ b/src/python_client/test/test_static_code_application_post.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_static_code_post.py b/src/python_client/test/test_static_code_post.py index 7d1cb810..2f144021 100644 --- a/src/python_client/test/test_static_code_post.py +++ b/src/python_client/test/test_static_code_post.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_static_code_request_post_body.py b/src/python_client/test/test_static_code_request_post_body.py index f231be8a..3953a4ee 100644 --- a/src/python_client/test/test_static_code_request_post_body.py +++ b/src/python_client/test/test_static_code_request_post_body.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_static_code_request_post_body_application.py b/src/python_client/test/test_static_code_request_post_body_application.py index 1b7d0da9..50148241 100644 --- a/src/python_client/test/test_static_code_request_post_body_application.py +++ b/src/python_client/test/test_static_code_request_post_body_application.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_static_code_response_post.py b/src/python_client/test/test_static_code_response_post.py index 03d200fa..b6f2d2fe 100644 --- a/src/python_client/test/test_static_code_response_post.py +++ b/src/python_client/test/test_static_code_response_post.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_static_code_scans_api.py b/src/python_client/test/test_static_code_scans_api.py index 25a6300b..a8b488ee 100644 --- a/src/python_client/test/test_static_code_scans_api.py +++ b/src/python_client/test/test_static_code_scans_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_success200_response.py b/src/python_client/test/test_success200_response.py index 0c7e5539..ae80db0a 100644 --- a/src/python_client/test/test_success200_response.py +++ b/src/python_client/test/test_success200_response.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_success200_response_data_inner.py b/src/python_client/test/test_success200_response_data_inner.py index 5a72e776..bb9ebe78 100644 --- a/src/python_client/test/test_success200_response_data_inner.py +++ b/src/python_client/test/test_success200_response_data_inner.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_system_a20_summary_dashboard_api.py b/src/python_client/test/test_system_a20_summary_dashboard_api.py index b4631e9a..f5a9dfde 100644 --- a/src/python_client/test/test_system_a20_summary_dashboard_api.py +++ b/src/python_client/test/test_system_a20_summary_dashboard_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_system_aa_summary_dashboard_api.py b/src/python_client/test/test_system_aa_summary_dashboard_api.py index b6c5dd2c..a643ec0e 100644 --- a/src/python_client/test/test_system_aa_summary_dashboard_api.py +++ b/src/python_client/test/test_system_aa_summary_dashboard_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_system_associations_dashboard_api.py b/src/python_client/test/test_system_associations_dashboard_api.py index f596c785..2fb0c21b 100644 --- a/src/python_client/test/test_system_associations_dashboard_api.py +++ b/src/python_client/test/test_system_associations_dashboard_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_system_conmon_integration_status_dashboard_api.py b/src/python_client/test/test_system_conmon_integration_status_dashboard_api.py index dbccc40e..aba5dbbc 100644 --- a/src/python_client/test/test_system_conmon_integration_status_dashboard_api.py +++ b/src/python_client/test/test_system_conmon_integration_status_dashboard_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_system_pl109_reporting_summary_dashboard_api.py b/src/python_client/test/test_system_pl109_reporting_summary_dashboard_api.py index 8ec64237..655f7fa4 100644 --- a/src/python_client/test/test_system_pl109_reporting_summary_dashboard_api.py +++ b/src/python_client/test/test_system_pl109_reporting_summary_dashboard_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_system_response.py b/src/python_client/test/test_system_response.py index d13e9126..86f3367b 100644 --- a/src/python_client/test/test_system_response.py +++ b/src/python_client/test/test_system_response.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_system_roles_api.py b/src/python_client/test/test_system_roles_api.py index 5c0c7561..8120af19 100644 --- a/src/python_client/test/test_system_roles_api.py +++ b/src/python_client/test/test_system_roles_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_system_roles_category_response.py b/src/python_client/test/test_system_roles_category_response.py index 1fc1164d..64fbf7ec 100644 --- a/src/python_client/test/test_system_roles_category_response.py +++ b/src/python_client/test/test_system_roles_category_response.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_system_roles_response.py b/src/python_client/test/test_system_roles_response.py index 3a49a709..bf53f066 100644 --- a/src/python_client/test/test_system_roles_response.py +++ b/src/python_client/test/test_system_roles_response.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_system_roles_response_data_inner.py b/src/python_client/test/test_system_roles_response_data_inner.py index b19359cf..2f5fee94 100644 --- a/src/python_client/test/test_system_roles_response_data_inner.py +++ b/src/python_client/test/test_system_roles_response_data_inner.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_system_status_dashboard_api.py b/src/python_client/test/test_system_status_dashboard_api.py index 2da1691c..ca4576cb 100644 --- a/src/python_client/test/test_system_status_dashboard_api.py +++ b/src/python_client/test/test_system_status_dashboard_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_systems.py b/src/python_client/test/test_systems.py index 2363de7f..cfc5422a 100644 --- a/src/python_client/test/test_systems.py +++ b/src/python_client/test/test_systems.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_systems_api.py b/src/python_client/test/test_systems_api.py index bf56b05a..a0dac211 100644 --- a/src/python_client/test/test_systems_api.py +++ b/src/python_client/test/test_systems_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_systems_response.py b/src/python_client/test/test_systems_response.py index d78c80cd..16a9ec4e 100644 --- a/src/python_client/test/test_systems_response.py +++ b/src/python_client/test/test_systems_response.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_test.py b/src/python_client/test/test_test.py index 84bd09f7..2aa57dd6 100644 --- a/src/python_client/test/test_test.py +++ b/src/python_client/test/test_test.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_test_api.py b/src/python_client/test/test_test_api.py index 086418e0..d64cdab1 100644 --- a/src/python_client/test/test_test_api.py +++ b/src/python_client/test/test_test_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_test_data.py b/src/python_client/test/test_test_data.py index bc67249b..ef57346c 100644 --- a/src/python_client/test/test_test_data.py +++ b/src/python_client/test/test_test_data.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_test_results_api.py b/src/python_client/test/test_test_results_api.py index 2f755511..811e330f 100644 --- a/src/python_client/test/test_test_results_api.py +++ b/src/python_client/test/test_test_results_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_test_results_get.py b/src/python_client/test/test_test_results_get.py index 87fbbc30..3fe5a5d8 100644 --- a/src/python_client/test/test_test_results_get.py +++ b/src/python_client/test/test_test_results_get.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_test_results_post.py b/src/python_client/test/test_test_results_post.py index 848de54d..17596f3b 100644 --- a/src/python_client/test/test_test_results_post.py +++ b/src/python_client/test/test_test_results_post.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_test_results_response_get.py b/src/python_client/test/test_test_results_response_get.py index 6be46ad7..9c073084 100644 --- a/src/python_client/test/test_test_results_response_get.py +++ b/src/python_client/test/test_test_results_response_get.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_test_results_response_post.py b/src/python_client/test/test_test_results_response_post.py index 25692a05..0aac9f3c 100644 --- a/src/python_client/test/test_test_results_response_post.py +++ b/src/python_client/test/test_test_results_response_post.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_threat_risks_dashboards_api.py b/src/python_client/test/test_threat_risks_dashboards_api.py index 8be278d3..5e143f5b 100644 --- a/src/python_client/test/test_threat_risks_dashboards_api.py +++ b/src/python_client/test/test_threat_risks_dashboards_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_users.py b/src/python_client/test/test_users.py index 29b8e23f..6abd02ec 100644 --- a/src/python_client/test/test_users.py +++ b/src/python_client/test/test_users.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_users_dashboard_api.py b/src/python_client/test/test_users_dashboard_api.py index a6661280..e4020f35 100644 --- a/src/python_client/test/test_users_dashboard_api.py +++ b/src/python_client/test/test_users_dashboard_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_workflow_definition_get.py b/src/python_client/test/test_workflow_definition_get.py index d0324d16..481cc48f 100644 --- a/src/python_client/test/test_workflow_definition_get.py +++ b/src/python_client/test/test_workflow_definition_get.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_workflow_definition_response_get.py b/src/python_client/test/test_workflow_definition_response_get.py index 1cda6b84..deb14391 100644 --- a/src/python_client/test/test_workflow_definition_response_get.py +++ b/src/python_client/test/test_workflow_definition_response_get.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_workflow_definitions_api.py b/src/python_client/test/test_workflow_definitions_api.py index 03d26180..01fa1757 100644 --- a/src/python_client/test/test_workflow_definitions_api.py +++ b/src/python_client/test/test_workflow_definitions_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_workflow_instance_get.py b/src/python_client/test/test_workflow_instance_get.py index d6112883..048bb19d 100644 --- a/src/python_client/test/test_workflow_instance_get.py +++ b/src/python_client/test/test_workflow_instance_get.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_workflow_instance_response_get.py b/src/python_client/test/test_workflow_instance_response_get.py index 61dbab6b..25d8981e 100644 --- a/src/python_client/test/test_workflow_instance_response_get.py +++ b/src/python_client/test/test_workflow_instance_response_get.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_workflow_instances_api.py b/src/python_client/test/test_workflow_instances_api.py index 5fed312c..d7805f56 100644 --- a/src/python_client/test/test_workflow_instances_api.py +++ b/src/python_client/test/test_workflow_instances_api.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_workflow_instances_get.py b/src/python_client/test/test_workflow_instances_get.py index 4fe1b4a2..bb31f025 100644 --- a/src/python_client/test/test_workflow_instances_get.py +++ b/src/python_client/test/test_workflow_instances_get.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_workflow_instances_response_get.py b/src/python_client/test/test_workflow_instances_response_get.py index 0f0a6ab5..3d5face1 100644 --- a/src/python_client/test/test_workflow_instances_response_get.py +++ b/src/python_client/test/test_workflow_instances_response_get.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/python_client/test/test_workflow_instances_response_get_pagination.py b/src/python_client/test/test_workflow_instances_response_get_pagination.py index 4c1687be..fcbc4ebd 100644 --- a/src/python_client/test/test_workflow_instances_response_get_pagination.py +++ b/src/python_client/test/test_workflow_instances_response_get_pagination.py @@ -9,8 +9,8 @@ This Python package was generated from the eMASS API specification: - API version: v3.12 -- Package version: 3.11.1 -- Build date: 2023-10-10T02:05:20.537795Z[Etc/UTC] +- Package version: 3.12.0 +- Build date: 2023-10-10T14:36:02.975730Z[Etc/UTC] ## Requirements. diff --git a/src/ruby_client/README.md b/src/ruby_client/README.md index e46e6c3a..246bbba3 100644 --- a/src/ruby_client/README.md +++ b/src/ruby_client/README.md @@ -10,7 +10,7 @@ assessments and complete actions associated with system records. New users will need to [register](https://nisp.emass.apps.mil/Content/Help/jobaids/eMASS_OT_NewUser_Job_Aid.pdf) an API key with the eMASS development team prior to accessing the site for the first time. The eMASS REST API requires a client certificate (SSL/TLS, DoD PKI only). Use the `Registration` POST endpoint to register the client -certificate. The endpoint returns the user `api-key`. BOHA

+certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-key). If the service receives diff --git a/src/ruby_client/emass_client.gemspec b/src/ruby_client/emass_client.gemspec index 97a42857..bd888a8c 100644 --- a/src/ruby_client/emass_client.gemspec +++ b/src/ruby_client/emass_client.gemspec @@ -3,7 +3,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil @@ -23,7 +23,7 @@ Gem::Specification.new do |s| s.email = ["disa.meade.id.mbx.emass-tier-iii-support@mail.mil"] s.homepage = "https://openapi-generator.tech" s.summary = "Enterprise Mission Assurance Support Service (eMASS) Ruby Gem" - # s.description = "The Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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: " + # s.description = "The Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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: " s.description = "The emass_client is a ruby gem that implements the Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) specifications" s.license = "Apache-2.0" s.required_ruby_version = ">= 2.4" diff --git a/src/ruby_client/lib/emass_client.rb b/src/ruby_client/lib/emass_client.rb index 3b0016a7..011a697d 100644 --- a/src/ruby_client/lib/emass_client.rb +++ b/src/ruby_client/lib/emass_client.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 5eb07589..5f805731 100644 --- a/src/ruby_client/lib/emass_client/api/artifacts_api.rb +++ b/src/ruby_client/lib/emass_client/api/artifacts_api.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 310594ed..160b4131 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 1e3d366e..c78aaf01 100644 --- a/src/ruby_client/lib/emass_client/api/cac_api.rb +++ b/src/ruby_client/lib/emass_client/api/cac_api.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/api/cloud_resource_results_api.rb b/src/ruby_client/lib/emass_client/api/cloud_resource_results_api.rb index bf06eaa9..cc3337a6 100644 --- a/src/ruby_client/lib/emass_client/api/cloud_resource_results_api.rb +++ b/src/ruby_client/lib/emass_client/api/cloud_resource_results_api.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 2cb3eca2..3cbfa9c0 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/api/container_scan_results_api.rb b/src/ruby_client/lib/emass_client/api/container_scan_results_api.rb index e633feec..b7a38349 100644 --- a/src/ruby_client/lib/emass_client/api/container_scan_results_api.rb +++ b/src/ruby_client/lib/emass_client/api/container_scan_results_api.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 74b75ca2..0da0d9a0 100644 --- a/src/ruby_client/lib/emass_client/api/controls_api.rb +++ b/src/ruby_client/lib/emass_client/api/controls_api.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/api/enterprise_artifacts_dashboards_api.rb b/src/ruby_client/lib/emass_client/api/enterprise_artifacts_dashboards_api.rb index 6a79846d..1072dc1d 100644 --- a/src/ruby_client/lib/emass_client/api/enterprise_artifacts_dashboards_api.rb +++ b/src/ruby_client/lib/emass_client/api/enterprise_artifacts_dashboards_api.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/api/enterprise_poam_dashboards_api.rb b/src/ruby_client/lib/emass_client/api/enterprise_poam_dashboards_api.rb index 29eed59e..9a2c581a 100644 --- a/src/ruby_client/lib/emass_client/api/enterprise_poam_dashboards_api.rb +++ b/src/ruby_client/lib/emass_client/api/enterprise_poam_dashboards_api.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/api/enterprise_security_controls_dashboards_api.rb b/src/ruby_client/lib/emass_client/api/enterprise_security_controls_dashboards_api.rb index e7c245f2..41cc37c2 100644 --- a/src/ruby_client/lib/emass_client/api/enterprise_security_controls_dashboards_api.rb +++ b/src/ruby_client/lib/emass_client/api/enterprise_security_controls_dashboards_api.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/api/enterprise_sensor_based_hardware_resources_dashboards_api.rb b/src/ruby_client/lib/emass_client/api/enterprise_sensor_based_hardware_resources_dashboards_api.rb index a762ba19..882a5225 100644 --- a/src/ruby_client/lib/emass_client/api/enterprise_sensor_based_hardware_resources_dashboards_api.rb +++ b/src/ruby_client/lib/emass_client/api/enterprise_sensor_based_hardware_resources_dashboards_api.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/api/enterprise_sensor_based_software_resources_dashboards_api.rb b/src/ruby_client/lib/emass_client/api/enterprise_sensor_based_software_resources_dashboards_api.rb index b79235f2..537224a6 100644 --- a/src/ruby_client/lib/emass_client/api/enterprise_sensor_based_software_resources_dashboards_api.rb +++ b/src/ruby_client/lib/emass_client/api/enterprise_sensor_based_software_resources_dashboards_api.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/api/enterprise_terms_conditions_dashboards_api.rb b/src/ruby_client/lib/emass_client/api/enterprise_terms_conditions_dashboards_api.rb index 6794f2fc..2b7e268f 100644 --- a/src/ruby_client/lib/emass_client/api/enterprise_terms_conditions_dashboards_api.rb +++ b/src/ruby_client/lib/emass_client/api/enterprise_terms_conditions_dashboards_api.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/api/enterprise_vulnerability_dashboards_api.rb b/src/ruby_client/lib/emass_client/api/enterprise_vulnerability_dashboards_api.rb index ca3d0016..b9fd0811 100644 --- a/src/ruby_client/lib/emass_client/api/enterprise_vulnerability_dashboards_api.rb +++ b/src/ruby_client/lib/emass_client/api/enterprise_vulnerability_dashboards_api.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/api/fisma_inventory_summary_dashboards_api.rb b/src/ruby_client/lib/emass_client/api/fisma_inventory_summary_dashboards_api.rb index d661a935..d64eb2ba 100644 --- a/src/ruby_client/lib/emass_client/api/fisma_inventory_summary_dashboards_api.rb +++ b/src/ruby_client/lib/emass_client/api/fisma_inventory_summary_dashboards_api.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/api/hardware_baseline_dashboards_api.rb b/src/ruby_client/lib/emass_client/api/hardware_baseline_dashboards_api.rb index 62a035de..06ce07cb 100644 --- a/src/ruby_client/lib/emass_client/api/hardware_baseline_dashboards_api.rb +++ b/src/ruby_client/lib/emass_client/api/hardware_baseline_dashboards_api.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 5e3ec543..cbcff90a 100644 --- a/src/ruby_client/lib/emass_client/api/milestones_api.rb +++ b/src/ruby_client/lib/emass_client/api/milestones_api.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 904f2e0c..2da84e77 100644 --- a/src/ruby_client/lib/emass_client/api/pac_api.rb +++ b/src/ruby_client/lib/emass_client/api/pac_api.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 f39043c3..2bed1fcc 100644 --- a/src/ruby_client/lib/emass_client/api/poam_api.rb +++ b/src/ruby_client/lib/emass_client/api/poam_api.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/api/ports_and_protocols_dashboards_api.rb b/src/ruby_client/lib/emass_client/api/ports_and_protocols_dashboards_api.rb index b3708e1e..63d669b5 100644 --- a/src/ruby_client/lib/emass_client/api/ports_and_protocols_dashboards_api.rb +++ b/src/ruby_client/lib/emass_client/api/ports_and_protocols_dashboards_api.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/api/privacy_compliance_dashboards_api.rb b/src/ruby_client/lib/emass_client/api/privacy_compliance_dashboards_api.rb index 90b6bb34..b56d2bf0 100644 --- a/src/ruby_client/lib/emass_client/api/privacy_compliance_dashboards_api.rb +++ b/src/ruby_client/lib/emass_client/api/privacy_compliance_dashboards_api.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 5bbe084c..db3603eb 100644 --- a/src/ruby_client/lib/emass_client/api/registration_api.rb +++ b/src/ruby_client/lib/emass_client/api/registration_api.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/api/software_baseline_dashboards_api.rb b/src/ruby_client/lib/emass_client/api/software_baseline_dashboards_api.rb index 4a2054b4..4f4c11db 100644 --- a/src/ruby_client/lib/emass_client/api/software_baseline_dashboards_api.rb +++ b/src/ruby_client/lib/emass_client/api/software_baseline_dashboards_api.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 dcbab3c8..af2bd8d5 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/api/system_a20_summary_dashboard_api.rb b/src/ruby_client/lib/emass_client/api/system_a20_summary_dashboard_api.rb index e821b6ae..a5bac57e 100644 --- a/src/ruby_client/lib/emass_client/api/system_a20_summary_dashboard_api.rb +++ b/src/ruby_client/lib/emass_client/api/system_a20_summary_dashboard_api.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/api/system_aa_summary_dashboard_api.rb b/src/ruby_client/lib/emass_client/api/system_aa_summary_dashboard_api.rb index 50ab539e..2c01e069 100644 --- a/src/ruby_client/lib/emass_client/api/system_aa_summary_dashboard_api.rb +++ b/src/ruby_client/lib/emass_client/api/system_aa_summary_dashboard_api.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/api/system_associations_dashboard_api.rb b/src/ruby_client/lib/emass_client/api/system_associations_dashboard_api.rb index 61aafd41..8d5d058b 100644 --- a/src/ruby_client/lib/emass_client/api/system_associations_dashboard_api.rb +++ b/src/ruby_client/lib/emass_client/api/system_associations_dashboard_api.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/api/system_conmon_integration_status_dashboard_api.rb b/src/ruby_client/lib/emass_client/api/system_conmon_integration_status_dashboard_api.rb index 4e4f6128..08a97e85 100644 --- a/src/ruby_client/lib/emass_client/api/system_conmon_integration_status_dashboard_api.rb +++ b/src/ruby_client/lib/emass_client/api/system_conmon_integration_status_dashboard_api.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/api/system_pl109_reporting_summary_dashboard_api.rb b/src/ruby_client/lib/emass_client/api/system_pl109_reporting_summary_dashboard_api.rb index 8c408f5f..6bc9b752 100644 --- a/src/ruby_client/lib/emass_client/api/system_pl109_reporting_summary_dashboard_api.rb +++ b/src/ruby_client/lib/emass_client/api/system_pl109_reporting_summary_dashboard_api.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 3f02b287..476d13cf 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/api/system_status_dashboard_api.rb b/src/ruby_client/lib/emass_client/api/system_status_dashboard_api.rb index bb44607c..c6071bb9 100644 --- a/src/ruby_client/lib/emass_client/api/system_status_dashboard_api.rb +++ b/src/ruby_client/lib/emass_client/api/system_status_dashboard_api.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 c86a98fd..9c57914b 100644 --- a/src/ruby_client/lib/emass_client/api/systems_api.rb +++ b/src/ruby_client/lib/emass_client/api/systems_api.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 a6057dbe..7dcd5f5c 100644 --- a/src/ruby_client/lib/emass_client/api/test_api.rb +++ b/src/ruby_client/lib/emass_client/api/test_api.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 c41dd81c..d9e4e170 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/api/threat_risks_dashboards_api.rb b/src/ruby_client/lib/emass_client/api/threat_risks_dashboards_api.rb index 2579f541..381cdab7 100644 --- a/src/ruby_client/lib/emass_client/api/threat_risks_dashboards_api.rb +++ b/src/ruby_client/lib/emass_client/api/threat_risks_dashboards_api.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/api/users_dashboard_api.rb b/src/ruby_client/lib/emass_client/api/users_dashboard_api.rb index 8a7b65d1..6bf21274 100644 --- a/src/ruby_client/lib/emass_client/api/users_dashboard_api.rb +++ b/src/ruby_client/lib/emass_client/api/users_dashboard_api.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 b8207916..87c4cb4a 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 fe5fe71a..8d52aba4 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/api_client.rb b/src/ruby_client/lib/emass_client/api_client.rb index 502a47a9..3a173767 100644 --- a/src/ruby_client/lib/emass_client/api_client.rb +++ b/src/ruby_client/lib/emass_client/api_client.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/api_error.rb b/src/ruby_client/lib/emass_client/api_error.rb index 9dd22cb2..e49593c9 100644 --- a/src/ruby_client/lib/emass_client/api_error.rb +++ b/src/ruby_client/lib/emass_client/api_error.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/configuration.rb b/src/ruby_client/lib/emass_client/configuration.rb index c06258d4..025a28df 100644 --- a/src/ruby_client/lib/emass_client/configuration.rb +++ b/src/ruby_client/lib/emass_client/configuration.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 5eb81cf1..20c4a3c4 100644 --- a/src/ruby_client/lib/emass_client/models/artifacts_get.rb +++ b/src/ruby_client/lib/emass_client/models/artifacts_get.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 573351f0..36f1a7c6 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 3b8917b0..2c90a97f 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 58e253d7..989113a2 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 3a62e3c7..c2dd6c2b 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 1617fe52..79957f89 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 0e4e774d..adc26056 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 01241561..beb028a0 100644 --- a/src/ruby_client/lib/emass_client/models/cac_get.rb +++ b/src/ruby_client/lib/emass_client/models/cac_get.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 8cbf3bf4..69ec447b 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 8cd8097c..d64675c1 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 a721e102..f8b769d2 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/models/cloud_resources_delete.rb b/src/ruby_client/lib/emass_client/models/cloud_resources_delete.rb index 18b6e006..5c97e003 100644 --- a/src/ruby_client/lib/emass_client/models/cloud_resources_delete.rb +++ b/src/ruby_client/lib/emass_client/models/cloud_resources_delete.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/models/cloud_resources_delete_body_inner.rb b/src/ruby_client/lib/emass_client/models/cloud_resources_delete_body_inner.rb index ec712c9a..d0453dfd 100644 --- a/src/ruby_client/lib/emass_client/models/cloud_resources_delete_body_inner.rb +++ b/src/ruby_client/lib/emass_client/models/cloud_resources_delete_body_inner.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/models/cloud_resources_post_delete.rb b/src/ruby_client/lib/emass_client/models/cloud_resources_post_delete.rb index 85a9a9e7..d93bd11e 100644 --- a/src/ruby_client/lib/emass_client/models/cloud_resources_post_delete.rb +++ b/src/ruby_client/lib/emass_client/models/cloud_resources_post_delete.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 7617465c..4cee55c4 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 0f1aff3c..b94b315f 100644 --- a/src/ruby_client/lib/emass_client/models/cmmc_get.rb +++ b/src/ruby_client/lib/emass_client/models/cmmc_get.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 2556c965..7d189c39 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 3aa07b08..ef525309 100644 --- a/src/ruby_client/lib/emass_client/models/connectivity_ccsd.rb +++ b/src/ruby_client/lib/emass_client/models/connectivity_ccsd.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/models/container_resources_delete_body_inner.rb b/src/ruby_client/lib/emass_client/models/container_resources_delete_body_inner.rb index 6ae2b6df..0117f622 100644 --- a/src/ruby_client/lib/emass_client/models/container_resources_delete_body_inner.rb +++ b/src/ruby_client/lib/emass_client/models/container_resources_delete_body_inner.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/models/containers_resources_post_delete.rb b/src/ruby_client/lib/emass_client/models/containers_resources_post_delete.rb index 18c00b63..8ec81b10 100644 --- a/src/ruby_client/lib/emass_client/models/containers_resources_post_delete.rb +++ b/src/ruby_client/lib/emass_client/models/containers_resources_post_delete.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/models/containers_response_delete.rb b/src/ruby_client/lib/emass_client/models/containers_response_delete.rb index 97e524e2..063b7b3b 100644 --- a/src/ruby_client/lib/emass_client/models/containers_response_delete.rb +++ b/src/ruby_client/lib/emass_client/models/containers_response_delete.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 a06ed6ea..a96ebe39 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 e19da541..e1e2485f 100644 --- a/src/ruby_client/lib/emass_client/models/controls_get.rb +++ b/src/ruby_client/lib/emass_client/models/controls_get.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 94d012fa..3adf82a9 100644 --- a/src/ruby_client/lib/emass_client/models/controls_put.rb +++ b/src/ruby_client/lib/emass_client/models/controls_put.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 ab20cea7..9309c702 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 c433c584..51a21bba 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/models/dashboard_mock_response.rb b/src/ruby_client/lib/emass_client/models/dashboard_mock_response.rb index ee4e1e07..19836066 100644 --- a/src/ruby_client/lib/emass_client/models/dashboard_mock_response.rb +++ b/src/ruby_client/lib/emass_client/models/dashboard_mock_response.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/models/dashboard_mock_response_pagination.rb b/src/ruby_client/lib/emass_client/models/dashboard_mock_response_pagination.rb index a9518787..3ba4eaa0 100644 --- a/src/ruby_client/lib/emass_client/models/dashboard_mock_response_pagination.rb +++ b/src/ruby_client/lib/emass_client/models/dashboard_mock_response_pagination.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 612a38cf..2f0b83cd 100644 --- a/src/ruby_client/lib/emass_client/models/definition_transitions.rb +++ b/src/ruby_client/lib/emass_client/models/definition_transitions.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 04d7f845..a8a7f651 100644 --- a/src/ruby_client/lib/emass_client/models/instances_transitions.rb +++ b/src/ruby_client/lib/emass_client/models/instances_transitions.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/models/milestone_response_delete.rb b/src/ruby_client/lib/emass_client/models/milestone_response_delete.rb index cef830a1..7c87d0e0 100644 --- a/src/ruby_client/lib/emass_client/models/milestone_response_delete.rb +++ b/src/ruby_client/lib/emass_client/models/milestone_response_delete.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 c158abcd..3596f518 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 69c56413..12a7a55e 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 184f9c9c..3316fec9 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 6bbc1235..0ccdf8b8 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 2b92adef..69f2a7ac 100644 --- a/src/ruby_client/lib/emass_client/models/milestones_get.rb +++ b/src/ruby_client/lib/emass_client/models/milestones_get.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 aa3e5103..71adb4d7 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 73c62822..456848a0 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 3bc6339c..c1c05a13 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 6b5f5590..86b6fc2b 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/models/mock_object.rb b/src/ruby_client/lib/emass_client/models/mock_object.rb index d7bbc94d..c00a756f 100644 --- a/src/ruby_client/lib/emass_client/models/mock_object.rb +++ b/src/ruby_client/lib/emass_client/models/mock_object.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 e6b06591..accb6e57 100644 --- a/src/ruby_client/lib/emass_client/models/pac_get.rb +++ b/src/ruby_client/lib/emass_client/models/pac_get.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 878eddf0..b2a09536 100644 --- a/src/ruby_client/lib/emass_client/models/pac_post.rb +++ b/src/ruby_client/lib/emass_client/models/pac_post.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 f5d39a06..f0b48531 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 4ec4adc3..688b3ed3 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 72d5bed1..b27f1e5e 100644 --- a/src/ruby_client/lib/emass_client/models/poam_get.rb +++ b/src/ruby_client/lib/emass_client/models/poam_get.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 14c715fa..26918ac5 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 7414e288..f7fc116f 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 1545bbef..6171c295 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 9ac8849b..a0ccef37 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 9cfa473f..2d1b566b 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 fbf5885e..7306003f 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 7b85a82d..a6d62eea 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/models/register.rb b/src/ruby_client/lib/emass_client/models/register.rb index c569f566..0476a2ea 100644 --- a/src/ruby_client/lib/emass_client/models/register.rb +++ b/src/ruby_client/lib/emass_client/models/register.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 7979b6b3..fef4bb5f 100644 --- a/src/ruby_client/lib/emass_client/models/register_data.rb +++ b/src/ruby_client/lib/emass_client/models/register_data.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 81a388cb..4763b831 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/models/response200.rb b/src/ruby_client/lib/emass_client/models/response200.rb index 326c4a3c..ad8cbfac 100644 --- a/src/ruby_client/lib/emass_client/models/response200.rb +++ b/src/ruby_client/lib/emass_client/models/response200.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/models/response201.rb b/src/ruby_client/lib/emass_client/models/response201.rb index e31ba5a1..ca4c7903 100644 --- a/src/ruby_client/lib/emass_client/models/response201.rb +++ b/src/ruby_client/lib/emass_client/models/response201.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 53a530bb..9ee59761 100644 --- a/src/ruby_client/lib/emass_client/models/response201_meta.rb +++ b/src/ruby_client/lib/emass_client/models/response201_meta.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/models/response400.rb b/src/ruby_client/lib/emass_client/models/response400.rb index 9f0294a1..b3ebad30 100644 --- a/src/ruby_client/lib/emass_client/models/response400.rb +++ b/src/ruby_client/lib/emass_client/models/response400.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 1bdad515..d4844afa 100644 --- a/src/ruby_client/lib/emass_client/models/response400_meta.rb +++ b/src/ruby_client/lib/emass_client/models/response400_meta.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/models/response401.rb b/src/ruby_client/lib/emass_client/models/response401.rb index d618a370..94c67de9 100644 --- a/src/ruby_client/lib/emass_client/models/response401.rb +++ b/src/ruby_client/lib/emass_client/models/response401.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 2ed220b0..395af3ff 100644 --- a/src/ruby_client/lib/emass_client/models/response401_meta.rb +++ b/src/ruby_client/lib/emass_client/models/response401_meta.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/models/response403.rb b/src/ruby_client/lib/emass_client/models/response403.rb index 62dce505..893ad4a5 100644 --- a/src/ruby_client/lib/emass_client/models/response403.rb +++ b/src/ruby_client/lib/emass_client/models/response403.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 19dd3170..ad353272 100644 --- a/src/ruby_client/lib/emass_client/models/response403_meta.rb +++ b/src/ruby_client/lib/emass_client/models/response403_meta.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/models/response404.rb b/src/ruby_client/lib/emass_client/models/response404.rb index 4acabb0b..581c97d4 100644 --- a/src/ruby_client/lib/emass_client/models/response404.rb +++ b/src/ruby_client/lib/emass_client/models/response404.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/models/response405.rb b/src/ruby_client/lib/emass_client/models/response405.rb index 14eb006d..d5d162cf 100644 --- a/src/ruby_client/lib/emass_client/models/response405.rb +++ b/src/ruby_client/lib/emass_client/models/response405.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 233c033d..280c8ac9 100644 --- a/src/ruby_client/lib/emass_client/models/response405_meta.rb +++ b/src/ruby_client/lib/emass_client/models/response405_meta.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/models/response411.rb b/src/ruby_client/lib/emass_client/models/response411.rb index 191cc62b..2a3ca3dd 100644 --- a/src/ruby_client/lib/emass_client/models/response411.rb +++ b/src/ruby_client/lib/emass_client/models/response411.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 75afcf85..9dd9ec8b 100644 --- a/src/ruby_client/lib/emass_client/models/response411_meta.rb +++ b/src/ruby_client/lib/emass_client/models/response411_meta.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/models/response490.rb b/src/ruby_client/lib/emass_client/models/response490.rb index 07ca3a00..2e3db7b4 100644 --- a/src/ruby_client/lib/emass_client/models/response490.rb +++ b/src/ruby_client/lib/emass_client/models/response490.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 cae0fab5..461492af 100644 --- a/src/ruby_client/lib/emass_client/models/response490_meta.rb +++ b/src/ruby_client/lib/emass_client/models/response490_meta.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/models/response500.rb b/src/ruby_client/lib/emass_client/models/response500.rb index f0899384..1a648c41 100644 --- a/src/ruby_client/lib/emass_client/models/response500.rb +++ b/src/ruby_client/lib/emass_client/models/response500.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 9ff15517..4929b013 100644 --- a/src/ruby_client/lib/emass_client/models/response500_meta.rb +++ b/src/ruby_client/lib/emass_client/models/response500_meta.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 aacd6e75..fa786b1b 100644 --- a/src/ruby_client/lib/emass_client/models/role_category.rb +++ b/src/ruby_client/lib/emass_client/models/role_category.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/models/roles.rb b/src/ruby_client/lib/emass_client/models/roles.rb index 402e4143..2d7f23e4 100644 --- a/src/ruby_client/lib/emass_client/models/roles.rb +++ b/src/ruby_client/lib/emass_client/models/roles.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/models/ssps.rb b/src/ruby_client/lib/emass_client/models/ssps.rb index 95c978ea..b210bb21 100644 --- a/src/ruby_client/lib/emass_client/models/ssps.rb +++ b/src/ruby_client/lib/emass_client/models/ssps.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/models/stage.rb b/src/ruby_client/lib/emass_client/models/stage.rb index eeeb8a77..b6f7d328 100644 --- a/src/ruby_client/lib/emass_client/models/stage.rb +++ b/src/ruby_client/lib/emass_client/models/stage.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/models/static_code_application_post.rb b/src/ruby_client/lib/emass_client/models/static_code_application_post.rb index 74d060f7..4b480f48 100644 --- a/src/ruby_client/lib/emass_client/models/static_code_application_post.rb +++ b/src/ruby_client/lib/emass_client/models/static_code_application_post.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 6009d253..38ea47c1 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 2730031a..39e7f1de 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 8b3c37a5..94abb40e 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 53f2cf2e..9cf30cdc 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 b115fe4e..c5f8b5c9 100644 --- a/src/ruby_client/lib/emass_client/models/success200_response.rb +++ b/src/ruby_client/lib/emass_client/models/success200_response.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 5ad6dae2..eae79d13 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 db9b5f42..b071fda8 100644 --- a/src/ruby_client/lib/emass_client/models/system_response.rb +++ b/src/ruby_client/lib/emass_client/models/system_response.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 daa7257d..7fcee988 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 a3d56ba4..dbe5b330 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 6a5b960d..d81553df 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/models/systems.rb b/src/ruby_client/lib/emass_client/models/systems.rb index bd37dccb..60b9808f 100644 --- a/src/ruby_client/lib/emass_client/models/systems.rb +++ b/src/ruby_client/lib/emass_client/models/systems.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 3253951e..ccd7020c 100644 --- a/src/ruby_client/lib/emass_client/models/systems_response.rb +++ b/src/ruby_client/lib/emass_client/models/systems_response.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/models/test.rb b/src/ruby_client/lib/emass_client/models/test.rb index c02c29f0..47965850 100644 --- a/src/ruby_client/lib/emass_client/models/test.rb +++ b/src/ruby_client/lib/emass_client/models/test.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 53f802b6..bb41b433 100644 --- a/src/ruby_client/lib/emass_client/models/test_data.rb +++ b/src/ruby_client/lib/emass_client/models/test_data.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 9fb02519..661fa7ad 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 64f6d5cb..fda9a6f8 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 35784310..b3a4b16c 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 32abb67c..2ba2a20c 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/models/users.rb b/src/ruby_client/lib/emass_client/models/users.rb index 072056a8..9cf7858e 100644 --- a/src/ruby_client/lib/emass_client/models/users.rb +++ b/src/ruby_client/lib/emass_client/models/users.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 0df2f89c..ff9d156e 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 9c00ecf1..b7495fa4 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 78bab975..2f7f92ea 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 c3545d73..d737dc25 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 473d2464..663d4ab5 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 b037cee0..ace9a31b 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 0ea62818..8db9f9b7 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/lib/emass_client/version.rb b/src/ruby_client/lib/emass_client/version.rb index 95a46ca5..96861fe5 100644 --- a/src/ruby_client/lib/emass_client/version.rb +++ b/src/ruby_client/lib/emass_client/version.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/api/artifacts_api_spec.rb b/src/ruby_client/spec/api/artifacts_api_spec.rb index 9bf03682..1ec80745 100644 --- a/src/ruby_client/spec/api/artifacts_api_spec.rb +++ b/src/ruby_client/spec/api/artifacts_api_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 4efccce6..7e2d127b 100644 --- a/src/ruby_client/spec/api/artifacts_export_api_spec.rb +++ b/src/ruby_client/spec/api/artifacts_export_api_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/api/cac_api_spec.rb b/src/ruby_client/spec/api/cac_api_spec.rb index 83a04fc1..15e14e7c 100644 --- a/src/ruby_client/spec/api/cac_api_spec.rb +++ b/src/ruby_client/spec/api/cac_api_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/api/cloud_resource_results_api_spec.rb b/src/ruby_client/spec/api/cloud_resource_results_api_spec.rb index 90cb5f80..d55f3106 100644 --- a/src/ruby_client/spec/api/cloud_resource_results_api_spec.rb +++ b/src/ruby_client/spec/api/cloud_resource_results_api_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 035b3f17..f1a7e277 100644 --- a/src/ruby_client/spec/api/cmmc_assessments_api_spec.rb +++ b/src/ruby_client/spec/api/cmmc_assessments_api_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/api/container_scan_results_api_spec.rb b/src/ruby_client/spec/api/container_scan_results_api_spec.rb index 01ec9359..0fd49992 100644 --- a/src/ruby_client/spec/api/container_scan_results_api_spec.rb +++ b/src/ruby_client/spec/api/container_scan_results_api_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/api/controls_api_spec.rb b/src/ruby_client/spec/api/controls_api_spec.rb index d9631cdf..7bfee588 100644 --- a/src/ruby_client/spec/api/controls_api_spec.rb +++ b/src/ruby_client/spec/api/controls_api_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/api/enterprise_artifacts_dashboards_api_spec.rb b/src/ruby_client/spec/api/enterprise_artifacts_dashboards_api_spec.rb index faaa70be..adc8eee1 100644 --- a/src/ruby_client/spec/api/enterprise_artifacts_dashboards_api_spec.rb +++ b/src/ruby_client/spec/api/enterprise_artifacts_dashboards_api_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/api/enterprise_poam_dashboards_api_spec.rb b/src/ruby_client/spec/api/enterprise_poam_dashboards_api_spec.rb index 5f3d4051..bf813b1e 100644 --- a/src/ruby_client/spec/api/enterprise_poam_dashboards_api_spec.rb +++ b/src/ruby_client/spec/api/enterprise_poam_dashboards_api_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/api/enterprise_security_controls_dashboards_api_spec.rb b/src/ruby_client/spec/api/enterprise_security_controls_dashboards_api_spec.rb index fd708d4d..7d20303b 100644 --- a/src/ruby_client/spec/api/enterprise_security_controls_dashboards_api_spec.rb +++ b/src/ruby_client/spec/api/enterprise_security_controls_dashboards_api_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/api/enterprise_sensor_based_hardware_resources_dashboards_api_spec.rb b/src/ruby_client/spec/api/enterprise_sensor_based_hardware_resources_dashboards_api_spec.rb index 9fc78857..d4240d3e 100644 --- a/src/ruby_client/spec/api/enterprise_sensor_based_hardware_resources_dashboards_api_spec.rb +++ b/src/ruby_client/spec/api/enterprise_sensor_based_hardware_resources_dashboards_api_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/api/enterprise_sensor_based_software_resources_dashboards_api_spec.rb b/src/ruby_client/spec/api/enterprise_sensor_based_software_resources_dashboards_api_spec.rb index a9b22814..316db66f 100644 --- a/src/ruby_client/spec/api/enterprise_sensor_based_software_resources_dashboards_api_spec.rb +++ b/src/ruby_client/spec/api/enterprise_sensor_based_software_resources_dashboards_api_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/api/enterprise_terms_conditions_dashboards_api_spec.rb b/src/ruby_client/spec/api/enterprise_terms_conditions_dashboards_api_spec.rb index 636e6248..52645ef3 100644 --- a/src/ruby_client/spec/api/enterprise_terms_conditions_dashboards_api_spec.rb +++ b/src/ruby_client/spec/api/enterprise_terms_conditions_dashboards_api_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/api/enterprise_vulnerability_dashboards_api_spec.rb b/src/ruby_client/spec/api/enterprise_vulnerability_dashboards_api_spec.rb index 35bd2538..d647c678 100644 --- a/src/ruby_client/spec/api/enterprise_vulnerability_dashboards_api_spec.rb +++ b/src/ruby_client/spec/api/enterprise_vulnerability_dashboards_api_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/api/fisma_inventory_summary_dashboards_api_spec.rb b/src/ruby_client/spec/api/fisma_inventory_summary_dashboards_api_spec.rb index fd83f943..a916fefc 100644 --- a/src/ruby_client/spec/api/fisma_inventory_summary_dashboards_api_spec.rb +++ b/src/ruby_client/spec/api/fisma_inventory_summary_dashboards_api_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/api/hardware_baseline_dashboards_api_spec.rb b/src/ruby_client/spec/api/hardware_baseline_dashboards_api_spec.rb index 7e171ab5..9dd907dc 100644 --- a/src/ruby_client/spec/api/hardware_baseline_dashboards_api_spec.rb +++ b/src/ruby_client/spec/api/hardware_baseline_dashboards_api_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/api/milestones_api_spec.rb b/src/ruby_client/spec/api/milestones_api_spec.rb index 6b08dfbc..83264932 100644 --- a/src/ruby_client/spec/api/milestones_api_spec.rb +++ b/src/ruby_client/spec/api/milestones_api_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/api/pac_api_spec.rb b/src/ruby_client/spec/api/pac_api_spec.rb index 68a082f9..22115ada 100644 --- a/src/ruby_client/spec/api/pac_api_spec.rb +++ b/src/ruby_client/spec/api/pac_api_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/api/poam_api_spec.rb b/src/ruby_client/spec/api/poam_api_spec.rb index 1f869be8..df008ca6 100644 --- a/src/ruby_client/spec/api/poam_api_spec.rb +++ b/src/ruby_client/spec/api/poam_api_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/api/ports_and_protocols_dashboards_api_spec.rb b/src/ruby_client/spec/api/ports_and_protocols_dashboards_api_spec.rb index 1a075fc4..5becac79 100644 --- a/src/ruby_client/spec/api/ports_and_protocols_dashboards_api_spec.rb +++ b/src/ruby_client/spec/api/ports_and_protocols_dashboards_api_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/api/privacy_compliance_dashboards_api_spec.rb b/src/ruby_client/spec/api/privacy_compliance_dashboards_api_spec.rb index b5baefa8..e33e8312 100644 --- a/src/ruby_client/spec/api/privacy_compliance_dashboards_api_spec.rb +++ b/src/ruby_client/spec/api/privacy_compliance_dashboards_api_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/api/registration_api_spec.rb b/src/ruby_client/spec/api/registration_api_spec.rb index c98820dc..22303858 100644 --- a/src/ruby_client/spec/api/registration_api_spec.rb +++ b/src/ruby_client/spec/api/registration_api_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/api/software_baseline_dashboards_api_spec.rb b/src/ruby_client/spec/api/software_baseline_dashboards_api_spec.rb index 61ca4b44..f05f932f 100644 --- a/src/ruby_client/spec/api/software_baseline_dashboards_api_spec.rb +++ b/src/ruby_client/spec/api/software_baseline_dashboards_api_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 fc09f60a..c2cb307e 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/api/system_a20_summary_dashboard_api_spec.rb b/src/ruby_client/spec/api/system_a20_summary_dashboard_api_spec.rb index 4bf3ef12..548e45f5 100644 --- a/src/ruby_client/spec/api/system_a20_summary_dashboard_api_spec.rb +++ b/src/ruby_client/spec/api/system_a20_summary_dashboard_api_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/api/system_aa_summary_dashboard_api_spec.rb b/src/ruby_client/spec/api/system_aa_summary_dashboard_api_spec.rb index ea3c508a..08618077 100644 --- a/src/ruby_client/spec/api/system_aa_summary_dashboard_api_spec.rb +++ b/src/ruby_client/spec/api/system_aa_summary_dashboard_api_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/api/system_associations_dashboard_api_spec.rb b/src/ruby_client/spec/api/system_associations_dashboard_api_spec.rb index ea84b015..2408beb1 100644 --- a/src/ruby_client/spec/api/system_associations_dashboard_api_spec.rb +++ b/src/ruby_client/spec/api/system_associations_dashboard_api_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/api/system_conmon_integration_status_dashboard_api_spec.rb b/src/ruby_client/spec/api/system_conmon_integration_status_dashboard_api_spec.rb index ea5888d8..9ce43e3a 100644 --- a/src/ruby_client/spec/api/system_conmon_integration_status_dashboard_api_spec.rb +++ b/src/ruby_client/spec/api/system_conmon_integration_status_dashboard_api_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/api/system_pl109_reporting_summary_dashboard_api_spec.rb b/src/ruby_client/spec/api/system_pl109_reporting_summary_dashboard_api_spec.rb index 472c4a5b..59fb35f1 100644 --- a/src/ruby_client/spec/api/system_pl109_reporting_summary_dashboard_api_spec.rb +++ b/src/ruby_client/spec/api/system_pl109_reporting_summary_dashboard_api_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 1f420da8..fe8d574f 100644 --- a/src/ruby_client/spec/api/system_roles_api_spec.rb +++ b/src/ruby_client/spec/api/system_roles_api_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/api/system_status_dashboard_api_spec.rb b/src/ruby_client/spec/api/system_status_dashboard_api_spec.rb index 8c823d22..fcc8544f 100644 --- a/src/ruby_client/spec/api/system_status_dashboard_api_spec.rb +++ b/src/ruby_client/spec/api/system_status_dashboard_api_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/api/systems_api_spec.rb b/src/ruby_client/spec/api/systems_api_spec.rb index c62ce571..ac3fce6a 100644 --- a/src/ruby_client/spec/api/systems_api_spec.rb +++ b/src/ruby_client/spec/api/systems_api_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/api/test_api_spec.rb b/src/ruby_client/spec/api/test_api_spec.rb index a615827b..5875b4c2 100644 --- a/src/ruby_client/spec/api/test_api_spec.rb +++ b/src/ruby_client/spec/api/test_api_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 6c8f37cd..6ce8cd5e 100644 --- a/src/ruby_client/spec/api/test_results_api_spec.rb +++ b/src/ruby_client/spec/api/test_results_api_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/api/threat_risks_dashboards_api_spec.rb b/src/ruby_client/spec/api/threat_risks_dashboards_api_spec.rb index 740ab741..cc0fe73b 100644 --- a/src/ruby_client/spec/api/threat_risks_dashboards_api_spec.rb +++ b/src/ruby_client/spec/api/threat_risks_dashboards_api_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/api/users_dashboard_api_spec.rb b/src/ruby_client/spec/api/users_dashboard_api_spec.rb index 32fb9268..2e839d26 100644 --- a/src/ruby_client/spec/api/users_dashboard_api_spec.rb +++ b/src/ruby_client/spec/api/users_dashboard_api_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 014c69c9..53f3b742 100644 --- a/src/ruby_client/spec/api/workflow_definitions_api_spec.rb +++ b/src/ruby_client/spec/api/workflow_definitions_api_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 1931b7a4..67c090f7 100644 --- a/src/ruby_client/spec/api/workflow_instances_api_spec.rb +++ b/src/ruby_client/spec/api/workflow_instances_api_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/api_client_spec.rb b/src/ruby_client/spec/api_client_spec.rb index 6b442491..9c8b4072 100644 --- a/src/ruby_client/spec/api_client_spec.rb +++ b/src/ruby_client/spec/api_client_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/configuration_spec.rb b/src/ruby_client/spec/configuration_spec.rb index e9c6513a..de365963 100644 --- a/src/ruby_client/spec/configuration_spec.rb +++ b/src/ruby_client/spec/configuration_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/artifacts_get_spec.rb b/src/ruby_client/spec/models/artifacts_get_spec.rb index 84b9c46e..df347275 100644 --- a/src/ruby_client/spec/models/artifacts_get_spec.rb +++ b/src/ruby_client/spec/models/artifacts_get_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 3c116daf..365ed8c0 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 cf9d1fbc..0592a4a5 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 976e6208..9cd36e4c 100644 --- a/src/ruby_client/spec/models/artifacts_response_del_spec.rb +++ b/src/ruby_client/spec/models/artifacts_response_del_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 6e40bfda..03402bc9 100644 --- a/src/ruby_client/spec/models/artifacts_response_get_spec.rb +++ b/src/ruby_client/spec/models/artifacts_response_get_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 19a96df2..40dba9f8 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 fb4ae118..7e3240c0 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/cac_get_spec.rb b/src/ruby_client/spec/models/cac_get_spec.rb index 3a483c07..359a6977 100644 --- a/src/ruby_client/spec/models/cac_get_spec.rb +++ b/src/ruby_client/spec/models/cac_get_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 b8244592..1e701fe0 100644 --- a/src/ruby_client/spec/models/cac_response_get_spec.rb +++ b/src/ruby_client/spec/models/cac_response_get_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 7c2cd8f9..fa0160bf 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 f820505e..7437cb0b 100644 --- a/src/ruby_client/spec/models/cac_response_post_spec.rb +++ b/src/ruby_client/spec/models/cac_response_post_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/cloud_resources_delete_body_inner_spec.rb b/src/ruby_client/spec/models/cloud_resources_delete_body_inner_spec.rb index 378c6a2c..734ab3f0 100644 --- a/src/ruby_client/spec/models/cloud_resources_delete_body_inner_spec.rb +++ b/src/ruby_client/spec/models/cloud_resources_delete_body_inner_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/cloud_resources_delete_spec.rb b/src/ruby_client/spec/models/cloud_resources_delete_spec.rb index 3a70a284..6e8aa40a 100644 --- a/src/ruby_client/spec/models/cloud_resources_delete_spec.rb +++ b/src/ruby_client/spec/models/cloud_resources_delete_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/cloud_resources_post_delete_spec.rb b/src/ruby_client/spec/models/cloud_resources_post_delete_spec.rb index 9c7ccf9e..bc417175 100644 --- a/src/ruby_client/spec/models/cloud_resources_post_delete_spec.rb +++ b/src/ruby_client/spec/models/cloud_resources_post_delete_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 851e3559..8b1b8b51 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/cmmc_get_spec.rb b/src/ruby_client/spec/models/cmmc_get_spec.rb index 0fbeb4e2..c8bd1b67 100644 --- a/src/ruby_client/spec/models/cmmc_get_spec.rb +++ b/src/ruby_client/spec/models/cmmc_get_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 ecd8e10c..68125d49 100644 --- a/src/ruby_client/spec/models/cmmc_response_get_spec.rb +++ b/src/ruby_client/spec/models/cmmc_response_get_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/connectivity_ccsd_spec.rb b/src/ruby_client/spec/models/connectivity_ccsd_spec.rb index 92e73e54..06f983ab 100644 --- a/src/ruby_client/spec/models/connectivity_ccsd_spec.rb +++ b/src/ruby_client/spec/models/connectivity_ccsd_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/container_resources_delete_body_inner_spec.rb b/src/ruby_client/spec/models/container_resources_delete_body_inner_spec.rb index 4a5bee55..a96878ec 100644 --- a/src/ruby_client/spec/models/container_resources_delete_body_inner_spec.rb +++ b/src/ruby_client/spec/models/container_resources_delete_body_inner_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/containers_resources_post_delete_spec.rb b/src/ruby_client/spec/models/containers_resources_post_delete_spec.rb index 237061ee..bb21f054 100644 --- a/src/ruby_client/spec/models/containers_resources_post_delete_spec.rb +++ b/src/ruby_client/spec/models/containers_resources_post_delete_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/containers_response_delete_spec.rb b/src/ruby_client/spec/models/containers_response_delete_spec.rb index 096f4ef0..a05a7946 100644 --- a/src/ruby_client/spec/models/containers_response_delete_spec.rb +++ b/src/ruby_client/spec/models/containers_response_delete_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 d0f030e1..6aa90473 100644 --- a/src/ruby_client/spec/models/containers_response_post_spec.rb +++ b/src/ruby_client/spec/models/containers_response_post_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/controls_get_spec.rb b/src/ruby_client/spec/models/controls_get_spec.rb index 70057dcb..e3dbad7c 100644 --- a/src/ruby_client/spec/models/controls_get_spec.rb +++ b/src/ruby_client/spec/models/controls_get_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/controls_put_spec.rb b/src/ruby_client/spec/models/controls_put_spec.rb index 4d3fcb0d..5427ae1b 100644 --- a/src/ruby_client/spec/models/controls_put_spec.rb +++ b/src/ruby_client/spec/models/controls_put_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 18da243b..2d45f8a3 100644 --- a/src/ruby_client/spec/models/controls_response_get_spec.rb +++ b/src/ruby_client/spec/models/controls_response_get_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 70c81c55..adac66a9 100644 --- a/src/ruby_client/spec/models/controls_response_put_spec.rb +++ b/src/ruby_client/spec/models/controls_response_put_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/dashboard_mock_response_pagination_spec.rb b/src/ruby_client/spec/models/dashboard_mock_response_pagination_spec.rb index f3c243b1..ccc7065b 100644 --- a/src/ruby_client/spec/models/dashboard_mock_response_pagination_spec.rb +++ b/src/ruby_client/spec/models/dashboard_mock_response_pagination_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/dashboard_mock_response_spec.rb b/src/ruby_client/spec/models/dashboard_mock_response_spec.rb index 6fe88cb9..615228f8 100644 --- a/src/ruby_client/spec/models/dashboard_mock_response_spec.rb +++ b/src/ruby_client/spec/models/dashboard_mock_response_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/definition_transitions_spec.rb b/src/ruby_client/spec/models/definition_transitions_spec.rb index 1917bccf..224311a0 100644 --- a/src/ruby_client/spec/models/definition_transitions_spec.rb +++ b/src/ruby_client/spec/models/definition_transitions_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/instances_transitions_spec.rb b/src/ruby_client/spec/models/instances_transitions_spec.rb index fb1e42a0..8fc56a92 100644 --- a/src/ruby_client/spec/models/instances_transitions_spec.rb +++ b/src/ruby_client/spec/models/instances_transitions_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/milestone_response_delete_spec.rb b/src/ruby_client/spec/models/milestone_response_delete_spec.rb index f064b354..8071220e 100644 --- a/src/ruby_client/spec/models/milestone_response_delete_spec.rb +++ b/src/ruby_client/spec/models/milestone_response_delete_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 7a26f1b9..dfe7cc26 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 f77c22ae..dcf3b462 100644 --- a/src/ruby_client/spec/models/milestone_response_get_spec.rb +++ b/src/ruby_client/spec/models/milestone_response_get_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 33edd724..821f4af2 100644 --- a/src/ruby_client/spec/models/milestone_response_post_spec.rb +++ b/src/ruby_client/spec/models/milestone_response_post_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 562ec0d3..b32ec6af 100644 --- a/src/ruby_client/spec/models/milestone_response_put_spec.rb +++ b/src/ruby_client/spec/models/milestone_response_put_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/milestones_get_spec.rb b/src/ruby_client/spec/models/milestones_get_spec.rb index 127ae44c..1c6e26bc 100644 --- a/src/ruby_client/spec/models/milestones_get_spec.rb +++ b/src/ruby_client/spec/models/milestones_get_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 ae2fdb11..16550efc 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 333594ac..33474157 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 01916098..4917844a 100644 --- a/src/ruby_client/spec/models/milestones_required_post_spec.rb +++ b/src/ruby_client/spec/models/milestones_required_post_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 754e98e2..8edd282e 100644 --- a/src/ruby_client/spec/models/milestones_required_put_spec.rb +++ b/src/ruby_client/spec/models/milestones_required_put_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/mock_object_spec.rb b/src/ruby_client/spec/models/mock_object_spec.rb index 248c8df2..4bf73ad4 100644 --- a/src/ruby_client/spec/models/mock_object_spec.rb +++ b/src/ruby_client/spec/models/mock_object_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/pac_get_spec.rb b/src/ruby_client/spec/models/pac_get_spec.rb index 22f3479c..577faed4 100644 --- a/src/ruby_client/spec/models/pac_get_spec.rb +++ b/src/ruby_client/spec/models/pac_get_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/pac_post_spec.rb b/src/ruby_client/spec/models/pac_post_spec.rb index bd584d15..cbcb8509 100644 --- a/src/ruby_client/spec/models/pac_post_spec.rb +++ b/src/ruby_client/spec/models/pac_post_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 cdf4a269..f8411ff2 100644 --- a/src/ruby_client/spec/models/pac_response_get_spec.rb +++ b/src/ruby_client/spec/models/pac_response_get_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 a96da7a8..9e089547 100644 --- a/src/ruby_client/spec/models/pac_response_post_spec.rb +++ b/src/ruby_client/spec/models/pac_response_post_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/poam_get_spec.rb b/src/ruby_client/spec/models/poam_get_spec.rb index 32de693d..34b926d2 100644 --- a/src/ruby_client/spec/models/poam_get_spec.rb +++ b/src/ruby_client/spec/models/poam_get_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 94a72d62..ffb8ebe6 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 4442f349..335f15f5 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 d6c7ec1a..a62aaef5 100644 --- a/src/ruby_client/spec/models/poam_response_delete_spec.rb +++ b/src/ruby_client/spec/models/poam_response_delete_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 8c5d8ae3..a37cb071 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 8020ae2b..0ed377b5 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 0d9ff303..67d526ae 100644 --- a/src/ruby_client/spec/models/poam_response_post_spec.rb +++ b/src/ruby_client/spec/models/poam_response_post_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 9833c708..e932ad3a 100644 --- a/src/ruby_client/spec/models/poam_response_put_spec.rb +++ b/src/ruby_client/spec/models/poam_response_put_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/register_data_spec.rb b/src/ruby_client/spec/models/register_data_spec.rb index 13671144..5d8910ac 100644 --- a/src/ruby_client/spec/models/register_data_spec.rb +++ b/src/ruby_client/spec/models/register_data_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/register_spec.rb b/src/ruby_client/spec/models/register_spec.rb index ce4efbcd..ae104f14 100644 --- a/src/ruby_client/spec/models/register_spec.rb +++ b/src/ruby_client/spec/models/register_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 82ffa802..b64427bd 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/response200_spec.rb b/src/ruby_client/spec/models/response200_spec.rb index 744e7a20..638c200a 100644 --- a/src/ruby_client/spec/models/response200_spec.rb +++ b/src/ruby_client/spec/models/response200_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/response201_meta_spec.rb b/src/ruby_client/spec/models/response201_meta_spec.rb index 4f0a9624..d9ac57a5 100644 --- a/src/ruby_client/spec/models/response201_meta_spec.rb +++ b/src/ruby_client/spec/models/response201_meta_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/response201_spec.rb b/src/ruby_client/spec/models/response201_spec.rb index 82f22785..922059b6 100644 --- a/src/ruby_client/spec/models/response201_spec.rb +++ b/src/ruby_client/spec/models/response201_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/response400_meta_spec.rb b/src/ruby_client/spec/models/response400_meta_spec.rb index 965def0e..650be8cb 100644 --- a/src/ruby_client/spec/models/response400_meta_spec.rb +++ b/src/ruby_client/spec/models/response400_meta_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/response400_spec.rb b/src/ruby_client/spec/models/response400_spec.rb index e13999af..081d1b83 100644 --- a/src/ruby_client/spec/models/response400_spec.rb +++ b/src/ruby_client/spec/models/response400_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/response401_meta_spec.rb b/src/ruby_client/spec/models/response401_meta_spec.rb index c312797f..3fd3c0a3 100644 --- a/src/ruby_client/spec/models/response401_meta_spec.rb +++ b/src/ruby_client/spec/models/response401_meta_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/response401_spec.rb b/src/ruby_client/spec/models/response401_spec.rb index 4ceadc90..def8d281 100644 --- a/src/ruby_client/spec/models/response401_spec.rb +++ b/src/ruby_client/spec/models/response401_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/response403_meta_spec.rb b/src/ruby_client/spec/models/response403_meta_spec.rb index c2051afd..e736fba2 100644 --- a/src/ruby_client/spec/models/response403_meta_spec.rb +++ b/src/ruby_client/spec/models/response403_meta_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/response403_spec.rb b/src/ruby_client/spec/models/response403_spec.rb index 00671468..2ed7dfe0 100644 --- a/src/ruby_client/spec/models/response403_spec.rb +++ b/src/ruby_client/spec/models/response403_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/response404_spec.rb b/src/ruby_client/spec/models/response404_spec.rb index bc7fc47c..dc548012 100644 --- a/src/ruby_client/spec/models/response404_spec.rb +++ b/src/ruby_client/spec/models/response404_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/response405_meta_spec.rb b/src/ruby_client/spec/models/response405_meta_spec.rb index 1e6401fb..dbaf1ac2 100644 --- a/src/ruby_client/spec/models/response405_meta_spec.rb +++ b/src/ruby_client/spec/models/response405_meta_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/response405_spec.rb b/src/ruby_client/spec/models/response405_spec.rb index 702ee61d..90954d82 100644 --- a/src/ruby_client/spec/models/response405_spec.rb +++ b/src/ruby_client/spec/models/response405_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/response411_meta_spec.rb b/src/ruby_client/spec/models/response411_meta_spec.rb index a1265cb3..29e723f1 100644 --- a/src/ruby_client/spec/models/response411_meta_spec.rb +++ b/src/ruby_client/spec/models/response411_meta_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/response411_spec.rb b/src/ruby_client/spec/models/response411_spec.rb index e44b1611..c7489ebc 100644 --- a/src/ruby_client/spec/models/response411_spec.rb +++ b/src/ruby_client/spec/models/response411_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/response490_meta_spec.rb b/src/ruby_client/spec/models/response490_meta_spec.rb index 2ffd946f..1efd30cd 100644 --- a/src/ruby_client/spec/models/response490_meta_spec.rb +++ b/src/ruby_client/spec/models/response490_meta_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/response490_spec.rb b/src/ruby_client/spec/models/response490_spec.rb index f8713c5e..b9f8731d 100644 --- a/src/ruby_client/spec/models/response490_spec.rb +++ b/src/ruby_client/spec/models/response490_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/response500_meta_spec.rb b/src/ruby_client/spec/models/response500_meta_spec.rb index 1b853231..b77617dd 100644 --- a/src/ruby_client/spec/models/response500_meta_spec.rb +++ b/src/ruby_client/spec/models/response500_meta_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/response500_spec.rb b/src/ruby_client/spec/models/response500_spec.rb index d940a5f3..d9cca1bd 100644 --- a/src/ruby_client/spec/models/response500_spec.rb +++ b/src/ruby_client/spec/models/response500_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/role_category_spec.rb b/src/ruby_client/spec/models/role_category_spec.rb index 44111bcd..b12a4475 100644 --- a/src/ruby_client/spec/models/role_category_spec.rb +++ b/src/ruby_client/spec/models/role_category_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/roles_spec.rb b/src/ruby_client/spec/models/roles_spec.rb index 714888a8..60816eba 100644 --- a/src/ruby_client/spec/models/roles_spec.rb +++ b/src/ruby_client/spec/models/roles_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/ssps_spec.rb b/src/ruby_client/spec/models/ssps_spec.rb index acb3ea60..3d9cccc9 100644 --- a/src/ruby_client/spec/models/ssps_spec.rb +++ b/src/ruby_client/spec/models/ssps_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/stage_spec.rb b/src/ruby_client/spec/models/stage_spec.rb index 65291cff..0e9d2c14 100644 --- a/src/ruby_client/spec/models/stage_spec.rb +++ b/src/ruby_client/spec/models/stage_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/static_code_application_post_spec.rb b/src/ruby_client/spec/models/static_code_application_post_spec.rb index eee9e8e2..4381ac0d 100644 --- a/src/ruby_client/spec/models/static_code_application_post_spec.rb +++ b/src/ruby_client/spec/models/static_code_application_post_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 616a1a4b..25ac38ed 100644 --- a/src/ruby_client/spec/models/static_code_post_spec.rb +++ b/src/ruby_client/spec/models/static_code_post_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 1d6b51b2..3735f232 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 7586dc02..25eb2437 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 156b7669..2174c912 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 6a4fe188..316bf585 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/success200_response_spec.rb b/src/ruby_client/spec/models/success200_response_spec.rb index d6f4ea3c..9ab9bb62 100644 --- a/src/ruby_client/spec/models/success200_response_spec.rb +++ b/src/ruby_client/spec/models/success200_response_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/system_response_spec.rb b/src/ruby_client/spec/models/system_response_spec.rb index fc697296..2a874350 100644 --- a/src/ruby_client/spec/models/system_response_spec.rb +++ b/src/ruby_client/spec/models/system_response_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 dde3f5af..15dfe235 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 e44a85e5..176a7acb 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 d531c5af..64f7b5f4 100644 --- a/src/ruby_client/spec/models/system_roles_response_spec.rb +++ b/src/ruby_client/spec/models/system_roles_response_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/systems_response_spec.rb b/src/ruby_client/spec/models/systems_response_spec.rb index 263d1679..0949321f 100644 --- a/src/ruby_client/spec/models/systems_response_spec.rb +++ b/src/ruby_client/spec/models/systems_response_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/systems_spec.rb b/src/ruby_client/spec/models/systems_spec.rb index 42e1df12..b0bbd2ae 100644 --- a/src/ruby_client/spec/models/systems_spec.rb +++ b/src/ruby_client/spec/models/systems_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/test_data_spec.rb b/src/ruby_client/spec/models/test_data_spec.rb index 5e36fdc6..833df9d2 100644 --- a/src/ruby_client/spec/models/test_data_spec.rb +++ b/src/ruby_client/spec/models/test_data_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 3a3fc528..78cceeb8 100644 --- a/src/ruby_client/spec/models/test_results_get_spec.rb +++ b/src/ruby_client/spec/models/test_results_get_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 3aad2613..a8d5c6b5 100644 --- a/src/ruby_client/spec/models/test_results_post_spec.rb +++ b/src/ruby_client/spec/models/test_results_post_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 d5befd99..88708a17 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 c326f1ef..8af64b70 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/test_spec.rb b/src/ruby_client/spec/models/test_spec.rb index a8c8d2d7..1b5ba254 100644 --- a/src/ruby_client/spec/models/test_spec.rb +++ b/src/ruby_client/spec/models/test_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/models/users_spec.rb b/src/ruby_client/spec/models/users_spec.rb index 44b36246..6d4a3caa 100644 --- a/src/ruby_client/spec/models/users_spec.rb +++ b/src/ruby_client/spec/models/users_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 3f7cd74b..9a3097bd 100644 --- a/src/ruby_client/spec/models/workflow_definition_get_spec.rb +++ b/src/ruby_client/spec/models/workflow_definition_get_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 2dd44789..4df20910 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 a426ec51..a066f8e1 100644 --- a/src/ruby_client/spec/models/workflow_instance_get_spec.rb +++ b/src/ruby_client/spec/models/workflow_instance_get_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 4310f620..34596400 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 02cd5f58..812aa87d 100644 --- a/src/ruby_client/spec/models/workflow_instances_get_spec.rb +++ b/src/ruby_client/spec/models/workflow_instances_get_spec.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 36e292f3..bde0be76 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil 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 3ecad9fe..bcfbd01b 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 @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/ruby_client/spec/spec_helper.rb b/src/ruby_client/spec/spec_helper.rb index 4a00b52a..9e614c27 100644 --- a/src/ruby_client/spec/spec_helper.rb +++ b/src/ruby_client/spec/spec_helper.rb @@ -1,7 +1,7 @@ =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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/typescript_client/api.ts b/src/typescript_client/api.ts index 3a41f9ea..59b49b0e 100644 --- a/src/typescript_client/api.ts +++ b/src/typescript_client/api.ts @@ -2,7 +2,7 @@ /* eslint-disable */ /** * 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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 * Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/typescript_client/base.ts b/src/typescript_client/base.ts index 2b50574e..ea50864d 100644 --- a/src/typescript_client/base.ts +++ b/src/typescript_client/base.ts @@ -2,7 +2,7 @@ /* eslint-disable */ /** * 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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 * Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/typescript_client/common.ts b/src/typescript_client/common.ts index 04d303b9..30e477bd 100644 --- a/src/typescript_client/common.ts +++ b/src/typescript_client/common.ts @@ -2,7 +2,7 @@ /* eslint-disable */ /** * 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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 * Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/typescript_client/configuration.ts b/src/typescript_client/configuration.ts index ffeee6be..686b7bbc 100644 --- a/src/typescript_client/configuration.ts +++ b/src/typescript_client/configuration.ts @@ -2,7 +2,7 @@ /* eslint-disable */ /** * 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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 * Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil diff --git a/src/typescript_client/index.ts b/src/typescript_client/index.ts index f19f31a0..8a635baa 100644 --- a/src/typescript_client/index.ts +++ b/src/typescript_client/index.ts @@ -2,7 +2,7 @@ /* eslint-disable */ /** * 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` POST endpoint to register the client certificate. The endpoint returns the user `api-key`. BOHA

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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 Enterprise Mission 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` POST endpoint to register the client certificate. The endpoint call returns the user `api-key`.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-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.12 * Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil