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

Check for lobby scope in token during login #840

Merged
merged 2 commits into from
Sep 27, 2021

Conversation

Sheikah45
Copy link
Member

This asserts that the oauth token contains the lobby scope before allowing a player to login. This allows for players to be banned from just the game service. All oauth tokens from the clients currently have the lobby scope

@Sheikah45
Copy link
Member Author

Hmmm not sure why that test is failing because it uses the old password login

@Sheikah45
Copy link
Member Author

When run by itself it passes just fine

@codecov
Copy link

codecov bot commented Sep 23, 2021

Codecov Report

Merging #840 (396849a) into develop (6dc1622) will increase coverage by 0.00%.
The diff coverage is 100.00%.

Impacted Files Coverage Δ
server/oauth_service.py 93.61% <100.00%> (+0.28%) ⬆️

@Askaholic
Copy link
Collaborator

Just a flakey test

@Brutus5000
Copy link
Member

Also this is super important for enabling Gog link 🚀 wheeeeee

@Brutus5000
Copy link
Member

Oh wait. This PR should instead remove the check for Steam link as this moves to the user service.

@Askaholic
Copy link
Collaborator

The steam link check only happens when you login with password

server/oauth_service.py Outdated Show resolved Hide resolved
@Askaholic
Copy link
Collaborator

So I'm assuming when you try to log in via the API and you're banned, you see the ban reason on the webpage?

@Brutus5000
Copy link
Member

Correct

@Askaholic Askaholic merged commit 4f54f25 into develop Sep 27, 2021
@Askaholic Askaholic deleted the feature/check-token-scope branch September 27, 2021 18:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants