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.

Sign up for GitHub

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

Jump to bottom

RacksDB Bearer token error #471

Closed
thatguy24601 opened this issue Feb 10, 2025 · 4 comments · Fixed by #477
Closed

RacksDB Bearer token error #471

thatguy24601 opened this issue Feb 10, 2025 · 4 comments · Fixed by #477
Assignees
@rezib
Labels
frontend Something todo in frontend component (Vue.js application)
Milestone
v4.2.0

Comments

@thatguy24601
Copy link

I recently tried using Slurm-web 4.1.0. I'm trying to use the RacksDB integration, however when I go to the resources tab I see a message where I'd expect to see the drawing that says:

Server error: Request failed with status code 403

All the other endpoints seem to work fine. Using browser tools I can see that this call is not being sent a Bearer token while all other calls appear to be getting one.

The only thing I see in the logs on the system itself is a message that says:

uwsgi[835945]: uWSGIWorker5Core0: [WARNING] Unauthorized access without bearer token
@rezib
Copy link
Contributor

rezib commented Feb 10, 2025

Hello @thatguy24601, thank you for reporting it!

This is clearly a bug, it is visible since the release of RFL v1.3.0 which brings a few changes in the way requests without bearer token are managed. I will probably release a v4.1.1 to fix this bug soon.

@rezib
Copy link
Contributor

rezib commented Feb 11, 2025 •
edited
Loading

Hello @thatguy24601, I published Slurm-web packages 4.1.0-2 and 3.2.0-2 with a patch to fix this bug. Can you update your packages to check it is fixed for you?

@rezib rezib self-assigned this Feb 11, 2025
@rezib rezib added this to the v4.2.0 milestone Feb 11, 2025
@rezib rezib added the frontend Something todo in frontend component (Vue.js application) label Feb 11, 2025
rezib added a commit to rackslab/hpck.it that referenced this issue Feb 11, 2025
@rezib
slurm-web: add patch for racksdb bearer token bug
5174cb3 
For reference: rackslab/Slurm-web#471
@thatguy24601
Copy link
Author

I can confirm this error no longer appears and I see a rack diagram. Thanks for the quick action on this!

@rezib
Copy link
Contributor

rezib commented Feb 11, 2025

Great! I will let the issue open until it's definitely fixed in v4.2.0.

rezib added a commit that referenced this issue Feb 13, 2025
@rezib
fix(front): add bearer token in racksdb request
3ee9773 
Add missing bearer token in RacksDB infrastructure diagram request, it
is now required by @check_jwt decorator on the gateway endpoint with
RFL >= 1.3.0 to avoid HTTP/403 response.

fix #471
@rezib rezib mentioned this issue Feb 13, 2025
Merged
rezib added a commit that referenced this issue Feb 13, 2025
@rezib
fix(front): add bearer token in racksdb request
d1ca288 
Add missing bearer token in RacksDB infrastructure diagram request, it
is now required by @check_jwt decorator on the gateway endpoint with
RFL >= 1.3.0 to avoid HTTP/403 response.

The token is removed from request headers for login (incl. anonymous)
and login service message at the same time, as the client does not have
JWT at this stage yet and the gateway does not enforce the presence of
the bearer token for the corresponding endpoints.

fix #471
rezib added a commit that referenced this issue Feb 13, 2025
@rezib
fix(front): add bearer token in racksdb request
cb8afb8 
Add missing bearer token in RacksDB infrastructure diagram request, it
is now required by @check_jwt decorator on the gateway endpoint with
RFL >= 1.3.0 to avoid HTTP/403 response.

The token is removed from request headers for login (incl. anonymous)
and login service message at the same time, as the client does not have
JWT at this stage yet and the gateway does not enforce the presence of
the bearer token for the corresponding endpoints.

fix #471
@rezib rezib closed this as completed in 214b6a6 Feb 13, 2025
rezib added a commit that referenced this issue Feb 13, 2025
@rezib
fix(front): add bearer token in racksdb request
a3a7b2f 
Add missing bearer token in RacksDB infrastructure diagram request, it
is now required by @check_jwt decorator on the gateway endpoint with
RFL >= 1.3.0 to avoid HTTP/403 response.

The token is removed from request headers for login (incl. anonymous)
and login service message at the same time, as the client does not have
JWT at this stage yet and the gateway does not enforce the presence of
the bearer token for the corresponding endpoints.

fix #471
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rezib rezib

Labels
frontend Something todo in frontend component (Vue.js application)
Projects
None yet
Milestone
v4.2.0
Development

Successfully merging a pull request may close this issue.

fix(front): add bearer token in racksdb request rackslab/Slurm-web
2 participants
@rezib @thatguy24601