CN114268474A - Operator application login control method, device, equipment and storage medium - Google Patents
Operator application login control method, device, equipment and storage medium Download PDFInfo
- Publication number
- CN114268474A CN114268474A CN202111516732.2A CN202111516732A CN114268474A CN 114268474 A CN114268474 A CN 114268474A CN 202111516732 A CN202111516732 A CN 202111516732A CN 114268474 A CN114268474 A CN 114268474A
- Authority
- CN
- China
- Prior art keywords
- application
- authorization
- user
- current operator
- party
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Landscapes
- Telephonic Communication Services (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The application provides a method, a device, equipment and a storage medium for controlling login of an operator application. Receiving a login request sent by a user to a third-party application, wherein the third-party application is a non-current operator application; obtaining an authorization request sent by the third-party application to the current operator application, wherein the authorization request is used for the third-party operator application to obtain the user account information stored by the current operator application; obtaining an authorization instruction of the current operator application corresponding to the authorization request; and logging in the third-party application through the user account information stored in the current operator application according to the authorization instruction. According to the method, the third-party application is logged in through authorization of the current operator application, so that the third-party application is rapidly logged in, and the use of a user is facilitated.
Description
Technical Field
The present application relates to the field of communications technologies, and in particular, to a method, an apparatus, a device, and a storage medium for controlling login of an operator application.
Background
In the current internet Application environment, there are many terminal Applications (APPs) that can be downloaded by a user, including applications developed by an operator, which are simply referred to as operator applications, and the user can select an Application that the user wants to use according to the requirement.
In the prior art, when a user logs in an application of a current operator and applications of other operators on a terminal device, a login account needs to be registered first, and then the user logs in after account information and a password are input on an application login interface, wherein the account information can be a mobile phone number of the user, a mailbox address, a combination of a user-defined number and a special symbol, and the like.
However, the current method of logging in the application of the current operator and the application of other operators requires a user to memorize a plurality of login accounts and passwords, and when the user uses different applications, the account needs to be switched, so that the time consumption of the login process is long, and the inconvenience is brought to the user.
Disclosure of Invention
The application provides a method, a device, equipment and a storage medium for controlling login of operator applications, and aims to solve the problem that the time consumed for logging in the current operator applications and the applications of other operators in the prior art is long.
In a first aspect, the present application provides an operator application login control method, including:
receiving a login request sent by a user to a third-party application, wherein the third-party application is a non-current operator application;
obtaining an authorization request sent by the third-party application to the current operator application, wherein the authorization request is used for the third-party operator application to obtain the user account information stored by the current operator application;
obtaining an authorization instruction of the current operator application corresponding to the authorization request;
and logging in the third-party application through the user account information stored in the current operator application according to the authorization instruction.
Optionally, the obtaining of the authorization instruction applied by the operator corresponding to the authorization request includes:
generating an authorization interface according to the authorization request;
receiving an authorization indication input by a user through the authorization interface;
and acquiring an authorization instruction applied by the current operator according to the authorization instruction.
Optionally, the logging in the third-party application through the user account information stored in the current operator application according to the authorization instruction includes:
according to the authorization instruction, acquiring an authorization code generated by the current operator application, wherein the authorization code represents a certificate for the third-party application to acquire the authorization of the current operator application;
according to the authorization code, obtaining an access token of the third-party application for accessing the current operator application, wherein the access token is used for the third-party application to obtain user account information stored in the current operator application;
and logging in the third-party application through the user account information stored in the current operator application.
Optionally, the authorization code includes permission information of the current operator application, which is allowed to be acquired by the third-party application, where the permission information includes one or more of a user number, a user number attribution area, a user avatar, and a number type.
Optionally, before the obtaining of the authorization instruction applied by the current operator corresponding to the authorization request, the method includes:
acquiring an authentication login request applied by the third-party application to an authentication platform of the current operator application;
and receiving authentication information sent by the current operator application to the third party application according to the authentication login request, wherein the authentication information is used for the third party application to acquire an authorization interface of the current operator application.
Optionally, the method further includes: receiving a login request sent by a user to a current operator application;
obtaining an authorization request sent by the current operator application to the third-party application, wherein the authorization request is used for the current operator application to obtain the user account information stored by the third-party application;
obtaining an authorization instruction of the third-party application corresponding to the authorization request;
and logging in the current operator application through the user account information stored in the third-party application according to the authorization instruction.
Optionally, the logging in the current operator application through the user account information stored in the third-party application according to the authorization instruction includes:
acquiring a user identifier of the third-party application;
judging whether the user identification is bound with a user number in an authentication platform applied by the current operator;
and if the user identification is bound with a user number, logging in the current operator application through the user number.
Optionally, the method further includes:
if the user identification is not bound with the user number, generating a user number binding interface;
and receiving a user number input by a user through the binding interface, and logging in the current operator application through the user number.
In a second aspect, the present application provides an operator application login control apparatus, including:
the system comprises a receiving module, a login module and a login module, wherein the login request sent by a user to a third-party application is received, and the third-party application is a non-current operator application;
the first acquisition module is used for acquiring an authorization request sent by the third-party application to the current operator application, wherein the authorization request is used for the third-party operator application to acquire the user account information stored in the current operator application;
the second acquisition module is used for acquiring the authorization instruction of the current operator application corresponding to the authorization request;
and the login module is used for logging in the third-party application through the user account information stored in the current operator application according to the authorization instruction.
In a third aspect, the present application provides an electronic device, comprising: a processor, and a memory communicatively coupled to the processor;
the memory stores computer-executable instructions;
the processor executes computer-executable instructions stored by the memory to perform the method of operator application login control of any of the first aspects.
In a fourth aspect, the present application provides a computer-readable storage medium having stored thereon computer-executable instructions for implementing the method for operator application login control according to any one of the first aspect.
According to the operator application login control method, the operator application login control device, the operator application login control equipment and the operator application login control storage medium, a login request sent by a user to a third-party application is received, wherein the third-party application is not a current operator application, then an authorization request sent by the third-party application to the current operator application is obtained, and the authorization request is used for the third-party operator application to obtain the user account information stored in the current operator application. And obtaining an authorization instruction applied by the current operator according to the authorization request, and logging in the third-party application through the user account information stored in the current operator application after obtaining the authorization instruction applied by the current operator. According to the method, the third-party application is logged in through authorization of the current operator application, so that the third-party application is rapidly logged in, and the use of a user is facilitated.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and together with the description, serve to explain the principles of the application.
Fig. 1 is a schematic flowchart of an operator application login control method according to an embodiment of the present application;
fig. 2 is a signaling flowchart of an operator application login control method according to a second embodiment of the present application;
fig. 3 is a schematic flowchart of another operator application login control method according to a third embodiment of the present application;
fig. 4 is a signaling flowchart of another operator application login control method provided in the third embodiment of the present application;
fig. 5 is a schematic flowchart of another operator application login control method according to the fourth embodiment of the present application;
fig. 6 is a schematic structural diagram of an apparatus for controlling login of an operator application according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
With the above figures, there are shown specific embodiments of the present application, which will be described in more detail below. These drawings and written description are not intended to limit the scope of the inventive concepts in any manner, but rather to illustrate the inventive concepts to those skilled in the art by reference to specific embodiments.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.
The terms referred to in this application are explained first:
openid: in an online Identity authentication system, after a user registers in advance on a website serving as an Openid Identity Provider (IdP), Openid can be used for directly logging in other websites. The Openid system can be applied to all places needing identity verification, not only to a single sign-on system, but also to identity authentication when sharing sensitive data.
Oauth: open Authorization, an Open network standard for Authorization (Authorization), is currently in version 2.0. The third-party website is allowed to access various information stored in a service provider by a user on the premise of user authorization, the user name and the password provided by the user are not required to be provided for the third-party website by the authorization, the credit granting process is safe and reliable, and in the application, Oauth is used for an authentication platform applied by a current operator.
H5: the HTML5 is a short form, and is a set of technologies for creating a web page interaction effect, that is, the H5 web page is a web interface of the mobile terminal, and is used for generating an authorization interface of the current operator in the present application.
With the development of internet technology, more and more terminal applications are available for users to select, including applications developed by operators, i.e., operator applications.
The operator provides necessary network service for the user, and meets the daily requirement of the user, and in order to enhance the convenience degree of the user to the network use, various operator application programs are correspondingly developed, and the user can check the communication information or the telephone charge condition of the user in the operator application, so that the user can conveniently master the communication condition of the user.
For example, the user may check the traffic usage of the user through the operator application, may check the remaining call duration through the operator application, may check the credit condition, and may directly pay the call charge through the operator application.
Currently, when a user uses a current operator application and other operator applications, a login account generally needs to be registered, and the user logs in and uses the current operator application and other operator applications after registering the account on different applications. In general, a user can use a mobile phone number of the user as a registered account, and after setting a password, the user logs in the application. Optionally, the user may also register in a manner of using a mailbox address + password, and the user may also register in a manner of customizing an account + password, for example, the account is composed of a combination of letters, numbers, special characters, and the like.
However, when the user wants to switch from the current operator application to another operator application, the user needs to log in the account and the password corresponding to the switched application again on the switched application, and when the user wants to switch from the other operator application to the current operator application, the user also needs to log in the account and the password of the current operator application again. Therefore, a user needs to memorize a plurality of login accounts and passwords, and the user needs to login the account and the password once every switching, so that the process is complicated and time-consuming, and great inconvenience is brought to the user.
Therefore, for the above problems in the prior art, the application provides an operator application login control method, an operator application login control device, and a storage medium, wherein the third-party application is controlled by the operator application and a third-party application, the third-party application is not currently controlled by the operator application, authorization of the operator application is obtained, the third-party application is logged in through user account information stored in the operator application, a user can experience different application programs only by using the same account, and the account and the password corresponding to the application to be logged in are not required to be obtained, so that rapid login between applications is not required.
The application scenario of the application can be login control between the operator application and the third-party application, for example, a user can log in the third-party application by authorization of the current operator application, and can also log in the operator application by authorization of the third-party application. It is understood that the operator application login control method provided by the present application includes, but is not limited to, the above application scenarios.
The following describes the technical solutions of the present application and how to solve the above technical problems with specific embodiments. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.
As shown in fig. 1, fig. 1 is a schematic flowchart of an operator application login control method according to an embodiment of the present application. As shown in fig. 1, the method may include the steps of:
s101, receiving a login request sent by a user to a third-party application, wherein the third-party application is a non-current operator application.
The execution main body of the application can be an intelligent terminal, wherein the intelligent terminal can be a mobile phone, a computer, a tablet computer and other equipment.
The terminal has a plurality of application programs, and a user can select an application which the user wants to use according to the requirement. The user selects a third-party application which the user wants to log in on the terminal, wherein the third-party application is not the current operator application, and after the user determines the third-party application which the user wants to log in, the terminal receives a login request sent by the user to the third-party application.
S102, an authorization request sent by the third-party application to the current operator application is obtained, and the authorization request is used for the third-party operator application to obtain user account information stored in the current operator application.
The operator application is an application program developed by an operator, and user account information is stored in the operator application.
After receiving a login request of a user, the third-party application prepares to log in the third-party application, and if the user wants to log in the third-party application through account information of the current operator application, the third-party application needs to send an authorization request to the current operator application.
It should be noted that, the user may log in the third-party application by inputting the corresponding account password on the third-party application login interface.
S103, obtaining an authorization instruction applied by the current operator corresponding to the authorization request.
After receiving the authorization request of the third-party application, the current operator application obtains an authorization instruction of the current operator application if the current operator application allows the third-party application to access.
And S104, logging in the third-party application through the user account information stored in the current operator application according to the authorization instruction.
After the current operator application allows the third-party application to access, the third-party application can acquire the user account information stored by the current operator application, and finally, the third-party application logs in through the user account information stored by the current operator application. The user account information may be a user number, a home zone of the user, a user avatar, or an operator number type.
In the embodiment of the application, the user sends a login request to the third-party application, the third-party application sends an authorization request to the current operator application to request to acquire the user account information stored by the current operator, and after the authorization is allowed by the current operator, the third-party application logs in through the user account information stored by the current operator application. The user does not need to register the account again in the third-party application, and the quick login of the third-party application is realized directly by a mode of authorizing the third-party application to access the user account information stored in the current operator application.
Further, on the basis of the first embodiment, the following describes in detail a process of authorizing to log in the third party application through the current operator application according to a second embodiment. As shown in fig. 2, fig. 2 is a signaling flowchart of an operator application login control method provided in the second embodiment of the present application, where the method may be implemented by the following steps:
s201, the user logs in the third-party application.
S202, the third party application requests authorization from the current operator application.
After receiving an authorization request sent by a third-party application, a current operator application starts to access a login interface of the current operator application, and generates an authorization code (code) after logging in the operator application interface, wherein the authorization code (code) represents a certificate for the third-party application to acquire authorization of the current operator application;
and S203, generating an authorization interface according to the authorization request.
And the user selects to apply authorization login through the current operator on the third-party application login interface, and the terminal generates an authorization interface according to the authorization request.
It should be noted that the authorization interface can be generated by the following method:
in a possible embodiment, the terminal may install the current operator application.
If the user installs the current operator application on the terminal, the third party application can directly acquire the current operator application authorization interface to acquire the user authorization. During authorization, the user can select the authorization level, such as the mobile phone number of the user, the home region of the user, the head portrait of the user or the number type of the operator, and the user information can be acquired after the user confirms the authorization level.
In another possible embodiment, the terminal does not need to install the current operator application.
If the user does not install the operator application on the terminal, the third-party application acquires the H5 authorized login page, the H5 authorized page can acquire the user number through a NET number taking mode of the current operator without guiding the user to download the current operator application, authorization is provided for the third-party application, the authorization level is only that the user number is acquired through authorization, and login can be achieved after the third-party application acquires the number.
And S204, receiving an authorization instruction input by the user through an authorization interface.
The user can select the user information which is allowed to be accessed by the third-party application and is stored in the current operator application, namely the authorization level in the authorization interface, and the authorized level content user can check on the interface by himself. Optionally, the third-party application may obtain the mobile phone number of the user, the home area of the user, the user avatar or the type of the operator number according to the current operator application authorization. If the information users do not want to check, the third-party application can only acquire the ID address information of the users, and therefore the level of the authorization allowed by the users is obtained.
It should be noted that the pop-up time for asking the user if the user authorizes the interface is limited, and if the current operator application can receive the authorization indication from the user within the set time, the authorization code (code) in the above steps is valid. If the current operator application cannot obtain the authorization indication of the user within the set time, the credential becomes invalid. Third party applications are required to re-acquire credentials.
And if the user does not allow the authorization of the current operator application, the third-party application cannot log in through the user account information stored in the current operator application.
S205, according to the authorization indication, the authorization code generated by the current operator application is obtained.
The current operator application acquires an authorization instruction of the current operator application according to an authorization instruction of a user, redirects the authorization instruction to a third party application, and sends an authorization code (code) to the third party application, wherein the authorization code contains permission information of the current operator application, which is allowed to be acquired by the third party application, and the permission information includes but is not limited to a user number, a user number attribution area, a user head portrait, a number type and the like.
S206, according to the authorization code, an access token of the third-party application for accessing the current operator application is obtained.
After receiving the authorization code (code) sent by the current operator application, the third-party application applies for an access token (access _ token) to the current operator application with the authorization code (code), wherein the access token (access _ token) is a pass for the third-party application to access the current operator application resource and is used for the third-party application to obtain the user account information stored by the current operator application.
And S207, logging in the third-party application through the user account information stored in the current operator application.
And when the third-party application takes the access token (access _ token), accessing the user account information stored in the current operator application through the access token (access _ token), and after the user account information is successfully obtained, the user sees that the login is successful in the third-party application.
Through the steps, the quick login of the third-party application is realized, wherein the third-party application is authorized through an operator Oauth2.0 authentication system.
It should be noted that, since the current operator application does not allow any application to access itself at will, when other applications want to access the operator application, they first need to obtain the audit of the access allowed by the operator application.
In particular, the method comprises the following steps of,
and acquiring an authentication login request applied by the third-party application to the authentication platform of the current operator application.
And receiving authentication information sent by the current operator application to the third party application according to the authentication login request, wherein the authentication information is used for the third party application to acquire an authorization interface of the current operator application.
First, the third-party application needs to be registered in an authentication platform of the current operator application, and after the registration of the third-party application is completed, the current operator application sends "authentication information" to the third-party application, where the authentication information includes, but is not limited to, information such as an application code (app _ code), a channel code (channel _ code), and an application key (app _ secret). The application code (app _ code), channel code (channel _ code) and application key (app _ secret) obtained by the third party application represent the identity of the third party application.
When the third-party application wants to access the current operator application, the third-party application provides an application authentication login request to the current operator application, and the current operator verifies the third-party application according to the identity of the third-party application.
The auditing process comprises the following steps:
the current operator application identifies which specific third party application wants to access according to an application code (app _ code) and a channel code (channel _ code) provided by the third party application, and then verifies the third party application program according to an application key (app _ secret). The verification of the identity of the third-party application is to verify the validity of the third-party application, and if the identity of the third-party application is legal, the third-party application is allowed to access the resources applied by the current operator, that is, the third-party application can obtain the authorization interface applied by the current operator.
In the second embodiment of the present application, an authorization interface is generated according to an authorization request of a third-party application, an authorization instruction of a user is received on the authorization interface, and the third-party application acquires an authorization instruction applied by a current operator according to the authorization instruction. And then the current operator application generates an authorization code according to the authorization instruction and sends the authorization code to the third-party application, the third-party application carries the authorization code to acquire an access token from the current operator application, and finally, the third-party application logs in through the user account information stored in the current operator application after the access token is acquired, so that the third-party application can log in quickly.
The above embodiments mainly illustrate that when a user wants to use a third-party application, the user authorizes login through a current operator application. Next, a process of authorizing login through a third party application when a user wants to use an operator application will be described through a third embodiment. As shown in fig. 3, fig. 3 is a schematic flowchart of another operator application login control method provided in the third embodiment of the present application, where the method may include the following steps:
s301, receiving a login request sent by a user to the current operator application.
S302, an authorization request sent by the current operator application to the third-party application is obtained, and the authorization request is used for the current operator application to obtain user account information stored by the third-party application.
S303, obtaining an authorization instruction of the third party application corresponding to the authorization request.
And S304, logging in the current operator application through the user account information stored in the third-party application according to the authorization instruction.
Further, the signaling flow diagram provided in fig. 4 specifically illustrates how to authorize login to the current operator application through the third party application. As shown in fig. 4, fig. 4 is a signaling flowchart of another operator application login control method provided in the third embodiment of the present application.
S401, the user logs in the current operator application.
The user selects the current operator application to be logged in on the terminal, and receives a login request sent by the user to the current operator application.
S402, the current operator application requests authorization from the third party application.
The user selects to authorize login through the third-party application, and the current operator application sends an authorization request to the third-party application.
And S403, generating an authorization interface according to the authorization request.
S404, receiving an authorization instruction input by a user through an authorization interface.
The user can select 'agree' or 'deny' on the authorization interface, and if the user clicks an 'agree' option, the current operator application can obtain authorization of the third-party application and log in through user account information of the third-party application. If the user clicks on the "deny" option, the current operator application cannot authorize the login via the third party application.
S405, obtaining the user identification of the third-party application.
After the user can select "agree" on the authorization interface, the user identification (Openid) of the third-party application can be acquired.
Openid is a digital identity recognition framework with a user as a center, and stores user information. It can be understood as the identity of the third party application itself, but the user identity (Openid) does not carry any identity sensitive information, and cannot directly expose the user information to the current operator application, for example, the user mobile phone number.
S406, judging whether the user unique identification is bound with the user number.
After the current operator application acquires the user identifier (Openid) of the third-party application, whether the user identifier (Openid) is bound with a user number is judged in an authentication platform of the current operator application.
And if the user number is bound, logging in the current operator application through the user number.
And S407, if the user number is not bound, generating a user number binding interface.
And if the user number is not bound, generating a user number binding interface, and optionally, at least setting a mobile phone number filling position, a verification code obtaining button position, a verification code inputting position, a submission button position and the like in the interface.
S408, binding the user number
After the user inputs the user number in the binding interface, the user sends the verification code to the terminal, the user inputs the received verification code to the position of the input verification code, and finally the verification code is submitted through a 'submitting' button, so that the user number is bound.
And S409, logging in the current operator application through the user number.
In the third embodiment of the present application, when a user logs in a current operator application, the user logs in the current operator application by receiving a login request sent by the user to the current operator application, then obtaining an authorization request sent by the current operator application to a third-party application, further obtaining an authorization instruction of the third-party application, and finally logging in the current operator application by using user account information stored in the third-party application. The user does not need to register the account again in the current operator application, and the rapid login of the current operator application is realized directly by authorizing the current operator application to access the user account information stored in the third-party application.
Furthermore, the method provided by the application can also be used for realizing the jump to a third-party page embedded in the current operator application in a login-free mode in the current operator application and accessing a third-party service, wherein the third-party service belongs to the third-party application.
For example, if a certain wealth service in the third-party application a is placed in the current operator application, if the service is intended to be used in the current operator application, the third-party application should acquire account login information of the current operator application, and then the current operator application is allowed to jump to a third-party page in a login-free manner, so as to access the certain wealth service in the third-party application a.
As shown in fig. 5, fig. 5 is a schematic flowchart of another operator application login control method according to a fourth embodiment of the present application. The specific implementation process may be:
the user logs in the current operator application at the terminal, and the mode of logging in the current operator application is to input an account and a password on a login interface. After logging in the current operator application, acquiring an access token (access _ token) and a refresh token (refresh _ token) generated by an authentication platform of the current operator application as interface calling certificates. The access token (access _ token) has a short validity period, and when the access token (access _ token) is overtime, the access token (access _ token) can be refreshed by using a refresh token (refresh _ token), so that login maintenance is realized.
When a user requests to access a third-party service, the current operator application requests the authentication platform to generate an authorization code (code) according to a credential access token (access _ token) invoked from the authentication platform generation interface.
Then, the current operator application accesses the third-party page, the third-party application obtains the access token (access _ token) from the current operator application authentication platform according to the obtained authorization code (code), and the third-party application obtains the user right from the current operator application authentication platform after obtaining the access token (access _ token) to perform service handling, wherein a manner of obtaining the authorization code and the access token by the third-party application is the same as the method described in the second embodiment, and is not described herein.
To sum up, the method for controlling login of an operator application is described in the first to fourth embodiments, and when a user logs in different applications, the user only needs to obtain authorized login of other operator applications without obtaining an account and a password of the current login application, so that quick authorization between different applications is realized.
Fig. 6 is a schematic structural diagram of an operator application login control device according to a fifth embodiment of the present application. As shown in fig. 6, the apparatus includes: a receiving module 601, a first obtaining module 602, a second obtaining module 603, and a login module 604.
The receiving module is used for receiving a login request sent by a user to a third-party application, wherein the third-party application is a non-current operator application;
the first acquisition module is used for acquiring an authorization request sent by a third-party application to a current operator application, wherein the authorization request is used for the third-party operator application to acquire user account information stored by the current operator application;
the second acquisition module is used for acquiring an authorization instruction which corresponds to the authorization request and is applied by the current operator;
and the login module is used for logging in the third-party application through the user account information stored in the current operator application according to the authorization instruction.
Fig. 7 is a schematic structural diagram of an electronic device provided in the present application. As shown in fig. 7, the apparatus may include: at least one transceiver 701, a processor 702, and a memory 703. Fig. 7 shows an electronic device as an example of a processor.
The memory 703 is used for storing programs. In particular, the program may include program code including computer operating instructions.
The memory 703 may comprise high-speed RAM memory, and may also include non-volatile memory (non-volatile memory), such as at least one disk memory.
The processor 702 is configured to execute computer execution instructions stored in the memory 703 and control the receiving action and the sending action of the transceiver 701, so as to implement a method for operator application login control;
the processor 702 may be a Central Processing Unit (CPU), an Application Specific Integrated Circuit (ASIC), or one or more Integrated circuits configured to implement the embodiments of the present Application, and the processor 702 executes instructions stored in the memory 703 to implement the method for controlling the login of the operator Application.
Alternatively, in a specific implementation, if the receiver 701, the processor 702 and the memory 703 are implemented independently, the receiver 701, the processor 702 and the memory 703 may be connected to each other through a bus and perform communication with each other. The bus may be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, an Extended ISA (EISA) bus, or the like. Buses may be classified as address buses, data buses, control buses, etc., but not as having only one bus or type of bus.
Alternatively, in a specific implementation, if the receiver 701, the processor 702, and the memory 703 are integrated into a single chip, the receiver 701, the processor 702, and the memory 703 may complete communication through an internal interface.
The present application also provides a computer-readable storage medium, which may include: the computer-readable storage medium may be a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and may store program codes.
The present application also provides a program product comprising execution instructions stored in a readable storage medium. The at least one processor of the electronic device may read the execution instructions from the readable storage medium, and the execution of the execution instructions by the at least one processor causes the electronic device to implement the methods provided by the various embodiments described above.
Other embodiments of the present application will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the invention following, in general, the principles of the application and including such departures from the present disclosure as come within known or customary practice within the art to which the invention pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the application being indicated by the following claims.
It will be understood that the present application is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the application is limited only by the appended claims.
Claims (11)
1. An operator application login control method, comprising:
receiving a login request sent by a user to a third-party application, wherein the third-party application is a non-current operator application;
obtaining an authorization request sent by the third-party application to the current operator application, wherein the authorization request is used for the third-party operator application to obtain the user account information stored by the current operator application;
obtaining an authorization instruction of the current operator application corresponding to the authorization request;
and logging in the third-party application through the user account information stored in the current operator application according to the authorization instruction.
2. The method of claim 1, wherein the obtaining the authorization instruction of the operator application corresponding to the authorization request comprises:
generating an authorization interface according to the authorization request;
receiving an authorization indication input by a user through the authorization interface;
and acquiring an authorization instruction applied by the current operator according to the authorization instruction.
3. The method according to claim 2, wherein the logging in the third-party application through the user account information stored by the current operator application according to the authorization instruction comprises:
according to the authorization instruction, acquiring an authorization code generated by the current operator application, wherein the authorization code represents a certificate for the third-party application to acquire the authorization of the current operator application;
according to the authorization code, obtaining an access token of the third-party application for accessing the current operator application, wherein the access token is used for the third-party application to obtain user account information stored in the current operator application;
and logging in the third-party application through the user account information stored in the current operator application.
4. The method according to claim 3, wherein the authorization code includes permission information of the current operator application, which is allowed to be obtained by the third-party application, and the permission information includes one or more of a subscriber number, a subscriber number attribution area, a subscriber avatar, and a number type.
5. The method according to claim 1, wherein the obtaining of the authorization instruction of the current operator application corresponding to the authorization request is preceded by:
acquiring an authentication login request applied by the third-party application to an authentication platform of the current operator application;
and receiving authentication information sent by the current operator application to the third party application according to the authentication login request, wherein the authentication information is used for the third party application to acquire an authorization interface of the current operator application.
6. The method of claim 1, further comprising:
receiving a login request sent by a user to a current operator application;
obtaining an authorization request sent by the current operator application to the third-party application, wherein the authorization request is used for the current operator application to obtain the user account information stored by the third-party application;
obtaining an authorization instruction of the third-party application corresponding to the authorization request;
and logging in the current operator application through the user account information stored in the third-party application according to the authorization instruction.
7. The method of claim 6, wherein the logging in the current carrier application according to the authorization instruction through the user account information stored by the third-party application comprises:
acquiring a user identifier of the third-party application;
judging whether the user identification is bound with a user number in an authentication platform applied by the current operator;
and if the user identification is bound with a user number, logging in the current operator application through the user number.
8. The method of claim 7, further comprising:
if the user identification is not bound with the user number, generating a user number binding interface;
and receiving a user number input by a user through the binding interface, and logging in the current operator application through the user number.
9. An operator application login control apparatus, comprising:
the system comprises a receiving module, a login module and a login module, wherein the login request sent by a user to a third-party application is received, and the third-party application is a non-current operator application;
the first acquisition module is used for acquiring an authorization request sent by the third-party application to the current operator application, wherein the authorization request is used for the third-party operator application to acquire the user account information stored in the current operator application;
the second acquisition module is used for acquiring the authorization instruction of the current operator application corresponding to the authorization request;
and the login module is used for logging in the third-party application through the user account information stored in the current operator application according to the authorization instruction.
10. An electronic device, comprising: a processor, and a memory communicatively coupled to the processor;
the memory stores computer-executable instructions;
the processor executes computer-executable instructions stored by the memory to implement the method of any of claims 1 to 8.
11. A computer-readable storage medium having computer-executable instructions stored thereon, which when executed by a processor, are configured to implement the operator application login control method of any one of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111516732.2A CN114268474A (en) | 2021-12-13 | 2021-12-13 | Operator application login control method, device, equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111516732.2A CN114268474A (en) | 2021-12-13 | 2021-12-13 | Operator application login control method, device, equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114268474A true CN114268474A (en) | 2022-04-01 |
Family
ID=80826790
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111516732.2A Pending CN114268474A (en) | 2021-12-13 | 2021-12-13 | Operator application login control method, device, equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114268474A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104243433A (en) * | 2013-06-20 | 2014-12-24 | 腾讯科技（深圳）有限公司 | Logging-in method, device and system based on browser client-side account |
| CN104468487A (en) * | 2013-09-23 | 2015-03-25 | 华为技术有限公司 | Communication authentication method and device and terminal device |
| CN106953831A (en) * | 2016-01-06 | 2017-07-14 | 阿里巴巴集团控股有限公司 | A kind of authorization method of user resources, apparatus and system |
| CN109598115A (en) * | 2018-07-27 | 2019-04-09 | 北京字节跳动网络技术有限公司 | Authorize implementation method, device, equipment, system, platform and the medium logged in |
| CN113572718A (en) * | 2020-04-29 | 2021-10-29 | 华为技术有限公司 | Login method, login device, electronic equipment and storage medium |
-
2021
- 2021-12-13 CN CN202111516732.2A patent/CN114268474A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104243433A (en) * | 2013-06-20 | 2014-12-24 | 腾讯科技（深圳）有限公司 | Logging-in method, device and system based on browser client-side account |
| CN104468487A (en) * | 2013-09-23 | 2015-03-25 | 华为技术有限公司 | Communication authentication method and device and terminal device |
| CN106953831A (en) * | 2016-01-06 | 2017-07-14 | 阿里巴巴集团控股有限公司 | A kind of authorization method of user resources, apparatus and system |
| CN109598115A (en) * | 2018-07-27 | 2019-04-09 | 北京字节跳动网络技术有限公司 | Authorize implementation method, device, equipment, system, platform and the medium logged in |
| CN113572718A (en) * | 2020-04-29 | 2021-10-29 | 华为技术有限公司 | Login method, login device, electronic equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111131242A (en) | Authority control method, device and system | |
| CN106341234B (en) | Authorization method and device | |
| US20140052638A1 (en) | Method and system for providing a card payment service using a mobile phone number | |
| WO2014183526A1 (en) | Identity recognition method, device and system | |
| CN102821085A (en) | Third party authorization login method, open platform and system | |
| US7734279B2 (en) | Method and system for controlling resources via a mobile terminal, related network and computer program product therefor | |
| CN103685139A (en) | Authentication and authorization processing method and device | |
| WO2018000568A1 (en) | Virtual sim card management method, management device, server and terminal | |
| US9807075B2 (en) | Methods for activation of an application on a user device | |
| CN113065115B (en) | Authentication method for realizing security of small program login and without network isolation based on oauth2.0 | |
| CN110276184A (en) | A kind of cloud computing resources authorization method and device | |
| KR20130109322A (en) | Apparatus and method to enable a user authentication in a communication system | |
| CN106161475B (en) | Method and device for realizing user authentication | |
| JP2013541908A (en) | User account recovery | |
| CN111062023A (en) | Method and device for realizing single sign-on of multiple application systems | |
| CN106713315B (en) | Login method and device of plug-in application program | |
| CN111949959B (en) | Authorization authentication method and device in Oauth protocol | |
| CN112039878B (en) | Equipment registration method and device, computer equipment and storage medium | |
| CN107645474B (en) | Method and device for logging in open platform | |
| CN113901429A (en) | Access method and device of multi-tenant system | |
| KR20210011577A (en) | Apparatus and Method for Personal authentication using Sim Toolkit and Applet | |
| CN112565239B (en) | Authentication method, device, computer equipment and storage medium for integrating multiple operators | |
| KR102464011B1 (en) | Automatic login supporting server and method thereof | |
| US11968531B2 (en) | Token, particularly OTP, based authentication system and method | |
| CN114268474A (en) | Operator application login control method, device, equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |