Skip to content

OAuth token expiration is not handled by the UI and/or session manager #140

Open
@guidorice

Description

@guidorice

I noticed this when developing on osm-teams locally.

My oauth token expired, and the osm-teams api was returning responses like this when I used the api with a bearer token

{"statusCode":401,"error":"Unauthorized","message":"Expired token"}

So that seems correct. However, presently the osm-teams UI did not give any indication that anything was expired, even if I reloaded it:

Screen Shot 2020-01-30 at 2 42 43 PM

Until I clicked on "create new team" which resulted in a 401 error json displayed in browser:

Screen Shot 2020-01-30 at 2 51 39 PM

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions