HumanSignal / HumanSignal/label-studio
Legacy token not available in the user UI
- Dominant language
- TypeScript
- Stars
- 28.3k
- Forks
- 3.7k
- Avg merge
- 14h
- Merged PRs (30d)
- 15
Description
**Describe the bug**
After version v1.17 of Label Studio I can no longer see the value of the user Legacy Token from the UI. Legacy tokens are enabled in the Organisation settings.
While inspecting the network calls in the `user/account` page I can see the following:
1. a call is being made to: "https://myhost.com/api/current-user/token", but my `LABEL_STUDIO_HOST` is the following: "https://myhost.com/label-studio/" since I use a reverse proxy.
2. the `:path` header of the previous request is `/api/current-user/token`
3. the previous call returns 404 (as expected)
4. the call to the correct URL "https://myhost.com/label-studio/api/current-user/token" actually works.
Do I need to change other settings in the label-studio configuration since the new updates?
**Expected behavior**
The Legacy token should not be "undefines" and should be loaded correctly in the UI.
Most likely the `:path` header of the previous request in my case should be `/label-studio/api/current-user/token`.
**Screenshots**
Missing legacy token:
**Environment:**
- Label Studio Version v1.20.0
Contributor guide
Assessment
This issue has not been assessed yet.