Dashboard: Expired token should be HTTP 401, not HTTP 500

Created on 1 Aug 2018  路  3Comments  路  Source: kubernetes/dashboard

Environment
Dashboard version: v1.8.3
Kubernetes version: v1.11.1
Operating system: CentOS Linux release 7.5.1804 (Core)
Steps to reproduce
  1. Log in to dashboard and keep the page open
  2. Wait/let token expire
  3. Refresh page
Observed result

in log:

2018/08/01 13:18:32 MSG_TOKEN_EXPIRED_ERROR
2018/08/01 13:18:32 [2018-08-01T13:18:32Z] Outcoming response to 10.244.18.212:38208 with 500 status code
Expected result

in log:

2018/08/01 13:18:32 MSG_TOKEN_EXPIRED_ERROR
2018/08/01 13:18:32 [2018-08-01T13:18:32Z] Outcoming response to 10.244.18.212:38208 with 401 status code
kinbug

Most helpful comment

/kind bug
/assign

I'll pick this one up! I see where the problem is and it should be fairly straight forward (famous last words) :)

All 3 comments

/kind bug
/assign

I'll pick this one up! I see where the problem is and it should be fairly straight forward (famous last words) :)

/close

This seems to still happen with v1.10.0:

2018/12/05 13:13:20 MSG_TOKEN_EXPIRED_ERROR
2018/12/05 13:13:20 [2018-12-05T13:13:20Z] Outcoming response to 10.244.22.126:49022 with 500 status code
Was this page helpful?
0 / 5 - 0 ratings