CN110417723B - Application login method, device, terminal and storage medium - Google Patents

Application login method, device, terminal and storage medium Download PDF

Info

Publication number
CN110417723B
CN110417723B CN201910252704.0A CN201910252704A CN110417723B CN 110417723 B CN110417723 B CN 110417723B CN 201910252704 A CN201910252704 A CN 201910252704A CN 110417723 B CN110417723 B CN 110417723B
Authority
CN
China
Prior art keywords
user information
application
user
real
list
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.)
Active
Application number
CN201910252704.0A
Other languages
Chinese (zh)
Other versions
CN110417723A (en
Inventor
谢嘉雯
邓小俊
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangzhou Tencent Technology Co Ltd
Original Assignee
Guangzhou Tencent Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Guangzhou Tencent Technology Co Ltd filed Critical Guangzhou Tencent Technology Co Ltd
Priority to CN201910252704.0A priority Critical patent/CN110417723B/en
Publication of CN110417723A publication Critical patent/CN110417723A/en
Application granted granted Critical
Publication of CN110417723B publication Critical patent/CN110417723B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0407—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the identity of one or more communicating identities is hidden
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0815—Network architectures or network communication protocols for network security for authentication of entities providing single-sign-on or federations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

The embodiment of the invention discloses an application login method, an application login device, a terminal and a storage medium; the embodiment of the invention can receive an authorized login request initiated by a first application; triggering a second application to display a user information list according to the authorized login request, wherein the user information list comprises a plurality of pieces of user information used for logging in the first application, and the plurality of pieces of user information comprise real user information of the user in the second application and non-real user information of the user in the second application; selecting target user information for logging in a first application from the user information list; and when an authorization confirmation instruction is detected, logging in the first application based on the target user information. The scheme can improve the safety of user information.

Description

Application login method, device, terminal and storage medium
Technical Field
The invention relates to the technical field of communication, in particular to an application login method, an application login device, a terminal and a storage medium.
Background
And authorizing login means that when a user uses one application, the user uses user information authorized by another application to login the application. Since the user information needs to be authorized to the application to be logged in during the login process, illegal situations such as user information leakage and theft may occur, and the security of the user information is poor.
Disclosure of Invention
The embodiment of the invention provides an application login method, an application login device, a terminal and a storage medium, which can ensure the safety of user information.
The embodiment of the invention provides an application login method, which comprises the following steps:
receiving an authorized login request initiated by a first application;
triggering a second application to display a user information list according to the authorized login request, wherein the user information list comprises a plurality of pieces of user information used for logging in the first application, and the plurality of pieces of user information comprise real user information of the user in the second application and non-real user information of the user in the second application;
selecting target user information for logging in a first application from the user information list;
and when an authorization confirmation instruction is detected, logging in the first application based on the target user information.
Correspondingly, an embodiment of the present invention further provides an application login apparatus, including:
the receiving unit is used for receiving an authorized login request initiated by a first application;
the display unit is used for triggering the second application to display a user information list according to the authorized login request, wherein the user information list comprises a plurality of pieces of user information used for logging in the first application, and the plurality of pieces of user information comprise real user information of the user in the second application and non-real user information of the user in the second application;
the selection unit is used for selecting target user information for logging in the first application from the user information list;
and the login unit is used for logging in the first application based on the target user information when an authorization confirmation instruction is detected.
The terminal provided by the embodiment of the invention comprises a processor and a memory, wherein the memory stores a plurality of instructions, and the processor loads the instructions to execute the steps in any application login method provided by the embodiment of the invention.
In addition, an embodiment of the present invention further provides a storage medium, where the storage medium stores a plurality of instructions, and the instructions are suitable for being loaded by a processor to perform steps in any one of the login methods provided in the embodiments of the present invention.
The embodiment of the invention can receive an authorized login request initiated by a first application; triggering a second application to display a user information list according to the authorized login request, wherein the user information list comprises a plurality of pieces of user information used for logging in the first application, and the plurality of pieces of user information comprise real user information of the user in the second application and non-real user information of the user in the second application; selecting target user information for logging in a first application from the user information list; and when an authorization confirmation instruction is detected, logging in the first application based on the target user information. According to the scheme, the login application can be authorized by adopting the non-real user information, so that illegal conditions such as leakage and stealing of the real user information can be prevented, and the safety of the user information is improved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings required to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the description below are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained based on these drawings without creative efforts.
Fig. 1a is a schematic view of a scenario of an application login method according to an embodiment of the present invention;
FIG. 1b is a flowchart of an application login method according to an embodiment of the present invention;
FIG. 1c is a schematic diagram of a landing page provided by an embodiment of the present invention;
FIG. 1d is a schematic diagram of an authorized login page provided by an embodiment of the present invention;
FIG. 1e is another schematic diagram of an authorized login page provided by an embodiment of the invention;
FIG. 1f is another schematic diagram of an authorized login page provided by an embodiment of the invention;
FIG. 2a is a schematic diagram of a UI interaction of an application authorization login provided by an embodiment of the present invention;
FIG. 2b is a schematic diagram of another UI interaction for authorizing login by an application provided by the embodiment of the invention;
FIG. 2c is a schematic diagram of another UI interaction for authorizing login by an application provided by the embodiment of the invention;
FIG. 3a is another flowchart of application login provided by the embodiment of the present invention;
FIG. 3b is a flowchart illustrating a user login using authorization according to an embodiment of the present invention;
FIG. 3c is a diagram illustrating a technical implementation of authorized login for an application according to an embodiment of the present invention;
fig. 4a is a schematic structural diagram of an application login apparatus according to an embodiment of the present invention;
fig. 4b is another schematic structural diagram of an application login apparatus according to an embodiment of the present invention;
fig. 4c is another schematic structural diagram of an application login apparatus according to an embodiment of the present invention;
fig. 4d is another schematic structural diagram of an application login apparatus according to an embodiment of the present invention;
fig. 5 is a schematic structural diagram of a terminal according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The embodiment of the invention provides an application login method, an application login device, a terminal and a storage medium. The application device can be integrated into a terminal, and the terminal can be a mobile phone, a tablet computer, a notebook computer and other equipment.
Referring to fig. 1a, an embodiment of the present invention provides an application login system, which includes a terminal and a server; the terminal and the server are connected through a network, for example, a wired or wireless network connection, and the like.
The terminal is provided with a first application program (first application for short) and a second application program (second application for short) in an installing mode; the server may be a server of the second application. The first application and the second application may be different applications, i.e. heterogeneous applications, and in an embodiment, the first application may also be a sub-application running in the second application, such as an applet in the second application.
The applet is a mobile application program which is developed based on a specific programming language and can be used without downloading and installation, and can run on a cross-platform mobile client or application. The small program has the greatest characteristic of convenient use, and the user can open the application by scanning or searching without manually installing the small program in an operating system of the mobile terminal.
When the terminal needs to log in the first application, the terminal receives an authorized login request initiated by the first application; triggering a second application to display a user information list according to the authorized login request, wherein the user information list comprises a plurality of pieces of user information used for logging in the first application, and the plurality of pieces of user information comprise real user information of the user in the second application and non-real user information of the user in the second application; selecting target user information for logging in the first application from the user information list; and when the authorization confirmation instruction is detected, logging in the first application based on the target user information.
Specifically, when the authorization confirmation instruction is detected, the terminal may acquire the target user information from the server based on the information identifier of the target user information, and then log in the first application based on the target user information. For example, the terminal may encode the information identifier of the target user information, the application identifier of the second application, and the identity identifier of the user in the second application to obtain the authorization code; and acquiring target user information in the second application from the server of the second application based on the authorization code, and then logging in the first application by the terminal based on the target user information.
The following are detailed below. It should be noted that the following description of the embodiments is not intended to limit the preferred order of the embodiments.
The embodiment will be described from the perspective of an application login apparatus, which may be specifically integrated in a terminal or other devices; the terminal may include a mobile phone, a tablet Computer, a notebook Computer, and a Personal Computer (PC).
In the application login method provided in the embodiment of the present invention, the method may be executed by a processor of a terminal, as shown in fig. 1b, a specific process of the application login method may be as follows:
101. an authorized login request initiated by a first application is received.
In the embodiment of the present invention, the first application and the second application may be different applications, that is, heterogeneous applications. In one embodiment, the first application and the second application may be two different independent applications, for example, the first application may be a game application, the second application may be an instant messaging application, and the like.
In an embodiment, the first application may also be a sub-application running in a certain application, such as an applet, for example, a sub-application running in a second application, such as an applet. For example, the second application may be an instant messaging application, and the first application may be an applet in the instant messaging application, such as a shopping applet, a game applet, a servlet, and the like.
In an embodiment, the first application may also be a business service account in an application, such as a business service account in a second application, for example, a public number in an instant messaging application.
Furthermore, in some embodiments, the first application may also be a web page, such as a game web page, a shopping web page, and the like.
That is, the first application in the embodiment of the present invention may be in the form of an application program (APP), a web page, a public number, an applet, or the like.
For example, in an embodiment, a login page of the first application may be displayed, and the user may trigger the first application to initiate the authorized login request through the login page, and at this time, the application login device receives the authorized login request.
For example, the step "receiving an authorized login request initiated by a first application" may include: displaying a login page of a first application; when detecting the authorized login operation of the user aiming at the login page, triggering the first application to initiate the authorized login request, and receiving the authorized login request initiated by the first application, such as receiving the authorized login request through the second application. The authorized login operation may include a swipe, click, etc.
In an embodiment, in order to facilitate a user login operation and improve login efficiency, an authorized login control may be further set on a login interface of the first application, and the user may perform an operation (such as sliding, clicking, and the like) on the authorized login control to trigger the first application to initiate an authorized login request, where the application login device may receive the authorized login request. The representation display of the authorized login control can be various, for example, it can be an input box, an icon, a button, etc.
For example, referring to fig. 1c, the terminal may display a login page of the first application after running the first application, the login page including an authorized login button, i.e., "second application login"; when the user clicks the "second application login" button, the first application is triggered to initiate an authorized login request, and the terminal receives the request.
The authorization login request may carry information such as an application identifier of the first application, an application identifier of the authorization application, for example, an application identifier of the second application, and the like.
102. And triggering the second application to display a user information list according to the authorized login request, wherein the user information list comprises a plurality of user information for logging in the first application, and the plurality of user information comprises real user information of the user in the second application and non-real user information of the user in the second application.
The user information list may include a plurality of pieces of user information for logging in the first application, the user information list may include at least two pieces of user information for logging in the first application, and the number of the pieces of user information may be set according to an actual situation.
The user information may include at least one of an avatar, a nickname, a location, a gender, and other information, and may include an avatar and a nickname of the user, for example.
The real user information may include user information currently used by the user in the second application, for example, taking the second application as an instant messaging application as an example, the real user information may be user information currently used by the user when the user uses the instant messaging application for message interaction. In practical applications, the real user information may be user information of a user newly stored in the system of the second application, such as user information newly stored and bound to the user representation. For example, the real user information of the user a may be user information of the user a that is newly stored in the message interaction system.
It should be understood that: in the embodiment of the invention, the real user information is not required to be consistent with the real identity information of the user, and can be called as the real user information. For example, if the nickname and avatar currently used by the user in the second application are not consistent with the real name and personal avatar of the user, the currently used nickname and avatar are the real user information.
Wherein the non-real user information is defined with respect to the real user information, the non-real user information being user information distinguished from the real user information; both are different user information. For example, taking an avatar and a nickname as examples, the real user information includes an avatar and a nickname currently used by the user in the second application; the non-real user information includes an avatar, a nickname distinguished from a user currently using in the second application.
The distinguishing between the real user information and the non-real user information may include: the two characters are completely different, for example, the head portrait and the nickname are different, and may also include parts of the same character, the nickname, and the like.
It should be understood that: the non-real user information in the embodiment of the invention is not required to be used in the second application, and can be only used for authorized login.
In an embodiment, after receiving the authorized login request, the terminal obtains the jump link information of the second application according to the authorized login request; and opening the second application based on the jump link information, and simultaneously triggering the second application to display the user information list.
In an embodiment, in order to facilitate application login, a user information list may also be displayed through a page, and the specific display manner may include the following:
(1) display of existing non-real user information in user information list
The step of triggering the second application to display the user information list according to the authorized login request may include:
and triggering the second application to display an authorized login page according to the authorized login request, wherein the authorized login page comprises a user information list, and the user information list comprises real user information of the user in the second application and non-real user information of the user in the second application.
For example, the terminal may authorize the login request to directly trigger the second application to display an authorized login page, where the authorized login page includes a user information list, and the list may include real user information and non-real user information, in this case, the user information list already includes non-real user information, and the non-real user information may be non-real user information edited or used by the user at the historical time, for example, user information edited or used by the user at the historical time when the login is authorized.
In one embodiment, the authorization log-in page may further include other information, such as a reminder, for example, to remind the user that a different user information log-in application may be selected, or to remind the user that the log-in requesting application is authorized (e.g., application information of the first application, such as an application name, an icon, etc. of the first application), or may further include a reminder of the type of user information, such as a type of user information that the user needs to be reminded to use to log in the first application, such as a type of avatar, nickname, location, etc.
The presentation form of the user information in the user information list in the embodiment of the present invention may include multiple forms, for example, the user information may be displayed in the form of a control, such as a selection control. For example, the user information list may include a selection control corresponding to the user information, such as a selection control corresponding to a non-real user and a selection control corresponding to a real user. Therefore, the user can intuitively see the user information corresponding to the selection control, and can select the target user information required to be used by operating the selection control. For example, when the selection control is a check type control, the user may operate the check control corresponding to the user information on the authorization login page, and select the user information for logging in the application in a check manner.
In an embodiment, the user information list may further include an information protection control; the user can operate the information protection control to select an authorized login mode which does not provide user information, the information granted to the first application in the login mode only comprises the user identity of the user in the second application, and the user logs in the first application only based on the user identity; during the login process, the user information of the user in the second application, such as the user information (such as head portrait, nickname, etc.) bound or associated with the user identity is not used.
For example, taking the first application as application a and the second application as application b as an example, after receiving the authorized login request initiated by application a, the terminal may open application b according to the authorized login request, and at the same time, trigger application b to display an authorized login page, as shown in fig. 1d, where the authorized login page includes a user information list, the user information list includes real information of the user in application b, such as a real avatar, e.g., "avatar 1", and a nickname "youth", and the list may also include non-real user information of the user in application b, such as a non-real avatar, e.g., "avatar 2", and a nickname "smart me". The non-real avatar and nickname may be an avatar and nickname that the user previously edited in application b authorizes to log in to other applications, such as an avatar and nickname that may be edited or used for historical time, such as the last time the user authorized to log in to other applications.
In fig. 1d, the user information in the user information list in fig. 1d may be displayed in the form of a selection control, for example, in fig. 1d, both the real user information and the non-real information may be displayed in the selection control; the user may select target user information for logging into the first application through the selection control.
As shown in fig. 1d, the user information list further includes an information protection control, that is, "XX user does not provide information such as a head portrait and a nickname" in fig. 1 d. In practical application, a user can select an authorized login mode for operating the information protection control, such as selecting an option of 'the XX user does not provide information such as a head portrait and a nickname', so as to select user information such as the head portrait and the nickname, and the information granted to the first application in the login mode only includes a user identity of the user in the second application, and the user logs in the first application only based on the user identity; user information, such as user information (e.g., avatar, nickname, etc.) bound or associated with the user's identity in the second application is not granted or used during the login process.
In addition, as shown in fig. 1d, the authorization login page may further include information of an authorization request application, i.e., application b, such as a name, an application icon, and the like, and a prompt message prompting the user to select different user information for login.
(2) And displaying the information of the non-real user newly added by the user to the list
In one embodiment, in order to improve the user information security and the flexibility of user operation, the user may also edit the non-real user information so as to authorize the login use. For example, in the case of displaying the user information list through the authorized login page, a user information adding control may be set in the page, and the user may perform operation and editing on the control on the needed unreal user information.
For example, the step "triggering the second application to display the user information list according to the authorized login request" may include:
triggering a second application to display an authorized login page according to the authorized login request, wherein the authorized login page comprises a user information adding control and a user information list, and the user information list comprises real user information of a user in the second application;
displaying a user information editing page based on the operation of adding a control to the user information by the user;
acquiring unreal user information edited by a user through a user information editing page;
adding the edited unreal user information to a user information list of an authorized login page;
and triggering the second application to display the added authorized login page.
That is, the terminal may display an initial authorized login page according to the authorized login request, where the page may include a user information adding control and a user information list, and the user may edit new unreal user information through the user information adding control to authorize login.
The user information adding control can be located in various positions in the page, for example, in the user information list, or outside the user information list, or in the bottom, top, or other positions of the page.
The user information list in the authorized login page displayed according to the authorized login request may include the real user information of the user in the second application, for example, the user information list may include only the real user information of the user in the second application. The display mode of the user information may refer to the above description, such as displaying in a control mode.
For example, taking the first application as application a and the second application as application b as an example, after receiving an authorized login request initiated by application a, the terminal may open application b according to the authorized login request, and simultaneously trigger application b to display an authorized login page, as shown in fig. 1e, the authorized login page includes a user information adding control, i.e., a "new avatar nickname" button and a user information list, the user information list only includes real information of the user in application b, e.g., a real avatar nickname (e.g., "avatar 1" and "teenager"), and an information protection control, i.e., an "XX user does not provide information such as avatar and nickname".
In an embodiment, the user information list may further include non-real user information of the user in the second application. That is, in a scenario of adding or creating new user information, the user information list in the authorized login page initially triggered and displayed may include real user information of the user in the second application and non-real user information of the user in the second application. The non-real user information may be non-real user information edited or used by the user at the historical time, for example, the user information edited or used by the user at the historical time when login is authorized.
For example, taking the first application as application a and the second application as application b as an example, after receiving an authorized login request initiated by application a, the terminal may open application b according to the authorized login request, and at the same time, trigger application b to display an authorized login page, as shown in fig. 1d, where the authorized login page includes a user information add control, i.e., a "new avatar nickname" button, and a user information list, the user information list includes real information of the user in application b, e.g., a real avatar such as "avatar 1" and a nickname "youth", and the list may also include unreal user information of the user in application b, e.g., an unreal avatar such as "avatar 2" and a nickname "wisdom like me". The non-real avatar and nickname may be an avatar and nickname that the user previously edited in application b authorizes to log in to other applications, such as an avatar and nickname that may be edited or used for historical time, such as the last time the user authorized to log in to other applications.
In addition, the user information list may further include some other information, which may specifically refer to the above description, for example, including an information protection control; the authorized login page may also include other information, such as reminder information, application information for the first application, and so forth.
The user information editing page is a page for a user to edit user information, and the user can perform operations such as input operations on the page to edit required user information. When the editing is completed, the terminal can acquire the information of the non-real user edited by the user through the page.
In one embodiment, the user information editing page may include an avatar editing control and a nickname editing control; the avatar editing control and the nickname editing control can be represented in various forms, for example, the avatar editing control can be represented in the form of icons, buttons and the like, and the nickname editing control can be represented in the form of an input box and the like.
Under the condition that the user information editing page is provided with head portrait and nickname editing controls, the user can operate the two controls to edit the head portrait and the nickname information. For example, the step of "acquiring the non-real user information edited by the user through the user information editing page" may include:
acquiring a head portrait edited by a user based on the editing operation of the user on the head portrait editing control;
and acquiring the nickname edited by the user based on the editing operation of the user aiming at the nickname editing control.
The manner of obtaining the avatar based on the operation of the avatar editing control is various, for example, the image deformation processing (such as character deformation, background deformation or fuzzification) can be performed on the real avatar of the user according to the operation of the avatar editing control to obtain the non-real avatar; for another example, the camera may be directly called to take a picture to obtain a head portrait.
For another example, in an embodiment, in order to improve flexibility of avatar editing, a plurality of avatar editing modes may be provided for a user to select when the user operates the avatar editing control. Specifically, the step "obtaining the avatar edited by the user based on the editing operation of the user for the avatar editing control" may include:
when detecting the triggering operation of the user for the head portrait editing control operation, displaying a photographing control and an album selection control on a user information editing page;
when the triggering operation of the user for the photographing control is detected, calling a camera to carry out photographing, and acquiring a head portrait of the user based on a photographed image;
when the triggering operation of the user on the album selection control is detected, the head portrait of the user is obtained based on the image selected by the user from the album.
For example, referring to fig. 2a, after the user adds a button operation (e.g., clicking, sliding, etc.) of a control "new avatar nickname" to the user information in the authorized login page shown in fig. 1e, the user may trigger the terminal or the application b to display a user information editing page, such as the "new personal information" page in fig. 2 a. The "new personal information" page may include an avatar editing control "avatar" option and a nickname editing control "nickname" option.
The user can operate the head portrait option of the head portrait editing control to trigger the terminal to display a photographing control, namely a photographing option, and an album selection control, namely a selection from an album, in a new personal information page. At this time, the user can select to construct the head portrait by photographing or select to construct the head portrait by selecting images from the album.
For example, the user may operate a photographing control, that is, a "photographing" option, at this time, the terminal may invoke the camera to perform photographing based on the operation, and after the image is obtained by photographing, the user's avatar may be constructed based on the photographed image, for example, the size of the photographed image may be adjusted according to the size specified by the avatar.
For another example, the user may also operate an album selection control, i.e., "select from album", at which time, the terminal constructs a non-real avatar of the user based on the image selected by the user from the album, e.g., adjust the selected image according to a specified size of the avatar.
Referring to fig. 2a, the user may also input a nickname in the "nickname" input box, in which case the terminal may obtain the information on the unreal nickname input by the user. For example, after the user has edited the avatar "avatar X" in the above manner, a nickname, such as "wisdom-less" can be input in the "nickname" input box of the user information editing page, i.e., the "new personal information" page.
In an embodiment, in order to improve the user information editing efficiency, the non-real user information of the user in the second application may also be randomly generated. For example, a random generation control may be set on the user information editing page, so that the user may operate the random generation control to trigger random generation of the unreal user information.
For example, the step "acquiring non-real user information edited by the user through the user information editing page" may include: and when the triggering operation of the user for the randomly generated control is detected, randomly generating the non-real user information of the user in the second application.
For example, user information such as a head portrait, a nickname, and the like can be randomly downloaded from a network side as the unreal user information of the user in the second application. For another example, the terminal may randomly generate non-real user information such as a head portrait, a nickname, and the like locally.
For example, in one embodiment, a plurality of images may be selected in the local album to compose the avatar, so as to avoid the non-real user information such as the avatar from being consistent with the real user information such as the avatar. Specifically, the step of randomly generating the non-real user information of the user in the second application may include:
randomly selecting a plurality of images from a local photo album;
segmenting each image to obtain a segmentation area of each image;
and carrying out image synthesis on the segmented area of each image to obtain a non-true head portrait.
For example, referring to fig. 2a, the user information editing page, i.e., "new personal information" page, is further provided with a randomly generated control of user information, i.e., "random avatar and nickname"; when the user operates and triggers the randomly generated control, namely the random head portrait and the nickname, the terminal or the application b randomly generates information such as the unreal head portrait, the nickname and the like of the user in the application b.
In one embodiment, in order to improve the operation accuracy, the edited user information can be added to the user information list when the user finishes editing; editing may generally be considered complete when a user needs to save the edited information. Therefore, an information saving control such as a button can be arranged on the user information editing page, and the user can operate the information saving control to trigger the terminal to save the edited information and add the edited information to the user information list. For example, the user information editing page further includes an information saving control, and the step "adding the edited non-real user information to the user information list of the authorized login page" may include:
and when the saving operation of the user for the information saving control is detected, saving the edited unreal user information, and adding the edited unreal user information to a user information list of the authorized login page.
For example, the terminal may store the edited unreal user information locally, or may store the edited unreal user information in the server. In practical application, the limitation of cross-application information acquisition is considered, and the edited unreal user information can be stored in the server, so that the application to be logged in, namely the first application, can acquire the unreal user information from the server and log in by using the information.
For example, referring to fig. 2a, the "new personal information" page may further include an information saving control "save" button, which may be clicked when the user has edited the avatar and the nickname, at which point the terminal saves the edited avatar and nickname, e.g., may send to the server of application b, which may save the edited unreal user information in a separate store, e.g., in a store corresponding to the interface call credential accesstoken, such as tokenkv or the like. At the same time the terminal may return to displaying an authorized login page that includes a list of user information to which edited avatars and nicknames ("avatar X", "wisdom-minded") have been added. Specifically, the terminal may add the edited avatar and nickname to the user information list, and trigger the application b to display the added authorized login page.
(3) The user operates to randomly generate unreal user information and adds the unreal user information to the display of the user list;
for example, in an embodiment, after the authorized login page is displayed, the user may trigger generation of the non-real user information through the authorized login page, and the terminal may randomly generate the non-real user information and add the non-real user information to the user information list for display. For example, the step "triggering the second application to display the user information list according to the authorized login request" may include:
triggering the second application to display an authorized login page according to the authorized login request, wherein the authorized login page comprises a user information adding control and a user information list, and the user information list comprises real user information of the user in the second application (in an embodiment, the user information list may also comprise the real user information of the user in the second application);
when the triggering operation of the user for the information random increasing control is detected, generating unreal user information of the user in the second application at random;
and adding the randomly generated non-real user information into a user information list of the authorized login page for display.
Referring to fig. 2b, the first application is application a, the second application is application b, for example, after receiving an authorized login request initiated by application a, the terminal may open application b according to the authorized login request, and at the same time, trigger application b to display an authorized login page, where the authorized login page includes an information random add control "randomly generate a nickname for a head portrait", a user information add control "newly create nickname" button, and a user information list, where the user information list includes real information of the user in application b, such as a real head portrait, such as "head portrait 1" and a nickname "teenager".
The user can trigger the flow of self-defining the avatar and the nickname through a user information adding control, namely a 'newly built avatar nickname' button, and the specific self-defining flow can refer to the related description of the above fig. 2a and the like.
In addition, the user may further operate the random addition control "randomly generate the avatar nickname" to trigger the terminal to randomly generate the unreal user to add to the user information list for display, as shown in fig. 2b, when the user clicks the randomly generated avatar nickname ", the terminal may add the randomly generated" random avatar 1 "and the nickname" XX user 3 "to the user information list.
(4) And automatically randomly generating unreal user information and adding the unreal user information into the display of the user list:
in an embodiment, after receiving the authorized login request, whether the user information list has the non-real user information or not can be detected, and if not, the non-real user information is randomly generated and added to the list for display, so that the user can select the non-real user information, and the authorized login efficiency is improved.
For example, the step "triggering the second application to display the user information list according to the authorized login request" may include:
acquiring a user information list according to the authorized login request, wherein the user information list comprises user information used for logging in the first application;
when the fact that the user information list does not have the non-real user information is detected, the non-real user information of the user in the second application is randomly generated;
and adding the randomly generated unreal user information into the user information list, and triggering the second application to display the user information list.
For example, taking a first application as an application a and a second application as an application b as an example, after receiving an authorized login request initiated by the application a, the terminal may obtain a user information list of the user in the application b according to the authorized login request; detecting whether the user information list has non-real user information, if so, displaying an authorized login page containing the user information list, and referring to a page shown in fig. 1 d; if the user information does not exist, the non-real user information of the user in the application b, such as the head portrait and the nickname, can be randomly generated and added to the user information list, and the terminal can trigger the application b to display the information list containing the randomly generated non-real user information, as shown in fig. 1f, wherein the nickname "XX @" and the corresponding random head portrait are the randomly generated nickname and head portrait.
That is, in the embodiment of the present invention, the existing non-real user information in the user information list may include non-real user information edited or used by the user in the historical time, or may include non-real user information randomly generated in the current authorized login process.
Through the steps, the user information list containing the real user information and the non-real user information is displayed.
103. Target user information for logging in the first application is selected from the user information list.
After displaying the user information list, the terminal may select target user information from the list, in which the user logs in the first application. The target user information refers to user information currently used for logging in the first application.
The target user information may be real user information or non-real user information.
For example, the step "selecting target user information for logging in the first application from the user information list" may include: and using the selected non-real user information from the user information list as target user information for logging in the first application.
In an embodiment, in the case that the user information list is displayed using the authorized login page, the step of "selecting target user information for logging in the first application from the user information list" may include: and selecting target user information for logging in the first application from the user information list based on the selection operation of the user on the authorized login page.
For example, in the initial authorized login page, the user may select, operate and select the target user information on the page, or for example, in the authorized login page that is displayed after editing is completed, the user may also select, operate and select the target user information on the page.
In some embodiments, the non-real user information may be selected as the target user information by default, for example, in a scenario where the user creates new non-real user information, for example, a scenario where the user creates new non-real user information by himself or randomly generates non-real user information, the new non-real user information may be selected from the list as the target user information, for example, the new non-real user information may be selected as the target user information by default.
For example, referring to fig. 2a, after the user triggers the avatar nickname editing process through the "newly created avatar nickname" button, the authorized login page with the newly created avatar nickname added thereto may be returned to display, and at this time, the terminal may default to select the newly created avatar nickname as the target avatar nickname of the login application a. As can be seen from fig. 2a, the newly created avatar nickname ("avatar X", "minuscule of wisdom") is in the selected state.
For another example, referring to fig. 2b, when the user clicks "randomly generated avatar nickname", the terminal may add "random avatar 1" and nickname "XX user 3" that are randomly generated to the user information list, return to and display an authorized login page, where the page is added with the random avatar nickname "random avatar 1" and nickname "XX user 3", at this time, the random avatar nickname is in a selected state, that is, the default randomly created avatar nickname is the target avatar nickname for the login user a.
In an embodiment, in a scenario of creating new non-real user information, when a user information list includes a plurality of pieces of non-real user information, the selected target user information may not be newly created or created non-real user information, or may be existing non-real user information in the list. For example, the terminal may select existing non-real user information from the list as the target user information based on a selection operation of the user for the list.
For example, referring to fig. 2c, taking the page shown in fig. 1d as an example, the authorized login page includes a user information adding control, i.e., a "new avatar nickname" button, and a user information list, the user information list includes real information of the user in application b, such as a real avatar ("avatar 1" "youth"), and the list may also include non-real user information of the user in application b, such as a non-real avatar, such as "avatar 2" and a nickname "smart me".
After the user adds a control "new avatar nickname" button operation (such as clicking, sliding, etc.) to the user information in the page, the terminal or the application b may be triggered to display a user information editing page, such as the "new personal information" page in fig. 2 c. The "new personal information" page may include an avatar editing control "avatar" option and a nickname editing control "nickname" option.
The user can edit the avatar and the nickname through the option of head portrait and the nickname editing control option of nickname, or randomly generate the avatar and the nickname through the button of random avatar and nickname. For example, the user can use the custom or randomly generated avatar nickname "avatar 4" or "smart XX"; the information editing process of fig. 2a described above may be referred to in particular as the editing process. And when the user finishes editing, the terminal returns to display an authorized login page, wherein the page comprises a real avatar nickname 'avatar 1' and 'teenagers', a non-real avatar nickname 'avatar 2' and 'locomotive wisdom me' which exist before, and a newly-built avatar nickname 'avatar 4' and 'smart XX'. At the moment, the terminal defaults to select a newly-built avatar nickname; however, the user may make a selection operation change on the page, for example, the user selects the existing unreal avatar nickname "avatar 2" or "smart me" as the target avatar nickname to log in the application a.
In an embodiment, when the user information list already has the non-real user information, the already-existing non-real user information can be directly selected as the target user information, and no new non-real user information is needed.
For example, referring to fig. 1d, the list of user information authorized to log in includes real information of the user in application b, such as a real avatar, e.g., "avatar 1", and a nickname "youth", and the list may also include non-real user information of the user in application b, such as a non-real avatar, e.g., "avatar 2", and a nickname "smart me". At the moment, the user can directly select the existing unreal head portrait "head portrait 2" and the nickname "smart me" as the nickname of the target head portrait without newly building the nickname of the head portrait. Or the terminal selects the existing non-real user information as the target user information by default. As with reference to fig. 1d, after the authorized login page is displayed, the avatar nickname "avatar 2" and "minwisdom me" are in a selected state, i.e., the default randomly existing unreal avatar nickname is the target avatar nickname for login user a.
In an embodiment, the real user information may also be selected from the user information list as the target user information, for example, after the new creation of the non-real user information, the user may select the real user information, for example, referring to fig. 2a, after the new creation of the avatar nickname, the user may also select the real avatar nickname "avatar 1" or "youth" as the final avatar nickname for the login application a.
Or, under the condition that no user information is newly established and non-real user information and real user information already exist, the real user information can be directly selected without a new establishing process.
104. And when the authorization confirmation instruction is detected, logging in the first application based on the target user information.
For example, when the authorization confirmation instruction is detected, the information identifier of the target user information, the application identifier of the second application, and the identity identifier of the user in the second application may be encoded by the second application to obtain an authorization code (code); triggering the first application to obtain an interface calling certificate (such as accesstocken) from a server of the second application based on the authorization code; triggering the first application to acquire target user information of the second application from the server based on the interface calling certificate; and triggering the first application to perform login operation based on the target user information.
In an embodiment, a terminal may trigger a first application to send a credential obtaining request to a server of a second application, where the request may carry an authorization code, an application identifier (appid) of the first application, and an application key (appsecret); after receiving the request, the server may verify the application identifier and the application key, and if the verification is passed, the server performs a decoding operation on the authorization code to obtain decoded information, where the decoded information includes: the information identification of the target user information, the application identification of the second application and the identity identification of the user in the second application. The server can distribute the corresponding interface calling certificate based on the decoding information and send the certificate to the terminal. The terminal triggers the first application to acquire target user information corresponding to the information identification from the server based on the interface calling certificate, and then logs in the first application based on the target user information.
For example, in the case that the user information list is displayed through the authorization login page, the user may trigger the authorization confirmation instruction by operating the authorization login page, and at this time, the authorization confirmation instruction may be detected.
In one embodiment, an authorization confirmation control can be set on the authorization login page, and an authorization confirmation instruction is triggered when a user operates the authorization confirmation control. For example, referring to fig. 1d, 1e, and 1f, an authorization confirmation control such as an "agreement" button and an authorization rejection control such as a "rejection" button are provided on the authorization login page; when the user selects target user information such as a head portrait nickname on the authorized login page, the "agree" button may be operated, for example, clicked, to trigger the authorization confirmation instruction, and at this time, the terminal may detect that the authorization confirmation instruction triggers the login operation of the application b. When the user needs to refuse the authorized login, the user can operate the authorization refusing control, such as a 'refusing' button, for example, clicking and the like to trigger the authorization refusing instruction, and at the moment, the terminal refuses the authorized login.
For another example, referring to fig. 2a, when the edited avatar is returned to display the authorized login page, the authorized login page is provided with an authorization confirmation control such as an "accept" button and an authorization rejection control such as a "reject" button; when a user selects target user information such as a head portrait nickname (for example, the head portrait nickname which can be edited by default is the target head portrait nickname) on an authorized login page, an "agree" button can be operated, for example, clicked, to trigger an authorization confirmation instruction, and at this time, the terminal can detect that the authorization confirmation instruction triggers the login operation of the application b. When the user needs to reject the authorized login, the user can operate the authorization rejection control, such as a rejection button, for example, clicking and the like to trigger an authorization rejection instruction, and at the moment, the terminal rejects the authorized login.
Similarly, in the scenarios of random generation by user operation and automatic random generation by the system, the authorization login page may be provided with an authorization confirmation control such as an "agreement" button and an authorization rejection control such as a "rejection" button, so that the user triggers an authorization confirmation instruction or rejects an authorization instruction and the like.
As can be seen from the above, the embodiment of the present invention may receive an authorized login request initiated by a first application; triggering a second application to display a user information list according to the authorized login request, wherein the user information list comprises a plurality of pieces of user information used for logging in the first application, and the plurality of pieces of user information comprise real user information of the user in the second application and non-real user information of the user in the second application; selecting target user information for logging in the first application from the user information list; and when the authorization confirmation instruction is detected, logging in the first application based on the target user information. According to the scheme, the non-real user can be provided for logging in the third-party application in the authorized logging process, and the safety of user information can be improved.
The scheme can also provide various user information such as real user information, non-real user information and the like for logging in the third application, and on the premise of improving the safety, the diversity and the flexibility of authorized logging in are improved.
In addition, the scheme can also allow the user to edit the information of the unreal user for logging in the third-party application, and the user can edit the information according to the actual requirement, so that the personalized requirement of the user can be met, and the interactivity of authorized logging in can be improved.
The method described in the above examples is further illustrated in detail below by way of example.
The method of the embodiment of the invention will be described by taking the case that the application login device is integrated on the terminal.
As shown in fig. 3a, an application login method specifically includes the following steps:
301. the terminal triggers the first application to initiate an authorized login request to the second application.
For example, the terminal displays a login page of a first application, and triggers the first application to initiate an authorized login request to a second application based on an authorized login operation of a user on the login page.
302. And the terminal triggers a second application to display an authorized login page according to the authorized login request, wherein the authorized login page comprises a user information adding control and a user information list.
The user information list can comprise a plurality of user information used for logging in the first application; for example, the user information list may only include the actual user information of the user at the second application, such as the authorized login page shown with reference to fig. 2 a. In an embodiment, the user information list may include real user information and non-real user information of the user in the second application, for example, refer to fig. 1d and the like. The authorization page may contain a real avatar nickname, a non-real avatar nickname.
For example, referring to fig. 3b, taking a third-party application in which the second application is an instant messaging application and the first application is an instant messaging application as an example, after the third-party application initiates an authorized login, the terminal may pull up the instant messaging client to display an authorized login page; the authorized login page may include a user information list, which may include real user information and non-real user information of the user in the instant messaging client. The user may select real user information in the list of pages, performing step 306, or select existing non-real user information, performing step 307.
303. And the terminal displays a user information editing page based on the operation of adding the control to the user information by the user.
For example, referring to fig. 2a, after adding a button operation (e.g., clicking, sliding, etc.) of a control "new avatar nickname" to the user information in the authorized login page, the terminal or application b may be triggered to display a user information editing page, such as the "new personal information" page in fig. 2 a. The "new personal information" page may include an avatar editing control "avatar" option and a nickname editing control "nickname" option.
304. The terminal acquires the unreal user information edited by the user through the user information editing page.
For example, referring to fig. 2a, the user may edit the avatar and the nickname through the avatar editing control and the nickname editing control, and the specific editing process may refer to the description of the above embodiments.
For another example, referring to fig. 2a, the user information editing page, i.e., the "new personal information" page, is further provided with a randomly generated control of the user information, i.e., "random avatar and nickname"; when the user operates the randomly generated control, namely the random head portrait and the nickname, the terminal or the application b is triggered to randomly generate information such as the unreal head portrait, the nickname and the like of the user in the application b.
In addition, other ways of randomly generating the avatar nickname may be specifically referred to the description of the above embodiments.
305. When the storage operation of the information storage control in the user information editing page is detected, the edited unreal user information is stored, the edited unreal user information is added to a user information list of the authorized login page, and the added authorized login page is displayed.
For example, referring to fig. 2a, the "new personal information" page may further include an information saving control "save" button, which may be clicked when the user has edited the avatar and the nickname, at which time, the terminal saves the edited avatar and nickname, for example, the terminal may send the saved avatar and nickname to a server of the application b, and the server may save the edited unreal user information in a separate storage, for example, a storage corresponding to the interface call credential accesstoken, such as tokenkv. At the same time the terminal may return to displaying an authorized login page that includes a list of user information to which edited avatars and nicknames ("avatar X", "wisdom-minded") have been added. Specifically, the terminal may add the edited avatar and nickname to the user information list, and trigger the application b to display the added authorized login page.
Referring to fig. 3b, when the user does not select the existing non-real user information, the user edits and creates a new non-real user information such as editing a head portrait, a nickname, etc. to log in the third party application; after the editing is finished, the user can save the edited information.
For example, referring to fig. 1d or fig. 1e, the user may select a new avatar nickname without selecting an existing real avatar nickname and an existing non-real avatar nickname, and the user may click a new avatar nickname button to enter an avatar nickname editing process, where the specific process may refer to the related contents shown in fig. 2a and described above. When the editing is finished, the user can click a 'save' button to save the edited avatar nickname, and at the moment, the terminal can add the edited avatar nickname to the list of the authorized login page for display.
306. The terminal selects the real user information from the user information list as the target user information for logging in the first application, and goes to step 308.
For example, referring to fig. 3b, when the real user information exists in the user information list, the user may directly select the real user information as the target user information for logging in the first application; for example, referring to FIG. 1d or FIG. 1e, the user may select the real avatar nickname "avatar 1" or "youth" to log into the third party application. Alternatively, referring to FIG. 2a, the user may directly select an existing real avatar nickname as the target avatar nickname to log into the third party application.
307. The terminal selects an existing non-real user from the user information list as target user information for logging in the first application, and goes to step 308.
For example, referring to fig. 3b, when real user information and non-real user information exist in the user information list, the user may select the non-real user information existing in the list as target user information for logging in the first application, instead of selecting the real user information.
When the user selects the existing non-real user information instead of the real user information, the user can select the non-real user information to be used in the list; and when the user clicks an authorization confirmation control in the authorization login page when the user agrees to authorization, such as 'agreement', the terminal can log in the third-party application based on the selected unreal user information. For example, referring to FIG. 1d, the user may select an existing non-real avatar nickname such as "avatar 2" or "mentally me" to log into the third party application.
308. When the confirmation operation of the user for the authorization confirmation control in the authorization login page is detected, the terminal logs in the first application based on the target user information selected by the user from the user information list.
In the new avatar nickname scenario, referring to fig. 3b, after the edited avatar nickname is saved, the user may approve the authorization by operation, and after the authorization is approved, the user may log in the third-party application based on the currently selected avatar nickname.
For example, referring to fig. 2a and 2b, after editing the avatar nickname, the terminal may return to display the authorized login page, at which point, the terminal may default to create the edited avatar nickname as the target avatar nickname for logging in the first application; when the user clicks the "agree" button on the page, the terminal can log in to the first application based on the default target avatar nickname.
In one embodiment, after editing the avatar nickname display authorization login page, the user may not select the default avatar nickname for login, or may operate on the page to select other avatar nicknames for login. For example, referring to FIG. 2a, after editing the display authorization login page, the user may select the real avatar nickname "avatar 1" or "youth" to log in to the third party application.
In a scenario where a real avatar nickname or an unreal avatar nickname is selected, referring to fig. 1d or fig. 1d, after selecting the avatar nickname, the user may click an "accept" button in the page, and at this time, the terminal may log in to the third-party application based on the selected avatar nickname.
Referring to fig. 3c, specifically, when the terminal detects a user authorization confirmation operation, that is, when the user agrees to authorization, the instant messaging application, that is, the second application may obtain an information identifier of target user information, an application identifier of the instant messaging application (in some embodiments, an identifier of a third party application), and an identity identifier of the user in the second application, and then encode these information to obtain an authorization code (code). And sending an authorization code to the third-party application, and pulling up or redirecting the third-party application. The third party application sends a certificate code acquisition request to a background server of the instant messaging application, wherein the request carries an authorization code, a third party identifier (apprequest) and an application key (apprechet); the backend server may return a corresponding interface call credential (e.g., accesstaken) to the third-party application based on the credential code acquisition request. The third-party application can call a user information interface (such as userinfo, namely, an interface for acquiring user information in a login process) provided by the backend server based on the interface call certificate (such as accesstocken) to acquire target user information such as head portrait nickname and the like from the backend server, and then login is carried out based on the acquired target user information.
The background server may query the storage (e.g., KV storage) corresponding to the interface calling credential (e.g., accesstaken), and return the target user information corresponding to the interface calling credential (e.g., accesstaken) to the third-party application.
The scheme provided by the embodiment of the invention can support the user not to use the real head portrait and the nickname to log in the third-party application, and simultaneously can store the unreal information which is selected by the user to log in the same application before, so that the user does not need to reset, the use threshold of the user is reduced, and the user privacy data is also ensured.
In order to better implement the method, correspondingly, the embodiment of the invention also provides an application login device, wherein the application login device can be specifically integrated into a terminal, and the terminal can be a mobile phone, a tablet computer, a notebook computer and other equipment.
For example, as shown in fig. 4a, the application login apparatus may include a receiving unit 401, a display unit 402, a selecting unit 403, and a login unit 404, as follows:
a receiving unit 401, configured to receive an authorized login request initiated by a first application;
a display unit 402, configured to trigger the second application to display a user information list according to the authorized login request, where the user information list includes a plurality of pieces of user information for logging in the first application, where the plurality of pieces of user information include real user information of the user in the second application and non-real user information of the user in the second application;
a selecting unit 403, configured to select target user information for logging in a first application from the user information list;
a login unit 404, configured to log in the first application based on the target user information when an authorization confirmation instruction is detected.
In an embodiment, the display unit 402 may be specifically configured to: triggering a second application to display an authorized login page according to the authorized login request, wherein the authorized login page comprises a user information list, and the user information list comprises real user information of a user in the second application and non-real user information of the user in the second application;
the selecting unit 403 may be specifically configured to select, based on a selection operation of the user on the authorized login page, target user information for logging in the first application from the user information list.
In an embodiment, referring to fig. 4b, the display unit 402 may include:
the first display subunit 4021 is configured to trigger the second application to display an authorized login page according to the authorized login request, where the authorized login page includes a user information adding control and a user information list, and the user information list includes real user information of a user in the second application;
an editing subunit 4022, configured to display a user information editing page based on an operation of a user on the user information addition control;
an obtaining subunit 4023, configured to obtain unreal user information edited by the user through the user information editing page;
an adding subunit 4024, configured to add the edited unreal user information to the user information list of the authorized login page;
the second display subunit 4025 is configured to trigger the second application to display the added authorized login page.
In one embodiment, the user information editing page further comprises an information saving control; an add subunit 4024 to: and when the storage operation of the user for the information storage control is detected, storing the edited unreal user information, and adding the edited unreal user information to the user information list of the authorized login page.
In an embodiment, the selecting unit 403 may be specifically configured to select, based on a selection operation of the user on the authorized login page, target user information for logging in the first application from the user information list.
In one embodiment, the user information editing page comprises a head portrait editing control and a nickname editing control; the non-real user information comprises a non-real head portrait and a nickname;
the obtaining subunit 4023 may specifically be configured to:
acquiring a head portrait edited by a user based on the editing operation of the user on the head portrait editing control;
and acquiring the nickname edited by the user based on the editing operation of the user aiming at the nickname editing control.
In an embodiment, the obtaining subunit 4023 may be specifically configured to:
when detecting the triggering operation of the user for the operation of the head portrait editing control, displaying a photographing control and an album selection control on the user information editing page;
when the triggering operation of the user for the photographing control is detected, calling a camera to carry out photographing, and acquiring a head portrait of the user based on a photographed image;
when the triggering operation of the user on the album selection control is detected, the head portrait of the user is obtained based on the image selected by the user from the album.
In one embodiment, the user information editing page includes a randomly generated control; the obtaining subunit 4023 may specifically be configured to:
and when the triggering operation of the user for the randomly generated control is detected, randomly generating the unreal user information of the user in the second application.
In an embodiment, the non-real user information includes a non-real avatar, and the obtaining subunit 4023 may specifically be configured to:
randomly selecting a plurality of images from a local photo album;
segmenting each image to obtain a segmentation area of each image;
and carrying out image synthesis on the segmented area of each image to obtain a non-true head portrait.
In an embodiment, referring to fig. 4c, the display unit 402 may include:
the page display subunit 4026 is configured to trigger the second application to display an authorized login page according to the authorized login request, where the authorized login page includes an information random addition control and a user information list, and the user information list includes real user information of the user in the second application;
a random generation subunit 4027, configured to randomly generate, when it is detected that the user performs a trigger operation on the information random increase control, non-real user information of the user in the second application;
an adding and displaying subunit 4028, configured to add the randomly generated non-real user information to the user information list of the authorized login page for display.
In an embodiment, the display unit 402 may be specifically configured to:
acquiring a user information list according to the authorized login request, wherein the user information list comprises user information used for logging in a first application;
when detecting that the user information list does not have non-real user information, randomly generating the non-real user information of the user in a second application;
and adding the randomly generated unreal user information into the user information list, and triggering a second application to display the user information list.
In an embodiment, referring to fig. 4d, the login unit 404 may include:
the encoding subunit 4041 is configured to encode, by the second application, the information identifier of the target user information, the application identifier of the second application, and the identity identifier of the user in the second application, so as to obtain an authorization code;
a first trigger subunit 4042, configured to trigger the first application to obtain an interface invocation credential from the server of the second application based on the authorization code;
a second triggering subunit 4043, configured to trigger the first application to acquire, from the server, target user information of the second application based on the interface invocation credential;
a third triggering subunit 4044, configured to trigger the first application to perform a login operation based on the target user information.
In an embodiment, the selecting unit 403 may specifically be configured to: and using the selected non-real user information from the user information list as target user information for logging in the first application.
In specific implementation, the above units may be implemented as independent entities, or may be combined arbitrarily, and implemented as the same or several entities, and specific implementations of the above units may refer to the foregoing method embodiment, which is not described herein again.
As can be seen from the above, the application login apparatus of the embodiment can receive an authorized login request initiated by a first application through the receiving unit 401; triggering, by the display unit 402, the second application to display a user information list according to the authorized login request, where the user information list includes a plurality of pieces of user information for logging in the first application, where the plurality of pieces of user information include real user information of the user in the second application and non-real user information of the user in the second application; selecting target user information for logging in a first application from the user information list by a selection unit 403; logging in the first application based on the target user information when an authorization confirmation instruction is detected by the logging in unit 404. According to the scheme, the non-real user information can be adopted, so that illegal conditions such as leakage and stealing of the real user information can be prevented, and the safety of the user information is improved.
In addition, an embodiment of the present invention further provides a terminal, as shown in fig. 5, which shows a schematic structural diagram of the terminal according to the embodiment of the present invention, specifically:
the terminal may include components such as a processor 501 of one or more processing cores, memory 502 of one or more computer-readable storage media, a power supply 503, and an input unit 504. Those skilled in the art will appreciate that the terminal structure shown in fig. 5 is not intended to be limiting and may include more or fewer components than those shown, or some components may be combined, or a different arrangement of components. Wherein:
the processor 501 is a control center of the terminal, connects various parts of the entire terminal using various interfaces and lines, and performs various functions of the terminal and processes data by running or executing software programs and/or modules stored in the memory 502 and calling data stored in the memory 502, thereby performing overall monitoring of the terminal. Optionally, processor 501 may include one or more processing cores; preferably, the processor 501 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, etc., and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 501.
The memory 502 may be used to store software programs and modules, and the processor 501 executes various functional applications and data processing by operating the software programs and modules stored in the memory 502. The memory 502 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application program required by at least one function (such as a sound playing function, an image playing function, etc.), and the like; the storage data area may store data created according to the use of the terminal, and the like. Further, the memory 502 may include high speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device. Accordingly, the memory 502 may also include a memory controller to provide the processor 501 with access to the memory 502.
The terminal further comprises a power supply 503 for supplying power to the various components, and preferably, the power supply 503 may be logically connected to the processor 501 through a power management system, so that functions of managing charging, discharging, power consumption, and the like are realized through the power management system. The power supply 503 may also include any component of one or more dc or ac power sources, recharging systems, power failure detection circuitry, power converters or inverters, power status indicators, and the like.
The terminal may also include an input unit 504, and the input unit 504 may be used to receive input numeric or character information and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control.
Although not shown, the terminal may further include a display unit and the like, which will not be described in detail herein. Specifically, in this embodiment, the processor 501 in the terminal loads the executable file corresponding to the process of one or more application programs into the memory 502 according to the following instructions, and the processor 501 runs the application programs stored in the memory 502, so as to implement various functions as follows:
receiving an authorized login request initiated by a first application; triggering a second application to display a user information list according to the authorized login request, wherein the user information list comprises a plurality of pieces of user information used for logging in the first application, and the plurality of pieces of user information comprise real user information of the user in the second application and non-real user information of the user in the second application; selecting target user information for logging in a first application from the user information list; and when an authorization confirmation instruction is detected, logging in the first application based on the target user information.
The above operations can be implemented in the foregoing embodiments, and are not described in detail herein.
As can be seen from the above, the terminal of this embodiment may receive an authorized login request initiated by the first application; triggering a second application to display a user information list according to the authorized login request, wherein the user information list comprises a plurality of pieces of user information used for logging in the first application, and the plurality of pieces of user information comprise real user information of the user in the second application and non-real user information of the user in the second application; selecting target user information for logging in a first application from the user information list; and when an authorization confirmation instruction is detected, logging in the first application based on the target user information. According to the scheme, the non-real user information can be adopted, so that illegal conditions such as leakage and stealing of the real user information can be prevented, and the safety of the user information is improved.
It will be understood by those skilled in the art that all or part of the steps of the methods of the above embodiments may be performed by instructions or by associated hardware controlled by the instructions, which may be stored in a computer readable storage medium and loaded and executed by a processor.
To this end, embodiments of the present invention further provide a storage medium, in which a plurality of instructions are stored, where the instructions can be loaded by a processor to execute steps in any one of the application login methods provided in the embodiments of the present invention. For example, the instructions may perform the steps of:
receiving an authorized login request initiated by a first application; triggering a second application to display a user information list according to the authorized login request, wherein the user information list comprises a plurality of pieces of user information used for logging in the first application, and the plurality of pieces of user information comprise real user information of the user in the second application and non-real user information of the user in the second application; selecting target user information for logging in a first application from the user information list; and when an authorization confirmation instruction is detected, logging in the first application based on the target user information.
The above operations can be implemented in the foregoing embodiments, and are not described in detail herein.
Wherein the storage medium may include: read Only Memory (ROM), Random Access Memory (RAM), magnetic or optical disks, and the like.
Since the instructions stored in the storage medium can execute the steps in any application login method provided in the embodiments of the present invention, the beneficial effects that can be achieved by any application login method provided in the embodiments of the present invention can be achieved, which are detailed in the foregoing embodiments and will not be described herein again.
The application login method, the application login device and the storage medium provided by the embodiment of the invention are described in detail, a specific example is applied in the description to explain the principle and the implementation of the invention, and the description of the embodiment is only used for helping to understand the method and the core idea of the invention; meanwhile, for those skilled in the art, according to the idea of the present invention, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present invention.

Claims (14)

1. An application login method, comprising:
receiving an authorized login request initiated by a first application;
triggering a second application to display a user information list according to the authorized login request, wherein the user information list comprises a plurality of pieces of user information used for logging in the first application, the plurality of pieces of user information comprise real user information of the user in the second application and non-real user information of the user in the second application, the real user information comprises user information currently used by the user in the second application, and the non-real user information is user information which is different from the real user information;
using the selected non-real user information from the user information list as target user information for logging in the first application;
and when an authorization confirmation instruction is detected, logging in the first application based on the target user information.
2. The application login method of claim 1, wherein triggering a second application to display a list of user information according to the authorized login request comprises:
triggering a second application to display an authorized login page according to the authorized login request, wherein the authorized login page comprises a user information list, and the user information list comprises real user information of a user in the second application and non-real user information of the user in the second application;
selecting target user information for logging in a first application from the user information list, including: and selecting target user information for logging in the first application from the user information list based on the selection operation of the user on the authorized login page.
3. The application login method of claim 1, wherein triggering a second application to display a list of user information according to the authorized login request comprises:
triggering a second application to display an authorized login page according to the authorized login request, wherein the authorized login page comprises a user information adding control and a user information list, and the user information list comprises real user information of a user in the second application;
displaying a user information editing page based on the operation of adding a control to the user information by the user;
acquiring non-real user information edited by a user through the user information editing page;
adding the edited unreal user information to a user information list of the authorized login page;
and triggering the second application to display the added authorized login page.
4. The application login method of claim 3, wherein the user information editing page comprises an avatar editing control and a nickname editing control; the non-real user information comprises a non-real head portrait and a nickname;
acquiring the unreal user information edited by the user through the user information editing page, wherein the unreal user information comprises the following steps:
acquiring a head portrait edited by a user based on the editing operation of the user on the head portrait editing control;
and acquiring the nickname edited by the user based on the editing operation of the user aiming at the nickname editing control.
5. The application login method of claim 4, wherein obtaining the avatar edited by the user based on the user's editing operation with respect to the avatar editing control comprises:
when detecting the triggering operation of the user for the operation of the head portrait editing control, displaying a photographing control and an album selection control on the user information editing page;
when the triggering operation of the user for the photographing control is detected, calling a camera to carry out photographing, and acquiring a head portrait of the user based on a photographed image;
when the triggering operation of the user for the album selection control is detected, the head portrait of the user is obtained based on the image selected by the user from the album.
6. The application login method of claim 3, wherein the user information editing page comprises a randomly generated control;
acquiring the unreal user information edited by the user through the user information editing page, wherein the unreal user information comprises the following steps:
and when the triggering operation of the user for the randomly generated control is detected, randomly generating the unreal user information of the user in the second application.
7. The application login method of claim 6, wherein the non-real user information comprises a non-real avatar;
randomly generating non-real user information of the user in the second application, wherein the non-real user information comprises:
randomly selecting a plurality of images from a local photo album;
segmenting each image to obtain a segmentation area of each image;
and carrying out image synthesis on the segmented area of each image to obtain a non-true head portrait.
8. The application login method of claim 1, wherein triggering a second application to display a list of user information according to the authorized login request comprises:
triggering a second application to display an authorized login page according to the authorized login request, wherein the authorized login page comprises an information random increasing control and a user information list, and the user information list comprises real user information of a user in the second application;
when the triggering operation of the user for the information random increasing control is detected, generating unreal user information of the user in the second application at random;
and adding the randomly generated non-real user information into a user information list of the authorized login page for display.
9. The application login method of claim 1, wherein triggering a second application to display a list of user information according to the authorized login request comprises:
acquiring a user information list according to the authorized login request, wherein the user information list comprises user information used for logging in a first application;
when detecting that the user information list does not have non-real user information, randomly generating the non-real user information of the user in a second application;
and adding the randomly generated unreal user information into the user information list, and triggering a second application to display the user information list.
10. The application login method of claim 3, wherein the user information editing page further comprises an information saving control;
adding the edited non-real user information to a user information list of the authorized login page, wherein the steps comprise:
and when the storage operation of the user for the information storage control is detected, storing the edited unreal user information, and adding the edited unreal user information to the user information list of the authorized login page.
11. The application login method of claim 1, wherein logging in the first application based on the target user information comprises:
coding the information identifier of the target user information, the application identifier of the second application and the identity identifier of the user in the second application through the second application to obtain an authorization code;
triggering the first application to acquire an interface calling certificate from a server of the second application based on the authorization code;
triggering the first application to acquire target user information of the second application from the server based on the interface calling certificate;
and triggering the first application to perform login operation based on the target user information.
12. An application login apparatus, comprising:
the receiving unit is used for receiving an authorized login request initiated by a first application;
the display unit is used for triggering the second application to display a user information list according to the authorized login request, wherein the user information list comprises a plurality of pieces of user information used for logging in the first application, the plurality of pieces of user information comprise real user information of a user in the second application and non-real user information of the user in the second application, the real user information comprises user information currently used by the user in the second application, and the non-real user information is user information which is different from the real user information;
the selection unit is used for taking the selected non-real user information from the user information list as target user information for logging in the first application;
and the login unit is used for logging in the first application based on the target user information when an authorization confirmation instruction is detected.
13. A terminal comprising a processor and a memory, said memory storing a plurality of instructions, said processor loading said instructions to perform the steps in the application login method of any one of claims 1 to 11.
14. A storage medium storing instructions adapted to be loaded by a processor to perform the steps of the application login method of any one of claims 1 to 11.
CN201910252704.0A 2019-03-29 2019-03-29 Application login method, device, terminal and storage medium Active CN110417723B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201910252704.0A CN110417723B (en) 2019-03-29 2019-03-29 Application login method, device, terminal and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201910252704.0A CN110417723B (en) 2019-03-29 2019-03-29 Application login method, device, terminal and storage medium

Publications (2)

Publication Number Publication Date
CN110417723A CN110417723A (en) 2019-11-05
CN110417723B true CN110417723B (en) 2022-05-06

Family

ID=68357546

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201910252704.0A Active CN110417723B (en) 2019-03-29 2019-03-29 Application login method, device, terminal and storage medium

Country Status (1)

Country Link
CN (1) CN110417723B (en)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110958234B (en) * 2019-11-22 2020-11-17 腾讯科技（深圳）有限公司 Application login control method and device and storage medium
CN111405016B (en) * 2020-03-09 2023-02-17 广州方硅信息技术有限公司 User information acquisition method and related equipment
CN111970298B (en) * 2020-08-26 2024-01-05 腾讯科技（深圳）有限公司 Application access method and device, storage medium and computer equipment
JP2022057801A (en) * 2020-09-30 2022-04-11 株式会社リコー Service providing system, information processing system, control method and program
CN113536402A (en) * 2021-07-19 2021-10-22 军事科学院系统工程研究院网络信息研究所 Peep-proof display method based on front camera shooting target identification

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105812398A (en) * 2016-06-06 2016-07-27 百度在线网络技术（北京）有限公司 Remote login authorization method and remote login authorization device
CN107438071A (en) * 2017-07-28 2017-12-05 北京信安世纪科技有限公司 cloud storage security gateway and access method
CN107623690A (en) * 2017-09-27 2018-01-23 上海掌门科技有限公司 Login method, equipment and storage medium

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106130881B (en) * 2016-07-07 2019-10-22 腾讯科技（深圳）有限公司 A kind of account number login method and device

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105812398A (en) * 2016-06-06 2016-07-27 百度在线网络技术（北京）有限公司 Remote login authorization method and remote login authorization device
CN107438071A (en) * 2017-07-28 2017-12-05 北京信安世纪科技有限公司 cloud storage security gateway and access method
CN107623690A (en) * 2017-09-27 2018-01-23 上海掌门科技有限公司 Login method, equipment and storage medium

Also Published As

Publication number Publication date
CN110417723A (en) 2019-11-05

Similar Documents

Publication Publication Date Title
CN110417723B (en) Application login method, device, terminal and storage medium
US10065119B2 (en) Game accessing method and processing method, server, terminal, and system
CN109587044B (en) Group creation and message interaction method and device
CN110348236B (en) File operation authority setting method and device and storage medium
US11258810B2 (en) Identity authentication method, apparatus, and system
CN106233718A (en) Display video call data
CN106416195A (en) Actionable notifications
CN109391476B (en) Network communication method, device and system
CN109586930B (en) Conference user adding method, first terminal, second terminal and processing server
CN106105110A (en) Instant message transmission
CN108133523A (en) Door-access control method and device
CN112242948B (en) Group session processing method and device, computer equipment and storage medium
US20220240073A1 (en) Methods, apparatuses, terminals, and storage media for transmitting and responding to assistance request
CN105392141A (en) Device control method and device
CN111857498B (en) Data interaction method and device and electronic equipment
CN111338971B (en) Application testing method and device, electronic equipment and storage medium
CN110995706B (en) Authentication system, method, device and storage medium for communication application
CN111723353A (en) Identity authentication method, device, terminal and storage medium based on face recognition
CN110661789B (en) Address resetting method, device, equipment and computer readable storage medium
CN112291420B (en) Message display method and terminal equipment
CN116938501A (en) Authentication method, device, storage medium, and program product
CN113420133A (en) Session processing method, device, equipment and storage medium
CN104580070B (en) BlueDrama confirmation method, apparatus and system
CN113099307A (en) Data interaction method and device, electronic equipment and storage medium
CN117041506B (en) Screen projection control method and device, screen projection receiving end and computer readable 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
GR01 Patent grant
GR01 Patent grant