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 if user already exists #1

Open
BlaneyXYZ opened this issue Nov 7, 2013 · 4 comments
Open

Check if user already exists #1

BlaneyXYZ opened this issue Nov 7, 2013 · 4 comments

Comments

@BlaneyXYZ
Copy link
Member

When username is first entered it should be checked against the existing database.
If possible included all variants of username in order to stop double accounts.

@WizardCM
Copy link
Member

WizardCM commented Nov 7, 2013

This will check the WordPress database for the existing user.

If the user exists, it'll ask them to login first. Then they can be redirected back to the first page to "link" that Minecraft username to their existing WordPress account.

If the user doesn't exist in WordPress, check that the Minecraft username entered exists in Mojang's "haspaid" list. If it doesn't, error. If it does, continue to the second step.

We could also do a blacklist of popular usernames, but truthfully we don't need to.

Another check would also be to see if it's already verified, then notify the user, as this isn't done on the site yet.

@Lunaphied
Copy link

This kind of authentication can be coupled with a server side plugin that
asks for a confirmation code when joining. This allows the web
authentication to avoid asking for the password of a user.
On Nov 7, 2013 1:02 AM, "Matt Gajownik" [email protected] wrote:

This will check the WordPress database for the existing user.

If the user exists, it'll ask them to login first. Then they can be
redirected back to the first page to "link" that Minecraft username to
their existing WordPress account.

If the user doesn't exist in WordPress, check that the Minecraft username
entered exists in Mojang's "haspaid" list. If it doesn't, error. If it
does, continue to the second step.

We could also do a blacklist of popular usernames, but truthfully we don't
need to.


Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-27941913
.

@WizardCM
Copy link
Member

WizardCM commented Nov 7, 2013

...at no point do we ask for a password, except when WordPress requires one to make an account.

The "confirmation" is that the user has to launch their game and connect to the python authentication server. Simple as that.

@Lunaphied
Copy link

That's what I was talking about, I merely meant that you could avoid
blacklists by doing what is already implemented.
On Nov 7, 2013 6:24 AM, "Matt Gajownik" [email protected] wrote:

...at no point do we ask for a password, except when WordPress requires
one to make an account.

The "confirmation" is that the user has to launch their game and connect
to the python authentication server. Simple as that.


Reply to this email directly or view it on GitHubhttps://github.com//issues/1#issuecomment-27958279
.

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

No branches or pull requests

3 participants