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

Bring uses_totp to the account object in the client api #5124

Open
1 task done
TekExplorer opened this issue Jun 16, 2024 · 2 comments · May be fixed by #5288
Open
1 task done

Bring uses_totp to the account object in the client api #5124

TekExplorer opened this issue Jun 16, 2024 · 2 comments · May be fixed by #5288
Labels
feature request A request for a new feature.

Comments

@TekExplorer
Copy link
Contributor

TekExplorer commented Jun 16, 2024

Is there an existing feature request for this?

  • I have searched the existing issues before opening this feature request.

Describe the feature you would like to see.

currently, the client api returns the following data about the user

  • int id (window.PterodactylUser shows uuid, but not id. strange discrepancy.)
  • bool admin
  • username
  • email
  • first and last name
  • language
    However, the enabled/disabled status of their mfa is locked behind window.PterodactylUser which is not accessible via the api.

Describe the solution you'd like.

Include the use_totp field in the user object returned by the api. and maybe name it properly as uses_totp

Additional context to this request.

As the developer of featherdactyl, an app for pterodactyl, its impossible for me to tell if a user has totp enabled or not, so i cannot properly show the correct dialog to toggle it with. I simply do not know which to show - enable, or disable.

I'm already stuck with web scraping for the app name, but at least that works. This, as its blocked by session login, simply doesnt.

@TekExplorer TekExplorer added the feature request A request for a new feature. label Jun 16, 2024
@TekExplorer
Copy link
Contributor Author

Note: pelican has consolidated both subuser and account, and included all of the missing fields in this pr: pelican-dev/panel#423

I'd suggest doing the same thing

@Boy132
Copy link
Contributor

Boy132 commented Jun 24, 2024

Note: pelican has consolidated both subuser and account, and included all of the missing fields in this pr: pelican-dev/panel#423

I'd suggest doing the same thing

Feel free to port these changes over to Pterodactyl if you want to.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request A request for a new feature.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants