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.

Sign up for GitHub

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

Jump to bottom

Observable of type Directory is not correctly formatted #1098

Closed
little-roach opened this issue Feb 18, 2021 · 0 comments
Closed

Observable of type Directory is not correctly formatted #1098

little-roach opened this issue Feb 18, 2021 · 0 comments
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
Release 4.2.4

Comments

@little-roach
Copy link
Contributor

Description

No matter input Observable of type Directory by Web page or Connector ImportFileStix2, OpenCTI return error message "Observable of type Directory is not correctly formatted", even in demo system( https://demo.opencti.io/ )

Environment

  1. OS: Ubuntu 16.4, etc.
  2. OpenCTI version: 4.0.7 or 4.2.3(demo)
  3. OpenCTI client: frontend/ python
  4. Other environment details:

Reproducible Steps

Scene 1: Input Observable of type Directory by Web page

Scene 2: Import STIX2 File by Conenctor ImportFileStix2

Expected Output

Success import Observable data of type Directory

Actual Output

Observable of type Directory is not correctly formatted

Directory_observable

Directory_observable_by_connector
@SamuelHassine SamuelHassine added the bug use for describing something not working as expected label Feb 18, 2021
SamuelHassine pushed a commit that referenced this issue Feb 19, 2021
[api] Remove regex check for directory, any char allowed (#1098)
156fdb5
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Feb 19, 2021
@SamuelHassine SamuelHassine added this to the Release 4.2.4 milestone Feb 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
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
Milestone
Release 4.2.4
Development

No branches or pull requests
2 participants
@SamuelHassine @little-roach