/graylog2-server

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

Fix redirection when user is unauthorised #1985

Closed
edmundoa opened this Issue Mar 29, 2016 · 0 comments

Comments

Assignees

@edmundoa edmundoa

Labels
P2 S3 bug triaged web
Projects
None yet
Milestone
  2.0.0
2 participants
@edmundoa @kroepke
@edmundoa
Member

edmundoa commented Mar 29, 2016

Problem description

We did some changes in the UI (#1944) to redirect the user when they are unauthorised to access a resource. Unfortunately that is not working properly at the moment, and the user is not being redirected to the start page.

Steps to reproduce the problem

  1. Log in as a regular user
  2. Go to /search
  3. The spinner loads forever, and the web console shows the error getting the resource (403)

Environment

  • Graylog Version: Graylog 2.0.0-beta.2-SNAPSHOT (f714ed5)
  • Browser version: Chrome 49

@edmundoa edmundoa added bug web labels Mar 29, 2016

@edmundoa edmundoa added this to the 2.0.0 milestone Mar 29, 2016

@SjonHortensius SjonHortensius referenced this issue Mar 30, 2016

Closed

2.0b1 - Link to specific message not working for Reader #1993

@kroepke kroepke added S3 P2 labels Mar 31, 2016

edmundoa added a commit that referenced this issue Apr 4, 2016

@edmundoa
Make history global 
As with the stores, history should be shared between plugins and the web
application. Otherwise the results of handling the history object in
plugins will not change the state in other plugins or the application.

Fixes #1985
Loading status checks…
ee7840b

@edmundoa edmundoa self-assigned this Apr 4, 2016

@edmundoa edmundoa referenced this issue Apr 4, 2016

Merged

Make history global #2024

@dennisoelkers dennisoelkers closed this in #2024 Apr 11, 2016

dennisoelkers added a commit that referenced this issue Apr 11, 2016

@edmundoa @dennisoelkers
Make history global (#2024) 
As with the stores, history should be shared between plugins and the web
application. Otherwise the results of handling the history object in
plugins will not change the state in other plugins or the application.

Fixes #1985
Loading status checks…
a91cfe9

@kroepke kroepke added the triaged label Sep 21, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment