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

Hygiene connector displays user's name for enrichment actions #5842

Closed
NiQuintin opened this issue Feb 6, 2024 · 5 comments
Closed

Hygiene connector displays user's name for enrichment actions #5842

NiQuintin opened this issue Feb 6, 2024 · 5 comments
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

@NiQuintin
Copy link

NiQuintin commented Feb 6, 2024

Description

When creating an observable, the Hygiene connector seems to be using certain user's name for enriching the observable (not necessarily the name of the creator, it may be a completely different user).

Environment

OpenCTI 5.12.29

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Choose a domain name for instance here and create it in the OCTI instance
  2. The hygiene connector will "impersonate" a user to replace the score, add hygiene to the label and add references.

Expected Output

Connector must display its own name for enrichment actions.

Actual Output

The connector impersonates certain users to display the origin of the enrichment.

Additional information

Example here: https://testing.octi.staging.filigran.io/dashboard/observations/observables/e9adde24-4e07-428e-9173-0e30cfc5404a

Screenshots (optional)

image

@NiQuintin NiQuintin added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Feb 6, 2024
@yassine-ouaamou
Copy link
Member

@Jipegien Jipegien removed the needs triage use to identify issue needing triage from Filigran Product team label Feb 7, 2024
@Jipegien
Copy link
Member

Jipegien commented Feb 7, 2024

@helene-nguyen & @Megafredo can you take a look when available ?

@helene-nguyen
Copy link
Member

Yes, we will take a look @Jipegien :)

@SamuelHassine SamuelHassine added this to the Release 6.0.0 milestone Feb 8, 2024
@labo-flg labo-flg assigned labo-flg and unassigned labo-flg Feb 8, 2024
@labo-flg
Copy link
Member

I let you guys do it @helene-nguyen or @Megafredo ;)

@richard-julien
Copy link
Member

Will be handled by #6042

@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Mar 26, 2024
@SamuelHassine SamuelHassine added this to the Release 6.0.9 milestone Mar 26, 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

8 participants