Home > Back-end >  SocketConnection1. AppServer. The login problem
SocketConnection1. AppServer. The login problem

Time:09-25

Consult SocketConnection1. AppServer. How the login the client and server authentication, after certification by additional OwnerData communications

CodePudding user response:

No player knows?

CodePudding user response:

As if this is an open contact? You try on first and then do a validation code verification, by the good, not through kicked him, try this method, that's what I wrote, method is a bit stupid, but feel good about themselves.

CodePudding user response:

refer to the second floor cowboy_tt response:
if this contact is open? You try to get through, and then make a verification code verification, by the good, not through just kicked him, try this method, that's what I wrote, method is a bit stupid, but feel good about themselves,


Can consider this part of your code? Thank you ~

CodePudding user response:

Three layer client authentication through two ways:

One, the client program login, have infinite connection access, through the login user name and password, to confirm whether have access, and other related permissions, this mainly is the identity confirmation,
Second, the client program when logging in, make sure whether have permissions, this is mainly for the client to confirm,

The original poster is obviously the second option, then to do,
1, on the server to add a LogIn () function, when the user access services for the first time, call the LogIn () to record the user's state information, the LogIn () function, upload the main IP address, MAC address,
2, proves successful, continue to provide services, or trigger has no right to access abnormalities, returned to the customer,
3, assigned to the user for a period of unrestricted access to the service, when after this period of time, the user login status is released, have to log in to continue to invoke the service,
  • Related