Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[API] Return HTTP 401 on failed authentication #854

Closed
jstanden opened this Issue Jan 9, 2019 · 1 comment

Comments

Projects
1 participant
@jstanden
Copy link
Owner

jstanden commented Jan 9, 2019

We currently return a 200 OK.

@jstanden jstanden modified the milestones: 9.1.1, 9.1.2 Jan 9, 2019

@jstanden jstanden added this to Sprint in 9.2.3 Jan 11, 2019

@jstanden jstanden modified the milestones: 9.1.2, 9.1.3, 9.1.4 Jan 16, 2019

@jstanden jstanden modified the milestones: 9.1.4, 9.1.5 Feb 6, 2019

@jstanden jstanden modified the milestones: 9.1.5, 9.1.6, 9.1.7 Feb 15, 2019

@jstanden jstanden modified the milestones: 9.1.7, 9.1.8, 9.1.9 Feb 26, 2019

@jstanden jstanden modified the milestones: 9.1.9, 9.2.1 Mar 9, 2019

@jstanden jstanden modified the milestones: 9.2.1, 9.2.2 Mar 26, 2019

@jstanden

This comment has been minimized.

Copy link
Owner Author

jstanden commented Mar 27, 2019

Implemented in 9.2.2

@jstanden jstanden closed this Mar 27, 2019

9.2.3 automation moved this from Sprint to Completed! Mar 27, 2019

jstanden added a commit that referenced this issue Mar 29, 2019

* [API/OAuth2] When accessing the REST API using an expired OAuth2 to…
…ken, a `401` (Unauthorized) status code is returned. This makes it easier for a client application to know when to use its refresh token.

Fixes #854

jstanden added a commit that referenced this issue Mar 29, 2019

* [API] When accessing the REST API using legacy signatures, a `401` …
…(Unauthorized) status code is returned for authentication errors.

Fixes #854
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.