Some time ago the development of a product, there is a small program and app: micro letter applets directly log on, app using a login verification code + phone number registration code + phone number / password.
One set of user account password can be used normally, it does not mandate complete another set of account. To avoid the same user account is a small program, app is another account, there are two sets of accounts system open up to each other (binding) requirements.
Login and registration processes under mutually binding comb below.
Applet Register Login
Into the small program from the micro-channel, if the database does not have the micro-channel users, that is registered as a new user, then automatically logged. If you already have this user, and automatically log on.
Why here is UnionID instead openid.
openid same unique users of the same application, unionid the same user the same unique open platform for all applications.
If you are using openid, when there are multiple applications, such as multiple small programs, or micro-channel authorization login applet and the app, with a micro-channel user have multiple openid, how it corresponds to the same account it is very complicated.
App Register Login
App designed only registered mobile phone number + verification codes. If there is no phone number for a user, and register as a new user login. If you already have the phone number of the user, automatically logged.
One more account to determine whether to disable the basic registration Login ratio.
At first there is no judgment of this layer, the issuance of new users when a red envelope (unconditional withdrawal) there is a problem: You have been banned landed phone number, again registered a new account.
So, blacklisted accounts, not only to block the part of the landing, the registration links have to block.
Small micro-channel program, binding / exchange tied phone number
In other tie process that requires original bindings after verification code + phone number verification to enter the unbundling process, to prevent others from malicious binding. Whether this step is necessary, according to the nature of the product may be, if a financial product, the money involved, there must be. Binding the user to replace the phone number, it is likely the original phone number has been unable to receive a verification code. So, if there is no other way of unbundling, the best this step can be skipped.
app phone log, micro-binding signal
These are the registered account login and binding process, which will involve a lot of detail, a good reason to add.