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] Orders endpoint only works in the browser and only after user login #5500

Closed
luisramos0 opened this issue May 26, 2020 · 1 comment
Closed
Labels
bug-s3 The bug is stopping a critical or non-critical feature but there is a usable workaround.

Comments

@luisramos0
Copy link
Contributor

luisramos0 commented May 26, 2020

Description

API authentication is not working in the api/orders api. IT only works if you login to the app on your browser and access the endpoint through that session.
USing api token and curl wont work.

Expected Behavior

Actual Behaviour

Steps to Reproduce

Animated Gif/Screenshot

Workaround

Severity

Your Environment

  • Version used:
  • Browser name and version:
  • Operating System and version (desktop or mobile):

Possible Fix

@luisramos0 luisramos0 added the bug-s2 The bug is affecting any of the non-critical features described in S1 and there is no workaround. label May 26, 2020
@luisramos0 luisramos0 assigned luisramos0 and unassigned luisramos0 May 26, 2020
@luisramos0 luisramos0 changed the title [API] Orders endpoint doesn't work outsside the brwoser [API] Orders endpoint doesn't work outside the browser (and only after login) May 26, 2020
@luisramos0 luisramos0 changed the title [API] Orders endpoint doesn't work outside the browser (and only after login) [API] Orders endpoint only works in the browser and only after user login May 26, 2020
@luisramos0 luisramos0 added bug-s3 The bug is stopping a critical or non-critical feature but there is a usable workaround. and removed bug-s2 The bug is affecting any of the non-critical features described in S1 and there is no workaround. labels May 26, 2020
@RachL
Copy link
Contributor

RachL commented Dec 7, 2022

I'm assuming v1 will handle this differently, closing.

@RachL RachL closed this as completed Dec 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug-s3 The bug is stopping a critical or non-critical feature but there is a usable workaround.
Projects
None yet
Development

No branches or pull requests

2 participants