pufferpanel
pufferpanel copied to clipboard
Access token authorization bug
Description of issue:
The token generated with /oauth2/token is unable to use parts of the panel api that is outside of /daemon. This leads to Response 401 when trying to send a GET request to /api/nodes.
How to reproduce it:
- Create an OAuth2 Client using an administrator account.
- Generate a key with the OAuth2 client's id and secret.
- Try sending a GET request to /api/nodes
I have uploaded the script I'm using so you can test it with that too, but this online tool can be used as well: Tool: https://reqbin.com/ Test script: https://pastebin.com/5YdMsKXS
Expected behavior:
Expected behavior would be to get a Response 200 and a body, containing all the informations of the panel's nodes. Instead what happens is a 401 Unauthorized response with no body content.
Thank you for looking into this. If you need any more testing or info, feel free to reach out to me either here or on discord. blackruby#2562
Same issue for me It seems that the error here is in token. I tried in many ways to send token with puffer_auth cookie and with Authorization Header but this isn't working
i switch to Mysql and now on i try to get token is return this {"scope":"","error":"invalid_client"}