Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot add Data Component through contextual component #6816

Closed
Bonsai8863 opened this issue Apr 25, 2024 · 1 comment
Closed

Cannot add Data Component through contextual component #6816

Bonsai8863 opened this issue Apr 25, 2024 · 1 comment
Assignees
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@Bonsai8863
Copy link
Contributor

Description

On an Attack Pattern entity view, click the plus icon next to 'Data components'. Click on a data component in the drawer and nothing happens.

Environment

  1. OS (where OpenCTI server runs): Mac OS Sonoma 14.4.1
  2. OpenCTI version: 6.0.10
  3. OpenCTI client: frontend

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Have system running with at least one Attack Pattern and one Data component
  2. Navigate to an Attack Pattern entity
  3. Click the plus icon next to 'Data components'
  4. Click on a data component in the drawer that appears

Expected Output

The clicked data component's icon should be replaced with a blue check mark and it should appear on the attack pattern's entity view.

Actual Output

Nothing happens: No logs in console or from graphql backend.

On page refresh it appears the relationship was created linking the Attack Pattern to the selected Data Component, but the Data Component still does not appear under the Details section. I've tried adding Data Components after deleting the relationships to no avail.

Screenshots (optional)

Screen.Recording.2024-04-25.at.11.42.11.AM.mov
@Bonsai8863 Bonsai8863 added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Apr 25, 2024
@Bonsai8863
Copy link
Contributor Author

The contextual Data Component add on Data Sources also appears to fail, but this time with an error. We get the following toast:
image

and the following error in the backend:

{
  "category": "APP",
  "errors": [
    {
      "attributes": { "genre": "TECHNICAL", "http_status": 500 },
      "message": "input.find is not a function",
      "name": "UNKNOWN_ERROR",
      "stack": "UNKNOWN_ERROR: input.find is not a function\n    at error (/path/to/opencti/opencti-platform/opencti-graphql/src/config/errors.js:8:10)\n    at UnknownError (/path/to/opencti/opencti-platform/opencti-graphql/src/config/errors.js:76:47)\n    at Object._logWithError (/path/to/opencti/opencti-platform/opencti-graphql/src/config/conf.js:331:23)\n    at Object.error (/path/to/opencti/opencti-platform/opencti-graphql/src/config/conf.js:341:48)\n    at Object.willSendResponse (/path/to/opencti/opencti-platform/opencti-graphql/src/graphql/loggerPlugin.js:119:20)\n    at processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at async Promise.all (index 1)\n    at sendResponse (/path/to/opencti/opencti-platform/opencti-graphql/node_modules/apollo-server-core/src/requestPipeline.ts:530:5)\n    at processHTTPRequest (/path/to/opencti/opencti-platform/opencti-graphql/node_modules/apollo-server-core/src/runHttpQuery.ts:437:24)"
    },
    {
      "message": "input.find is not a function",
      "name": "TypeError",
      "stack": "TypeError: input.find is not a function\n    at stixDomainObjectEditField (/path/to/opencti/opencti-platform/opencti-graphql/src/domain/stixDomainObject.js:205:30)\n    at processTicksAndRejections (node:internal/process/task_queues:95:5)\n    at dataSourceDataComponentAdd (/path/to/opencti/opencti-platform/opencti-graphql/src/modules/dataSource/dataSource-domain.ts:33:3)"
    }
  ],
  "inner_relation_creation": 0,
  "level": "error",
  "message": "Platform unmanaged direct error",
  "operation": "AddDataComponentsLinesToDataSourceRelationAddMutation",
  "operation_query": "mutation AddDataComponentsLinesToDataSourceRelationAddMutation($id:ID!$dataComponentId:ID!){dataSourceDataComponentAdd(id:$id dataComponentId:$dataComponentId){...DataSourceDataComponents_dataSource id}}fragment DataSourceDataComponents_dataSource on DataSource{id name parent_types entity_type dataComponents{edges{node{id parent_types name description}}}}",
  "size": 102,
  "time": 4,
  "timestamp": "2024-04-25T16:03:03.165Z",
  "type": "WRITE_ERROR",
  "user": {
    "group_ids": ["ede27053-615b-418d-8a72-1adf5c1e3ea6"],
    "ip": "::1",
    "organization_ids": [],
    "referer": "http://localhost:4000/dashboard/techniques/data_sources/45ada5f8-4f19-4c9a-b813-6e1613475843",
    "socket": "query",
    "user_id": "88ec0c6a-13ce-5e39-b486-354fe4a7084f",
    "user_metadata": {}
  },
  "variables": {
    "dataComponentId": "67ff9302-70f2-42e8-a5f0-fd386f92beda",
    "id": "45ada5f8-4f19-4c9a-b813-6e1613475843"
  },
  "version": "6.0.10"
}

@nino-filigran nino-filigran removed the needs triage use to identify issue needing triage from Filigran Product team label Apr 26, 2024
@SarahBocognano SarahBocognano self-assigned this Apr 26, 2024
@SamuelHassine SamuelHassine added this to the Release 6.0.11 milestone Apr 26, 2024
@SarahBocognano SarahBocognano added the solved use to identify issue that has been solved (must be linked to the solving PR) label May 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

No branches or pull requests

4 participants