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

Don't send 'data' when exchanging for a token #103

Open
SpraxDev opened this issue Nov 7, 2020 · 1 comment
Open

Don't send 'data' when exchanging for a token #103

SpraxDev opened this issue Nov 7, 2020 · 1 comment
Assignees
@SpraxDev
Labels
bug Something isn't working enhancement New feature or request

Comments

@SpraxDev
Copy link
Member

SpraxDev commented Nov 7, 2020

I believe this is agains OAuth 2.0 and an /profile route should be used instead, giving the exchanged token an actual purpose.

We'd want to keep the route for backwards compatibility and introduce the 'new' endpoints at the /v2/ suffix.
@SpraxDev SpraxDev added bug Something isn't working enhancement New feature or request labels Nov 7, 2020
@SpraxDev SpraxDev self-assigned this Nov 7, 2020
@SpraxDev SpraxDev mentioned this issue Nov 7, 2020
Open
@SpraxDev SpraxDev pinned this issue Aug 2, 2022
@SpraxDev
Copy link
Member Author

Update

There is now /api/v2/profile which you can contact to get the current profile in the exact same format Mojang provides it.
Please use the access_token you exchanged and set the Authorization header: Authorization: Bearer THE_ACCESS_TOKEN.

Please update your apps to no longer use the data field as it is now considered deprecated and will be removed in the future.

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

@SpraxDev SpraxDev

Labels
bug Something isn't working enhancement New feature or request
Milestone
No milestone
Development

No branches or pull requests
1 participant
@SpraxDev