We generally obtain authorization by way of silent micro-channel users openid, the general security of the entire process in order to do this thing we are all on the server side, when the server side gets to openid, then just jump to our true home, it should also in most cases, because every time I see some numbers on top of opening the public to a particular website are the first white pages for some time, this waiting period is to obtain micro-channel openid time, but once we return to the real home page click on the button , you will find that is unable to return the letter of micro browser is closed, but the constant cycle.
Our current practice is to set up a pre-page, pre-action of the page is devoted to the problem of obtaining openid, server-side all the callbacks current page will come to this page and this page to get in and then go jump to openid the real interface, and if want to get openid a page, you can jump to the page to get openid, so after joining the middle pages, in all parts of an application can be openid acquisition operation, but we still recommend when the page is the start get openid, only to fold loading speed is very required to consider only get openid in two pages,
After adding the intermediate pages marked in the middle of the page, if you determine the source of intent, if the intention is to obtain the implementation of access openid openid, if it is to get openid server callback, then jump to the target page, if it is because of the current recession came page, perform history.back () or closeWindow