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

Unauthorized errors should redirect to Login page #5608

Closed
SouadHadjiat opened this issue Jan 19, 2024 · 0 comments · Fixed by #5609
Closed

Unauthorized errors should redirect to Login page #5608

SouadHadjiat opened this issue Jan 19, 2024 · 0 comments · Fixed by #5609
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)

Comments

@SouadHadjiat
Copy link
Member

SouadHadjiat commented Jan 19, 2024

Description

Unauthorized errors used to redirect to Login page, and it's not the case anymore. Reproduced on Testing and latest Prod.

Environment

  1. OS (where OpenCTI server runs): { e.g. Mac OS 10, Windows 10, Ubuntu 16.4, etc. }
  2. OpenCTI version: 5.12.20
  3. OpenCTI client: frontend
  4. Other environment details:

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Go to Settings => Security and invalidate your session
  2. Click on any menu (without refreshing) => you'll see "unknown error occurred" message and no redirection to login page (the only way to see the login page is to refresh the page). Happens also when session expires.

Expected Output

Should redirect to Login page

Screenshots (optional)

Capture d'écran 2024-01-19 123923

@SouadHadjiat SouadHadjiat added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Jan 19, 2024
@SouadHadjiat SouadHadjiat self-assigned this Jan 19, 2024
@SouadHadjiat SouadHadjiat removed the needs triage use to identify issue needing triage from Filigran Product team label Jan 19, 2024
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Jan 19, 2024
@SamuelHassine SamuelHassine added this to the Release 5.12.21 milestone Jan 19, 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

Successfully merging a pull request may close this issue.

2 participants