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

Requesting creator through log fail if the action was executed by SYSTEM_ADMIN #707

Closed
richard-julien opened this issue May 15, 2020 · 0 comments
Closed

Requesting creator through log fail if the action was executed by SYSTEM_ADMIN #707

richard-julien opened this issue May 15, 2020 · 0 comments
Assignees
@SamuelHassine
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 3.3.0

Comments

@richard-julien
Copy link
Member

Description

With the new log system we create an history of every actions, user creation too. But when a user login through LDAP, a system user create the user. Unfortunately this system user doesnt exists in the history system, so the resolution fail when we try to display the creation of this user.

Environment

OpenCTI version: 3.2.2

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Log through ldap
  2. Go to list of persons screen
  3. Try to see your detail

Expected Output

Your person definition with a creator named "system" or "opencti"

Actual Output

Crash
@richard-julien richard-julien added the bug use for describing something not working as expected label May 15, 2020
@richard-julien richard-julien added this to the Release 3.3.0 milestone May 15, 2020
SamuelHassine pushed a commit that referenced this issue May 24, 2020
[api] Fix empty creator and return system user (#707)
741ed65
SamuelHassine pushed a commit that referenced this issue May 24, 2020
[api] Fix empty creator and return system user (#707)
dd4b7e2
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label May 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@SamuelHassine SamuelHassine

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 3.3.0
Development

No branches or pull requests
2 participants
@richard-julien @SamuelHassine