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

Empty TAXII Ingester User Reverts to Previous User instead of System #4813

Closed
zhantt1 opened this issue Oct 30, 2023 · 1 comment · Fixed by #4834
Closed

Empty TAXII Ingester User Reverts to Previous User instead of System #4813

zhantt1 opened this issue Oct 30, 2023 · 1 comment · Fixed by #4834
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)

Comments

@zhantt1
Copy link

zhantt1 commented Oct 30, 2023

Description

The "User responsible for data creation (empty = System)" reverts to the previously set user when changing the field blank. There doesn't appear to be a way to set the User back to "System".

Environment

  1. OS (where OpenCTI server runs): Ubuntu 22.04
  2. OpenCTI version: 5.11.12
  3. OpenCTI client: frontend
  4. Other environment details:

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Create a TAXII Ingester. Set the user to an existing user.
  2. Click Update
  3. Set the user field to blank and hit the "X" to close the UI element
  4. Hit Update again to view the User field and notice that the value is no longer blank or set to System. It is the previous user.

Expected Output

When the User field is blank, the value becomes System.

Actual Output

The User field becomes the previous user value.

Screenshots (optional)

Changing value to empty:
image

Value after change (reverted to previous user "admin"):
image

@helene-nguyen
Copy link
Member

Hi @zhantt1,

I open a PR to fix it, you can follow it on the link below:

#4834

@helene-nguyen helene-nguyen added the solved use to identify issue that has been solved (must be linked to the solving PR) label Nov 8, 2023
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
3 participants