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

Capabilities settings do not work correctly with the Connectors section #6329

Closed
rattat0r opened this issue Mar 13, 2024 · 1 comment
Closed
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

@rattat0r
Copy link

Description

The user has the "Access connectors" right enabled, but the "Access administration" right is disabled.
In this case, he cannot get to the "data/ingestion/connectors" section from the sidebar, since the "ingestion" section is not displayed without the "Access administration" right.
Direct access via the link http://[ip]:8080/dashboard/data/ingestion/connectors gives access to the section with connectors, but it is impossible to get there from the sidebar.

Environment

  1. OS: Ubuntu 20.04.6
  2. OpenCTI version: OpenCTI 6.0.4
  3. OpenCTI client: frontend

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Enable the "Access connectors" right and disable the "Access administration" right for the user.
    image
  2. The "Ingestion" section has disappeared from the sidebar. It is impossible to go to the connectors section through the side panel.
    image
  3. Direct link access works.
    image

Expected Output

A section with connectors is available in the sidebar if the "Access connectors" right is enabled.

Is it possible to hide inaccessible sections directly in this area?
image

Actual Output

When the "Access administration" right is disabled, the "Data/Ingestion" section, in which the section with connectors was located, disappears.

@rattat0r rattat0r added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Mar 13, 2024
@SamuelHassine SamuelHassine added this to the Release 6.0.7 milestone Mar 13, 2024
@jborozco jborozco removed the needs triage use to identify issue needing triage from Filigran Product team label Mar 14, 2024
@SouadHadjiat SouadHadjiat self-assigned this Mar 14, 2024
@Jipegien Jipegien modified the milestones: Release 6.0.7, Release 6.0.8 Mar 14, 2024
@SouadHadjiat
Copy link
Member

solved with #6340

@SouadHadjiat SouadHadjiat added the solved use to identify issue that has been solved (must be linked to the solving PR) label Mar 14, 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

5 participants