[
https://issues.apache.org/jira/browse/IGNITE-11353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16771750#comment-16771750
]
Ilya Borisov commented on IGNITE-11353:
---------------------------------------
The issue was caused by wrong state name. When 401 happens, the app redirects
to '403', which doesn't exist, instead of 'base.403'. The '403' was moved to
'base.403' not so long ago, so this is probably the root of it. After fixing
that, I found another related bug: timed-redirect component used for 403 screen
did not redirect anywhere if user wasn't authorized, so I added an extra check
for user authorization and redirect to 'signin' state if not.
> 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)
