POST request is not working as expected

[venkataveera]

Describe the problem
System Security Plan's POST request is not working as explained in the documentation scenarios: https://docs.oscal.io/docs/scenarios

POST: http://localhost:8080/oscal/v1/system-security-plan/

Request:
{ "system-security-plan-list": [ { "file-id": "ssp-8675309", "title": "Sample System's SSP", "published": "2024-08-14T11:20:00Z", "last-modified": "2024-08-14T11:20:00Z", "version": "1.0", "oscal-version": "1.1.1" } ] }

Refer the below scenario listed on the documentation scenarios: https://docs.oscal.io/docs/scenarios

`Deliver an SSP With Attachments
An SSP author delivers an OSCAL-based SSP to the ISSO's office for adjudication. The SSP is in OSCAL JSON format. It includes a boundary diagram attachment (Boundary.pdf) in the resources with a UUID value of 2ba7db9b-4603-4574-8eb2-93a447dbcd29l

Client: OSCAL-based SSP Authoring Tool
Server: CISO's GRC Repository

Client sends the SSP to the CISO's GRC Repository
Client -> Server: POST https://example.com/system-security-plan (HTTP Headers: Access Token, Content-type: application/json)(Payload: oscal_ssp.json)
Server verifies the access token was create-new permissions.
Server assigns a unique file identifier ("file-id": "ssp-8675309").
Server stores the SSP and associates the file-id with it
Server -> Client: SSP list entry that includes file-id, title, version, last-modified and other metadata (JSON).`

[pjavan]

@venkataveera thank you for posting the issue. A little over a month ago, we announced updates to the API Specification, with changes that included attachment handling.

The initial implementation was a starting point, intended to stay in line with the specification through contributions with the community. Future updates will continue to be made to the Specification and if enough interest exists, we will revisit an implementation "refresh".

Would love to hear from others on this.