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

UI Display of connectors - Not showing connectors after page cut-off. #703

Closed
cvdsouza opened this issue May 13, 2020 · 0 comments
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

@cvdsouza
Copy link

Description

Display of list of connectors at /dashboard/data/connectors doesn't show the full list. It seems that on the front-end I'm not able to scroll through the list of the indicators after they fill the page.

Environment

  1. OS (where OpenCTI server runs): Ubuntu 18.04.
  2. OpenCTI version: 3.2.2
  3. OpenCTI client: Frontend
  4. Other environment details:
    Tested the bug on :
  • Chrome : Version 81.0.4044.138 (Official Build) (64-bit)
  • Firefox : 76.0 (64-bit)

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Enable connectors such that there are a large number on the connectors page. Eg: 19 for us.
  2. Go to /dashboard/data/connectors on the frontend.
  3. last few connectors are cut off from the page even after scrolling.

Expected Output

I would expect to be able to scroll and see all connectors.

Actual Output

Some connectors don't appear on the page, even through they are active and I can see their logs pushing into OpenCTI in the back.

Additional information

Attaching Screenshots of both Chrome and Firefox

Virustotal is being cut off in Chrome ( There are more connectors below)
image

Firefox (Notice the red highlight, unlike the demo instance, there are additional connectors after Virustotal that i can see clickable but I cannot scroll to them).
image

@SamuelHassine SamuelHassine added the bug use for describing something not working as expected label May 15, 2020
@SamuelHassine SamuelHassine added this to the Release 3.3.0 milestone May 15, 2020
@SamuelHassine SamuelHassine self-assigned this May 15, 2020
@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
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

2 participants