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

Client Api Key not visible #768

Closed
3 tasks done
TeddyBear2004 opened this issue Dec 5, 2024 · 0 comments · Fixed by #771
Closed
3 tasks done

Client Api Key not visible #768

TeddyBear2004 opened this issue Dec 5, 2024 · 0 comments · Fixed by #771
Labels
🐛 bug Something isn't working
Milestone

Comments

@TeddyBear2004
Copy link

TeddyBear2004 commented Dec 5, 2024

Current Behavior

When creating a client api token in the new gui, these are not displayed. Only the short form is displayed.

Expected Behavior

The api token must be visible in the gui, otherwise it is tempting to assume that the short form of the token is the actual token.

Steps to Reproduce

  1. open the new gui
  2. click on the profile picture top left
  3. select profile
  4. select API Keys
  5. type any description
  6. create

Panel Version

1.0.0-beta14

Wings Version

1.0.0-beta6

Games and/or Eggs Affected

No response

Docker Image

No response

Error Logs

No response

Is there an existing issue for this?

  • I have searched the existing issues before opening this issue.
  • I have provided all relevant details, including the specific game and Docker images I am using if this issue is related to running a server.
  • I have checked in the Discord server and believe this is a bug with the software, and not a configuration issue with my specific system.
@RMartinOscar RMartinOscar added the 🐛 bug Something isn't working label Dec 6, 2024
@RMartinOscar RMartinOscar added this to the beta15 milestone Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants