mitre-attack / mitre-attack/attack-workbench-rest-api
how to write data via rest-api at port 3000
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 57
- Forks
- 18
- Avg merge
- 6m
- Merged PRs (30d)
- 2
Description
I am trying to add a new software via localhost:3000, with a problem "401 Unauthorized"
When I use name 'navigator' with read-only, I can get the software data. I tried three accounts and go through the config file within the project, there are only 3 service roles "read-only", "stix-export","collection-manager".
How can I do the post operation? or is there anyother serviceRole with write permission to support 'Post' ?
rest-api-service-confg.json is set as follows:
{
"serviceAuthn": {
"challengeApikey": {
"enable": true,
"serviceAccounts": [
{
"name": "collection-manager",
"apikey": "sample-key",
"serviceRole": "collection-manager"
}
]
},
"basicApikey": {
"enable": true,
"serviceAccounts": [
{
"name": "navigator",
"apikey": "sample-key-1",
"serviceRole": "read-only"
},
{
"name": "apikey-test-service",
"apikey": "sample-key-2",
"serviceRole": "stix-export"
},
{
"name": "collection-manager",
"apikey": "sample-key-2",
"serviceRole": "collection-manager"
}
]
}
}
}
log:
2025-09-19 11:22:16 2025-09-19T03:22:16.647Z [HTTP] GET /api/software 200 90.058 ms - -
2025-09-19 11:22:16 2025-09-19T03:22:16.699Z [HTTP] POST /api/software 401 16.854 ms - 14
2025-09-19 11:22:16 2025-09-19T03:22:16.707Z [HTTP] POST /api/software 401 3.321 ms - 14
2025-09-19 11:22:16 2025-09-19T03:22:16.713Z [HTTP] POST /api/software 401 1.281 ms - 14
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with rest-api-service-confg.json and the POST /api/software request described in the issue, then inspect the REST API authentication and service-role documentation or entry points. Done means the supported write-authentication path and required service role are clearly documented, with the reported 401 scenario addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, authentication, authorization
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100