Skip to content

Expired JWT returns a 401 #3506

Open
Open
@Seluj78

Description

@Seluj78

Description

When trying to use an expired token (the one I used was created on Monday and expired this morning at 9:26am GMT+1), you get a 401 response from the API.

I don't think this is standard but also it's confusing for us using the API. We cannot know if it is just because the token is expired, malformed, or missing.

I've tested with a malformed token and I get the same 401 error.

Edition

Community

Version

0.14.3-rc1

Metadata

Metadata

Assignees

Labels

apiv2Planned for API v2

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions