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

Access denied despite capabilities #5856

Closed
Lhorus6 opened this issue Feb 7, 2024 · 1 comment
Closed

Access denied despite capabilities #5856

Lhorus6 opened this issue Feb 7, 2024 · 1 comment
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

@Lhorus6
Copy link

Lhorus6 commented Feb 7, 2024

Description

This error appears in the context of data segregation by organization

If I am not part of the Platform main organization, I get an "forbidden access" error despite the fact that I have the capabilities to enrich the data (see screenshot to look the full configuration)

Environment

OCTI 5.12.29

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Org A as Platform main organization
  2. User B part of Org B
  3. User B with read/write/update access on knowledge + enrich capabilities
  4. User B create an IPv4 not existing in the platform (ensure this by looking in the platform with a user who has full access)
  5. Try to enrich the IPv4 with user B
    -> "forbidden access" error

Screenshots

Screenshots

Platform main organization (Org A)

main_org

User B config

user_org

Config of the User B's Group

group_config

Config of the User B's Role

role_config

Error raised

forbidden_access_to_enrich

@Lhorus6 Lhorus6 added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Feb 7, 2024
@Jipegien Jipegien removed the needs triage use to identify issue needing triage from Filigran Product team label Feb 8, 2024
@SamuelHassine SamuelHassine added this to the Release 6.0.0 milestone Feb 8, 2024
@aHenryJard aHenryJard self-assigned this Feb 9, 2024
@richard-julien richard-julien self-assigned this Feb 16, 2024
@richard-julien
Copy link
Member

Will be handled by #6042

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

5 participants