Three schemes for finclip to realize wechat authorized login

With the breakthrough of wechat, a national application monthly 12 Billion , More and more users tend to choose wechat as the whole network login account , Therefore, wechat authorized login is used by many APP、 Applets are the first choice for third-party login authorization . Under wechat applet , The applet login function will generally be through OpenID or UnionID As a unique identifier , Connect with the account system of the applet service , Complete the construction and design of user account system .

at present FinClip As in App The mainstream solution for running applets in , For migrating from wechat applet environment to FinClip The applet under has a rapid reuse wechat login process , And the need to realize wechat authorized login . This article focuses on sharing , stay FinClip In the environment , Several schemes for small programs to realize wechat authorized login .

Why does the applet need to be associated with wechat login ？

First of all, let's talk about the reason why small programs need to be associated with wechat login ： If the developer chooses to put the developed applet on wechat first , You can call wx . login Get user identity , Quickly establish the user system of small programs . After that, if you want to migrate the applet to another App , The account system is facing reconstruction , Previously accumulated wechat users want to guide access to other platforms , It will be very inconvenient to log in with the original wechat account . Use FinClip After associated wechat login , Wechat login logic can be reused quickly , Authorize to obtain wechat account information , Help enterprises quickly divert from wechat to self built ecosystem .

FinClip Three schemes to realize wechat authorized login

Scheme 1 ： Server transformation

Applicable scenario ： Passed by the platform party FinClip Build your own Ecology ,FinClip Third party applets are running in the environment （ That is, the platform cannot modify the applet code ）.

• First step ： stay App By customizing API Inject wx.login Method , Return in the format of wechat applet code;
• The second step ： There is no need to change the applet , According to the implementation on wechat , At this point code Send to the developer's server ;
• The third step ： The developer server adapts , adopt code It can be judged that the login is from FinClip platform , from code Resolve in UserID, Just return the contents of your own account system .

Option two ： Server transformation （ Arouse wechat authorization ）

Use scenarios ： Passed by the platform party FinClip Complete the splitting of its own functions , Small programs are developed by the platform side （ That is, the platform side can modify the applet code ）.

• First step ：SDK Integrated wechat development platform SDK;
• The second step ： Use customization API Inject wx.login, You can get the return after arousing wechat authorization code, At this point, it may be necessary to code Splice unique identification ;
• The third step ： There is no need to change the applet , According to the implementation on wechat , At this point code Send to the developer's server ;
• Step four ： The server is based on code Unique identification , Call different authorization interfaces to obtain OpenID, Query login status returns ;

Limit ： Because wechat restricts different subjects , Under different open platforms OpenID It's inconsistent , At this time, the applet needs to be associated with the same subject , Or the same open platform （ At this time, the unique identifier is UnionID）.

Option three ： Small program transformation

Applicable scenario ： Make logical changes to the applet , When judging FinClip In the environment , Directly from wx.login Get the required information from （ That is, the platform side can modify the applet code ）.

APP Use customization API Inject wx.login , Returns the current APP The login status of the user is ok .

In three scenes , This method is a little more complicated , The definition needs to be modified in the existing wechat applet , Thus making FinClip The applet has the ability of wechat login , Please refer to official documents for specific operation procedures ： Wechat login function introduction
The effect is as follows ：

FinClip Implementation effect of wechat authorized login

Applet generation app It can also easily realize wechat authorized login

be familiar with FinClip Of all know , Except in own App Outside the middle run applet . adopt FinClip Provided FIDE It can also generate wechat applets APP, For some companies with weak development ability , perhaps APP Projects with simple functional requirements are very fast and practical , You can click the development document to view the specific tutorial ： Applet generation App
For this kind of transfer through applet app, It can also realize wechat authorized login , Method as above .

Recently I saw FinClip It has been launched SAAS edition , It's very versatile , Monthly 10000 Free release call , For our individual developers , This free adjustment is enough , It's also very cheap to buy traffic packages for the excess part , It's basically a fracture . If you are interested, you can go to the official website .