=begin #Enterprise Mission Assurance Support Service (eMASS) #The Enterprise Mission Assurance Support Service (eMASS) Representational State Transfer (REST) Application Programming Interface (API) enables users to perform assessments and complete actions associated with system records. The `emasser` is a command-line interface (CLI) tool that implements all of the eMASS endpoints defined in the eMASS REST API v3.2, dated October 21, 2021.

Register CLI
New users will need to register an API key with the eMASS development team prior to accessing the site for the first time. The eMASS REST API requires a client certificate (SSL/TLS, DoD PKI only) where {url}/api/register (POST) is used to register the client certificate.

Every call to the eMASS REST API will require the use of the agreed upon public key certificate and API key. The API key must be provided in the request header for all endpoint calls (api-key). If the service receives an untrusted certificate or API key, a 401 error response code will be returned along with an error message.

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

Approve API Client for Actionable Requests
Users are required to log-in to eMASS and grant permissions for a client to update data within eMASS on their behalf. This is only required for actionable requests (PUT, POST, DELETE). The Registration Endpoint and all GET requests can be accessed without completing this process with the correct permissions. Please note that leaving a field parameter blank (for PUT/POST requests) has the potential to clear information in the active eMASS records. To establish an account with eMASS and/or acquire an api-key/user-uid, contact one of the listed POC: OpenAPI spec version: v3.2 Contact: disa.meade.id.mbx.emass-tier-iii-support@mail.mil Generated by: https://github.com/swagger-api/swagger-codegen.git Swagger Codegen version: 3.0.26 =end require 'spec_helper' require 'json' # Unit tests for SwaggerClient::POAMApi # Automatically generated by swagger-codegen (github.com/swagger-api/swagger-codegen) # Please update as you see appropriate describe 'POAMApi' do before do # run before each test @instance = SwaggerClient::POAMApi.new end after do # run after each test end describe 'test an instance of POAMApi' do it 'should create an instance of POAMApi' do expect(@instance).to be_instance_of(SwaggerClient::POAMApi) end end # unit tests for add_poam_by_system_id # Add one or many POA&M items in a system # Add a POA&M for given `systemId`<br> **Request Body Required Fields** - `status` - `vulnerabilityDescription` - `sourceIdentVuln` - `pocOrganization` - `resources` **Note**<br /> 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.<br> `pocFirstName`, `pocLastName`, `pocPhoneNumber`<br /> # @param body Update an existing control by Id # @param system_id **System Id**: The unique system record identifier. # @param [Hash] opts the optional parameters # @return [PoamResponsePost] describe 'add_poam_by_system_id test' do it 'should work' do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for delete_poam # Remove one or many POA&M items in a system # Remove the POA&M matching `systemId` path parameter and `poamId` query parameter<br> # @param body Delete the given POA&M Id # @param system_id **System Id**: The unique system record identifier. # @param [Hash] opts the optional parameters # @return [PoamResponseDelete] describe 'delete_poam test' do it 'should work' do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for get_system_poams # Get one or many POA&M items in a system # Returns system(s) containing POA&M items for matching parameters. # @param system_id **System Id**: The unique system record identifier. # @param [Hash] opts the optional parameters # @option opts [String] :scheduled_completion_date_start **Date Started**: Filter query by the scheduled completion start date (Unix date format). # @option opts [String] :scheduled_completion_date_end **Date Ended**: Filter query by the scheduled completion start date (Unix date format). # @option opts [String] :control_acronyms **System Acronym**: Filter query by given system acronym (single or comma separated). # @option opts [String] :ccis **CCI System**: Filter query by Control Correlation Identifiers (CCIs). # @option opts [BOOLEAN] :system_only **Systems Only**: Indicates that only system(s) information is retrieved. # @return [PoamResponseGet] describe 'get_system_poams test' do it 'should work' do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for get_system_poams_by_poam_id # Get POA&M item by ID in a system # Returns system(s) containing POA&M items for matching parameters. # @param system_id **System Id**: The unique system record identifier. # @param poam_id **POA&M Id**: The unique POA&M record identifier. # @param [Hash] opts the optional parameters # @return [PoamResponseGet] describe 'get_system_poams_by_poam_id test' do it 'should work' do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end # unit tests for update_poam_by_system_id # Update one or many POA&M items in a system # Update a POA&M for given `systemId`<br> **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.<br> `pocOrganization`, `pocFirstName`, `pocLastName`, `pocEmail`, `pocPhoneNumber`<br /> - To delete a milestone through the POA&M PUT the field `isActive` must be set to `false`: `isActive=false`. # @param body Update an existing control by Id # @param system_id **System Id**: The unique system record identifier. # @param [Hash] opts the optional parameters # @return [PoamResponsePut] describe 'update_poam_by_system_id test' do it 'should work' do # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers end end end