[jira] [Updated] (IGNITE-11353) Web console: responses with status 401 do not redirect to signin page
[ https://issues.apache.org/jira/browse/IGNITE-11353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-11353: -- Ignite Flags: (was: Docs Required) > Web console: responses with status 401 do not redirect to signin page > - > > Key: IGNITE-11353 > URL: https://issues.apache.org/jira/browse/IGNITE-11353 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Alexey Kuznetsov >Priority: Major > Time Spent: 56m > Remaining Estimate: 0h > > What happens: > On page reload, when backend API responds with status of 401, the app is > stuck on "loading" screen and does not redirect to signin screen. > What should happen: > The app should redirect to signin screen when 401 happens (except for a few > exceptions). > How to reproduce: > 1. Sign out. > 2. Open profile page URL (/settings/profile). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11353) Web console: responses with status 401 do not redirect to signin page
[ https://issues.apache.org/jira/browse/IGNITE-11353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Kuznetsov updated IGNITE-11353: -- Fix Version/s: 2.8 > Web console: responses with status 401 do not redirect to signin page > - > > Key: IGNITE-11353 > URL: https://issues.apache.org/jira/browse/IGNITE-11353 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Alexey Kuznetsov >Priority: Major > Fix For: 2.8 > > Time Spent: 56m > Remaining Estimate: 0h > > What happens: > On page reload, when backend API responds with status of 401, the app is > stuck on "loading" screen and does not redirect to signin screen. > What should happen: > The app should redirect to signin screen when 401 happens (except for a few > exceptions). > How to reproduce: > 1. Sign out. > 2. Open profile page URL (/settings/profile). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11353) Web console: responses with status 401 do not redirect to signin page
[ https://issues.apache.org/jira/browse/IGNITE-11353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ilya Borisov updated IGNITE-11353: -- Description: What happens: On page reload, when backend API responds with status of 401, the app is stuck on "loading" screen and does not redirect to signin screen. What should happen: The app should redirect to signin screen when 401 happens (except for a few exceptions). How to reproduce: 1. Sign out. 2. Open profile page URL (/settings/profile). was: What happens: On page reload, when backend API responds with status of 401, the app is stuck on "loading" screen and does not redirect to signin screen. What should happen: The app should redirect to signin screen when 401 happens (except for a few exceptions). How to reproduce: 1. Sign in. 2. Kill user session in db. 3. Reload the page. > Web console: responses with status 401 do not redirect to signin page > - > > Key: IGNITE-11353 > URL: https://issues.apache.org/jira/browse/IGNITE-11353 > Project: Ignite > Issue Type: Improvement > Components: wizards >Reporter: Ilya Borisov >Assignee: Ilya Borisov >Priority: Major > > What happens: > On page reload, when backend API responds with status of 401, the app is > stuck on "loading" screen and does not redirect to signin screen. > What should happen: > The app should redirect to signin screen when 401 happens (except for a few > exceptions). > How to reproduce: > 1. Sign out. > 2. Open profile page URL (/settings/profile). -- This message was sent by Atlassian JIRA (v7.6.3#76005)