WO2016173199A1 - 一种移动应用单点登录方法及装置 - Google Patents
一种移动应用单点登录方法及装置 Download PDFInfo
- Publication number
- WO2016173199A1 WO2016173199A1 PCT/CN2015/090563 CN2015090563W WO2016173199A1 WO 2016173199 A1 WO2016173199 A1 WO 2016173199A1 CN 2015090563 W CN2015090563 W CN 2015090563W WO 2016173199 A1 WO2016173199 A1 WO 2016173199A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- application
- pseudo
- single sign
- user
- password
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
Definitions
- the present invention relates to the field of single sign-on, and in particular, to a mobile application single sign-on method and apparatus.
- SSO is one of the more popular solutions for enterprise business integration. SSO is defined in multiple applications, users only need to log in once to access all trusted applications.
- the application system can identify the user who has logged in, and can automatically determine whether the current user has logged in, thereby automatically completing the login function.
- the SSO implementation mechanism is that when the user accesses the application system A for the first time, because it has not logged in, it will be directed to the authentication system for login; according to the login information provided by the user, the authentication system performs identity verification if After verification, the user should return a certified credential ticket; when the user accesses another application, the ticket will be taken as the credential for the authentication. After receiving the request, the application will send the ticket to the authentication system. Check and check the legality of the ticket. If the verification is passed, the user can access the application system B and the application system C without logging in again.
- the embodiment of the invention provides a mobile application single sign-on method and device, which can at least avoid modifying the mobile application client and the server source code to implement single sign-on.
- a mobile application single sign-on method including:
- the terminal When the mobile application single sign-on is performed for the first time, the terminal will carry the user login information via the pseudo single sign-on server, Sending, by the application server, the first login verification request of the application, the first login verification request of the application identifier to the application server, so that the pseudo single sign-on server obtains the pseudo password after the application server verifies the first login verification request;
- the terminal acquires the pseudo password from the pseudo single sign-on server by using the user identifier to log in to the second application;
- the terminal performs the single sign-on processing of the second application by using the user login information and the pseudo password.
- the user login information of the first application and the second application are the same, and are associated with each other by the user identifier.
- the terminal Before the terminal sends the first login verification request carrying the user login information, the package name of the first application, and the user identifier to the application server via the pseudo single sign-on server, the terminal intercepts the carried user login information used for the mobile application single sign-on for the first time. The request, and adding the package name and user identifier of the first application to the request, forming a first login verification request.
- the user login information includes a user account and a password
- the step of the terminal performing the single sign-on processing of the second application by using the user login information and the pseudo password includes:
- the terminal intercepts a request for carrying a user account and a pseudo password for performing mobile application single sign-on again;
- the password is replaced with a password and sent to the application server for login verification.
- a mobile application single sign-on method including:
- the pseudo single sign-on server sends the received first login verification request carrying the user login information, the package name of the first application, and the user identifier to the application server;
- the pseudo single sign-on server After the application server verifies the first login verification request, the pseudo single sign-on server acquires a pseudo password, and saves the login information, a package name of the first application, a user identifier, and a pseudo password;
- the pseudo single sign-on server sends the saved pseudo password to the terminal by using the received package name and user identifier of the second application from the terminal, so that the terminal utilizes the pseudo Password for single sign-on processing of the second application;
- the user login information of the first application and the second application are the same, and are associated with each other by the user identifier.
- the user login information includes a user account and a password.
- the pseudo single sign-on server After the pseudo single sign-on server sends the saved pseudo password to the terminal, the pseudo single sign-on server receives the packet carrying the user account, the pseudo password, and the second application.
- a mobile application single sign-on device including:
- the client request interceptor is configured to send the first login verification request carrying the user login information, the package name of the first application, and the user identifier to the application server via the pseudo single sign-on server when the mobile application single sign-on is performed for the first time.
- Make The pseudo single sign-on server acquires a pseudo password after the application server verifies the first login verification request;
- Automatically logging in to the processor configured to acquire the pseudo password from the pseudo single sign-on server by using the user identifier when the mobile application single sign-on is performed again, and use the user login information and the pseudo password to perform the first Two applications for single sign-on processing;
- the user login information of the first application and the second application are the same, and are associated with each other by the user identifier.
- the client request interceptor intercepts the mobile application single sign-on for the first time before sending the first login verification request carrying the user login information, the package name of the first application, and the user identifier to the application server via the pseudo single sign-on server
- the user login information includes a user account and a password
- the client requests an interceptor to intercept a request for carrying a user account and a pseudo password for performing mobile application single sign-on again, and adding a package name of the second application to the request.
- the user identifier is formed into a second login verification request, and sent to the pseudo single sign-on server, where the pseudo single sign-on server replaces the pseudo password in the second login verification request with a password, and sends the password to the application server for login verification.
- a mobile application single sign-on device including:
- the transceiver module is configured to: when the terminal performs the single sign-on of the mobile application for the first time, send the received first login verification request carrying the user login information, the package name of the first application, and the user identifier to the application server;
- Obtaining a module after the application server verifies the first login verification request, acquiring a pseudo password, and saving the user login information, a package name of the first application, a user identifier, and a pseudo password;
- the processing module is configured to: when the terminal performs the mobile application single sign-on again, send the saved pseudo password to the terminal through the transceiver module by using the received package name and user identifier of the second application from the terminal, for the terminal to utilize The pseudo password is used for performing single sign-on processing of the second application;
- the user login information of the first application and the second application are the same, and are associated with each other by the user identifier.
- the user login information includes a user account and a password.
- the processing module receives, by using the transceiver module, a second user name, a pseudo password, a second application, and a user identifier.
- the pseudo password in the second login verification request is replaced with a password, and then sent to the corresponding application server for login verification via the transceiver module.
- the embodiment of the present invention can implement the function of “one-time login and multiple use” without changing the client and server source code of the application, thereby avoiding the trouble of the user inputting the user login information such as the user name and the password multiple times, and also reducing the application.
- FIG. 1 is a schematic block diagram of a first method for mobile application single sign-on provided by an embodiment of the present invention
- FIG. 2 is a block diagram of a first device for mobile application single sign-on provided by an embodiment of the present invention
- FIG. 3 is a schematic block diagram of a second method for mobile application single sign-on provided by an embodiment of the present invention.
- FIG. 4 is a block diagram of a second apparatus for mobile application single sign-on provided by an embodiment of the present invention.
- FIG. 5 is a flowchart of a single sign-on of a mobile application according to an embodiment of the present invention.
- FIG. 6 is a flow chart of a packer provided by an embodiment of the present invention.
- FIG. 1 is a schematic block diagram of a first method for mobile application single sign-on according to an embodiment of the present invention. As shown in FIG. 1 , the steps include:
- Step S101 When the mobile application single sign-on is performed for the first time, the terminal sends the first login verification request carrying the user login information (including the user account and password), the package name of the first application, and the user identifier to the pseudo single sign-on server to the first login verification request.
- the application server causes the pseudo single sign-on server to acquire a pseudo password after the application server verifies the first login verification request.
- the terminal Before the terminal sends the first login verification request carrying the user login information, the package name of the first application, and the user identifier to the application server via the pseudo single sign-on server, the terminal intercepts the carried user login information used for the mobile application single sign-on for the first time. The request, and adding the package name and user identifier of the first application to the request, forming a first login verification request.
- Step S102 When the mobile application single sign-on is performed again, the terminal acquires the pseudo password from the pseudo single sign-on server by using the user identifier to automatically log in to the second application.
- Step S103 The terminal performs single sign-on processing of the second application by using the user login information and the pseudo password.
- the terminal After the terminal simulates the user inputting the user account and the pseudo password, the terminal generates a request for carrying the user account and the pseudo password for the mobile application single sign-on, the terminal intercepts the request, and adds the package name of the second application to the request.
- the user identifier forms a second login verification request and is sent to the pseudo single sign-on server, so that the pseudo single sign-on server replaces the pseudo password in the second login verification request with a password and sends it to the application server for login verification.
- the user login information of the first application and the second application are the same, and are associated with each other by the user identifier. That is to say, one user identifier can be associated with multiple mobile applications having the same user account and password, so that even if the second application is the first login, automatic login can be realized without the user manually inputting the user account and password again. To achieve single sign-on for multiple mobile apps with the same account.
- terminals in the foregoing steps S101 and S102 may be the same terminal, or may be different ends. At the end, when the two terminals are different, the application single sign-on across the terminal is implemented.
- the specific use scenario of the present invention is to implement the single sign-on function of the application itself, single sign-on of multiple mobile applications with the same account, and single sign-on of the application across the terminal without modifying the original system source code.
- FIG. 2 is a block diagram of a first apparatus for mobile application single sign-on according to an embodiment of the present invention.
- the client includes a client request interceptor 11 and an automatic login processor 12 disposed on a mobile terminal side.
- the client request interceptor 11 is configured to carry the user login information (including the user account and password), the package name of the first application, and the first login of the user identifier via the pseudo single sign-on server when the mobile application single sign-on is performed for the first time. Sending the verification request to the application server, so that the pseudo single sign-on server obtains the pseudo password after the application server verifies the first login verification request, and saves the user account, the password, the package name of the first application, User ID and pseudo user.
- the client request interceptor 11 intercepts the mobile application list for the first time before sending the first login verification request carrying the user login information, the package name of the first application, and the user identifier to the application server via the pseudo single sign-on server. Clicking on the request for carrying the user login information, and adding the package name and the user identifier of the first application to the request, forming a first login verification request.
- the automatic login processor 12 is configured to acquire the pseudo password from the pseudo single sign-on server by using the user identifier when the mobile application single sign-on is performed again, and use the user login information and the pseudo password to perform the first Two applications for single sign-on processing. Specifically, the automatic login processor 12 automatically simulates the user account and the pseudo password obtained by the user input operation, and issues a request for carrying the user account and the pseudo password for the mobile application single sign-on again, at this time, the client requests The interceptor 11 intercepts the request, adds the package name and the user identifier of the second application to the request, forms a second login verification request, and sends the request to the pseudo single sign-on server for the pseudo single sign-on server to use the second The pseudo password in the login verification request is replaced with a password and sent to the application server for login verification.
- the first application and the second application have the same user account and password, and are associated with the same user identifier, thereby implementing the single sign-on function of the application itself, single sign-on of multiple mobile applications with the same account, and application orders across terminals. Click Login.
- FIG. 3 is a schematic block diagram of a second method for mobile application single sign-on according to an embodiment of the present invention. As shown in FIG. 3, the steps include:
- Step S201 When the terminal performs mobile application single sign-on for the first time, the pseudo single sign-on server sends the first login verification request that carries the user login information (including the user account and password), the package name of the first application, and the user identifier. To the application server.
- the pseudo single sign-on server sends the first login verification request that carries the user login information (including the user account and password), the package name of the first application, and the user identifier.
- Step S202 After the application server verifies the first login verification request, the pseudo single sign-on server acquires a pseudo password, and saves the user login information, the package name of the first application, the user identifier, and the pseudo password.
- Step S203 When the terminal performs the mobile application single sign-on again, the pseudo single sign-on server sends the saved pseudo password to the terminal by using the received package name and user identifier of the second application, so that the terminal uses the pseudo The password is used for single sign-on processing of the second application.
- the user login information of the first application and the second application are the same, and are associated with each other by the user identifier.
- the pseudo single sign-on server After the pseudo single sign-on server sends the saved pseudo password to the terminal, the pseudo single sign-on server receives the second login verification request that carries the user account, the pseudo password, the package name of the second application, and the user identifier, and After the pseudo password in the second login verification request is replaced with a password, it is sent to the corresponding application server for verification. After the verification is completed, the verification result is returned to the terminal through the pseudo single sign-on server.
- FIG. 4 is a block diagram of a second apparatus for mobile application single sign-on according to an embodiment of the present invention. As shown in FIG. 4, the method includes a transceiver module 21, an obtaining module 22, and a processing module 23 disposed on a pseudo single sign-on server.
- the pseudo single sign-on server is disposed between the terminal and the application server.
- the transceiver module 21 is configured to send the received first login verification request carrying the user login information (including the user account and password), the package name of the first application, and the user identifier to the application server when the terminal performs the single sign-on of the mobile application for the first time. .
- the first login verification request of the transceiver module 21 carrying the user account, the password, the user identifier, and the package name of the first application is sent to the application server, and the user identity is verified by the application server, and after the verification is completed, Return the verification result to the terminal.
- the obtaining module 22 is configured to acquire a pseudo password after the application server verifies the first login verification request, and save the user login information, a package name of the first application, a user identifier, and a pseudo password.
- the obtaining module 22 may automatically generate a pseudo password after confirming that the first login verification request passes the verification.
- the pseudo password may be pre-configured.
- the processing module 23 is configured to, when the terminal performs the mobile application single sign-on again, send the saved pseudo password to the terminal via the transceiver module 21 through the received package name and user identifier of the second application from the terminal, for the terminal.
- the single sign-on processing of the second application is performed using the pseudo password.
- the processing module 23 receives, via the transceiver module, a second login verification request that carries a user account, a pseudo password, a package name of the second application, and a user identifier, and the second After the pseudo password in the login verification request is replaced with a password, it is sent to the corresponding application server via the transceiver module 21 for login verification.
- the user login information account and password of the first application and the second application are the same, and are associated with each other by the user identifier.
- FIG. 1 to Figure 4 can be implemented by applying the shelling method, including four parts: the shelling implementation, the mobile device management (MDM) manager, the shell code engineering function, and the pseudo SSO server part.
- MDM mobile device management
- APK applications that require pseudo-single sign-on use the shelling technology to incorporate the pseudo-single-login shell code into the app APK, so that users must pass the pseudo-single sign-on when using the APK app after the shelling
- the control system can use the subsequent functions of the application.
- Packing uses the ApkTool tool to first decompile the original APK, then merge the pseudo SSO shell code and resources into the decompiled original APK, including processing the AndroidManifest.xml file, merging string.xml and other resource files, and then merging them using the ANT script tool.
- the post project is repackaged into an APK.
- the MDM Manager application is used to generate a unique user ID, which is set to implement single sign-on across terminals. If single sign-on for a single terminal does not use the MDM Manager, only the device's unique mobile device international ID (International Mobile) is required. Equipment Identity, IMEI) or MAC address as a unique identifier.
- International Mobile International Mobile
- the MDM manager provides an AIDL service, and when the user logs in to the MDM manager application, a unique user identifier is generated.
- the unique user identifier is obtained from the AIDL service, and the user identifier is carried to the pseudo.
- SSO server after logging in to the MDM manager with the same account on another device, and then logging in to the associated packaged application, the unique user identifier is retrieved from the ADM service of the MDM manager and sent to the pseudo SSO server to obtain the pseudo login. Information to achieve automatic login.
- the shell code project implements two functions, namely the client request interceptor and the automatic login processor function.
- the enterprise application's request is generally HTTP. Therefore, you can add device information (IMEI, MAC address), application package name information, and then carry the information in the login request. Boot to the pseudo SSO server.
- the proxy interception technology is used here, and the proxy interception technology is implemented based on the proxy server.
- the application's login request is first transferred to its own interceptor, and after adding additional devices, user IDs, and application package name information, the request is forwarded to the pseudo SSO server.
- the automatic login processor obtains the user name and pseudo password that have been logged in from the pseudo SSO server, and automatically fills in the entered user name and pseudo password into the input box of the corresponding login interface, and then automatically logs in.
- the pseudo SSO server needs to automatically log in to the application, including the application package name, login url, request message format, identification field of the user name and password, pseudo password, response message format, identification of whether the login is successful, and which applications belong to the associated application.
- the same username and password in order to correctly resolve the login request, and forward the request to the real application authentication server.
- the application server informs the authentication success, save the login user name, password, package name, tag, etc. Prepare information data.
- the shell code project automatically logs in to the processor's control module.
- the user name and pseudo password are obtained from the pseudo SSO server, and when the login page is transferred, the user name, pseudo password, and the like are automatically input to implement automatic login.
- the embodiment of the present invention does not verify the validity of the user through a unified ticket. Instead, when the user accesses the system for the first time, the user's login information is recorded to the unified user management platform, and the user accesses the system or other users later. When the related system obtains the login information of the user from the user platform, the simulated user inputs the user login information and automatically logs in.
- FIG. 5 is a flowchart of a single sign-on of a mobile application according to an embodiment of the present invention, including the following steps:
- Step 1.1 When the user accesses the application system 1 for the first time, because the user has not logged in, the user logs in through the login interface;
- Step 1.2 Intercept the login request, carry a unique identifier (imei, mac or other identifier), application package name, and guide the user to log in to the pseudo SSO server.
- a unique identifier e.g., mac or other identifier
- Step 1.3 The pseudo SSO server directs the login request to the authentication system of the application server for identity verification.
- Step 1.4 The application server returns the verification result, for example by verification.
- Step 1.5 The pseudo SSO server saves the login information of the user.
- Step 2.1 The user accesses this application or another related application, such as application system 2.
- Step 2.2 Bring the application unique identifier (imei, mac or other identifier), the application package name, and send it to the pseudo SSO server to obtain the user account and the pseudo password.
- the application unique identifier mei, mac or other identifier
- Step 2.3 The pseudo SSO server obtains a pseudo password according to the unique identifier.
- Step 2.4 Send the pseudo password to the terminal and go to the login interface, automatically simulate the user to fill in the obtained user account and pseudo password, and automatically log in.
- Step 2.5 After booting the login request to the pseudo SSO server, replace the pseudo password with the real password;
- Step 2.6 Forward the request to the authentication system of the application server for verification, and check the legitimacy of the user and the real password.
- Step 2.7 The application server returns the verification result, for example, by checking, so that the user can access the application system 2 and the application system 3 without manually logging in.
- FIG. 6 is a flow chart of a packer provided by an embodiment of the present invention. As shown in FIG. 6, the method includes the following steps:
- Step S301 Packing starts.
- Step S302 APKTool decompiles the original APK file.
- Step S303 Copy the pseudo SSO shell project to the target directory.
- Step S304 merge the AndroidManifest.xml of the pseudo SSO project and the AndroidManifest.xml of the original APK, except that the application name is modified to the application name of the pseudo SSO shell, and other application information is modified to the original APK information, and the entry activity is modified to pseudo SSO. Shell activity.
- Step S305 merge the pseudo-SSO project and the decompressed original APK resource file
- Step S306 The packaged merged directory is the packaged APK.
- Step S307 The filling is completed.
- the embodiment of the present invention can also support pseudo single sign-on with multiple accounts and pseudo single sign-on across terminals.
- the pseudo single sign-on with multiple accounts needs to be configured on the pseudo SSO server to determine which applications belong to the same system. As long as one of the applications has been logged in, other applications can be started according to the client application package name and unique identification information.
- the pseudo SSO server configuration information is obtained by automatically logging in to the login account and pseudo password that other applications have logged in.
- the pseudo single sign-on across the terminal is implemented by the MDM manager application.
- the user first logs in to the manager to generate unique tag information.
- tag information and the application package name are transmitted.
- the pseudo-SSO server saves the login user name and password.
- the application login is obtained according to the client application registration, tag information, and pseudo SSO server configuration information.
- the account and pseudo password are automatically logged in. .
- the solution of the embodiment of the present invention is simple to use, and only needs to provide a terminal application installation package, and a pseudo SSO shell can be added for the application, without modifying the source code of the third party, and the single sign-on function can be implemented by combining the pseudo SSO server. Save business costs and reduce the potential risks of secondary development.
- the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation.
- the technical solution of the present invention which is essential or contributes to the prior art, may be embodied in the form of a software product stored in a storage medium (such as ROM/RAM, disk,
- the optical disc includes a number of instructions for causing a terminal device (which may be a cell phone, a computer, a server, or a network device, etc.) to perform the methods described in various embodiments of the present invention.
- each of the above modules may be implemented by software or hardware.
- the foregoing may be implemented by, but not limited to, the foregoing modules are all located in the same processor; or, the modules are located in multiple In the processor.
- Embodiments of the present invention also provide a storage medium.
- the foregoing storage medium may include Including but not limited to: U disk, Read-Only Memory (ROM), Random Access Memory (RAM), mobile hard disk, disk or optical disk, and other media that can store program code.
- the mobile application single sign-on method and apparatus provided by the embodiments of the present invention have the following beneficial effects: the embodiment of the present invention can implement "one-time login" without changing the client and server source code of the application.
- the function of “multiple use” avoids the trouble of user inputting user login information such as user name and password multiple times, and can also reduce the cost and risk of re-development of the application.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Telephonic Communication Services (AREA)
Abstract
本发明公开了一种移动应用单点登录方法及装置,所述方法包括:当首次进行移动应用单点登录时,终端经由伪单点登录服务器将携带用户登录信息、第一应用的包名、用户标识的第一登录验证请求发送至应用服务器,使所述伪单点登录服务器在所述应用服务器验证所述第一登录验证请求之后,获取伪密码;当再次进行移动应用单点登录时,终端利用所述用户标识,从所述伪单点登录服务器获取所述伪密码,以登录第二应用;终端利用所述用户登录信息和伪密码,进行第二应用的单点登录处理;其中,所述第一应用和第二应用的用户登录信息相同,并通过所述用户标识相互关联。本发明实现多个移动应用的单点登录和跨终端的应用单点登录。
Description
本发明涉及单点登录领域,特别涉及一种移动应用单点登录方法及装置。
随着移动智能终端设备、手机越来越普及,促进了移动互联网平台下各种新兴业务的快速展开和应用。在时间不断的推移和移动互联网高歌猛进推进下,各个公司企业纷纷上马了自己的移动应用,单个公司的移动应用越来越多,很多应用本身没有实现自动登录功能,而且相同账号的移动应用也不能做到单点登录。
因此在使用这些应用时,并不方便。用户每次使用,都必须输入用户名称和用户密码,进行身份验证;而且应用不同,用户账号就不同,用户必须同时牢记多套用户名称和用户密码。特别是对于应用数目较多,用户数目也很多,这个问题就尤为突出。问题的原因并不是应用开发出现失误,而是缺少整体规划,缺乏统一的用户登录平台,使用单点登录(Single Sign On,SSO)技术可以解决以上这些问题。
SSO是目前比较流行的企业业务整合的解决方案之一。SSO的定义是在多个应用系统中,用户只需要登录一次就可以访问所有相互信任的应用系统。应用系统能够识别已经登录过的用户,能自动判断当前用户是否登录过,从而自动完成登录功能。
传统意义上的SSO实现机制是当用户第一次访问应用系统A的时候,因为还没有登录,会被引导到认证系统中进行登录;根据用户提供的登录信息,认证系统进行身份校验,如果通过校验,应该返回给用户一个认证的凭据ticket;用户再访问别的应用的时候就会将这个ticket带上,作为自己认证的凭据,应用系统接受到请求之后会把ticket送到认证系统进行校验,检查ticket的合法性。如果通过校验,用户就可以在不用再次登录的情况下访问应用系统B和应用系统C了。
由于移动互联网领域人员流动性很大,系统众多,因此没有更多时间维护改造系统,在这种没有人力又需要实现自动登录功能的情况下,投入人力强行更改原系统的风险很大,成本也很高,通过使用伪SSO可以很好的解决这方面问题。
发明内容
本发明实施例提供了一种移动应用单点登录方法及装置,至少能更好地避免修改移动应用客户端和服务端源代码来实现单点登录。
根据本发明的一个实施例,提供了一种移动应用单点登录方法,包括:
当首次进行移动应用单点登录时,终端经由伪单点登录服务器将携带用户登录信息、第
一应用的包名、用户标识的第一登录验证请求发送至应用服务器,使所述伪单点登录服务器在所述应用服务器验证所述第一登录验证请求之后,获取伪密码;
当再次进行移动应用单点登录时,终端利用所述用户标识,从所述伪单点登录服务器获取所述伪密码,以登录第二应用;
终端利用所述用户登录信息和伪密码,进行第二应用的单点登录处理;
其中,所述第一应用和第二应用的用户登录信息相同,并通过所述用户标识相互关联。
终端经由伪单点登录服务器将携带用户登录信息、第一应用的包名、用户标识的第一登录验证请求发送至应用服务器之前,终端拦截用来首次进行移动应用单点登录的携带用户登录信息的请求,并在所述请求中加入第一应用的包名、用户标识,形成第一登录验证请求。
所述用户登录信息包括用户账号和密码,所述的终端利用所述用户登录信息和伪密码,进行第二应用的单点登录处理的步骤包括:
终端拦截用来再次进行移动应用单点登录的携带用户账号和伪密码的请求;
在所述请求中加入第二应用的包名、用户标识,形成第二登录验证请求,并发送至伪单点登录服务器,以供伪单点登录服务器将所述第二登录验证请求中的伪密码替换为密码后发送至应用服务器进行登录验证。
根据本发明的另一实施例,提供了一种移动应用单点登录方法,包括:
当终端首次进行移动应用单点登录时,伪单点登录服务器将收到的携带用户登录信息、第一应用的包名和用户标识的第一登录验证请求发送至应用服务器;
在所述应用服务器验证所述第一登录验证请求之后,所述伪单点登录服务器获取伪密码,并保存所述登录信息、第一应用的包名、用户标识和伪密码;
当终端再次进行移动应用单点登录时,所述伪单点登录服务器通过接收的来自终端的第二应用的包名和用户标识,将其保存的伪密码发送至终端,以供终端利用所述伪密码,进行第二应用的单点登录处理;
其中,所述第一应用和第二应用的用户登录信息相同,并通过所述用户标识相互关联。
所述用户登录信息包括用户账号和密码,在所述伪单点登录服务器将其保存的伪密码发送至终端之后,所述伪单点登录服务器接收携带用户账号、伪密码、第二应用的包名和用户标识的第二登录验证请求,并将所述第二登录验证请求中的伪密码替换为密码后,发送至相应的应用服务器进行验证。
根据本发明的另一实施例,提供了一种移动应用单点登录装置,包括:
客户端请求拦截器,设置为当首次进行移动应用单点登录时,经由伪单点登录服务器将携带用户登录信息、第一应用的包名、用户标识的第一登录验证请求发送至应用服务器,使
所述伪单点登录服务器在所述应用服务器验证所述第一登录验证请求之后,获取伪密码;
自动登录处理器,设置为当再次进行移动应用单点登录时,利用所述用户标识,从所述伪单点登录服务器获取所述伪密码,并利用所述用户登录信息和伪密码,进行第二应用的单点登录处理;
其中,所述第一应用和第二应用的用户登录信息相同,并通过所述用户标识相互关联。
所述客户端请求拦截器经由伪单点登录服务器将携带用户登录信息、第一应用的包名、用户标识的第一登录验证请求发送至应用服务器之前,拦截用来首次进行移动应用单点登录的携带用户登录信息的请求,并在所述请求中加入第一应用的包名、用户标识,形成第一登录验证请求。
所述用户登录信息包括用户账号和密码,所述客户端请求拦截器拦截用来再次进行移动应用单点登录的携带用户账号和伪密码的请求,在所述请求中加入第二应用的包名、用户标识,形成第二登录验证请求,并发送至伪单点登录服务器,以供伪单点登录服务器将所述第二登录验证请求中的伪密码替换为密码后发送至应用服务器进行登录验证。
根据本发明的另一实施例,提供了一种移动应用单点登录装置,包括:
收发模块,设置为当终端首次进行移动应用单点登录时,将收到的携带用户登录信息、第一应用的包名和用户标识的第一登录验证请求发送至应用服务器;
获取模块,设置为在所述应用服务器验证所述第一登录验证请求之后,获取伪密码,并保存所述用户登录信息、第一应用的包名、用户标识和伪密码;
处理模块,设置为当终端再次进行移动应用单点登录时,通过接收的来自终端的第二应用的包名和用户标识,将其保存的伪密码经由所述收发模块发送至终端,以供终端利用所述伪密码,进行第二应用的单点登录处理;
其中,所述第一应用和第二应用的用户登录信息均相同,并通过所述用户标识相互关联。
所述用户登录信息包括用户账号和密码,在将所述伪密码发送至终端之后,所述处理模块经由所述收发模块接收携带用户账号、伪密码、第二应用的包名和用户标识的第二登录验证请求,并将所述第二登录验证请求中的伪密码替换为密码后,经由所述收发模块发送至相应的应用服务器进行登录验证。
与相关技术相比较,本发明实施例的有益效果在于:
本发明实施例不需要改动应用的客户端和服务端源代码,就能实现“一次登录,多次使用”的功能,避免用户多次输入用户名和密码等用户登录信息的麻烦,也可以减少应用再次开发带来的成本和风险。
图1是本发明实施例提供的移动应用单点登录第一方法原理框图;
图2是本发明实施例提供的移动应用单点登录第一装置框图;
图3是本发明实施例提供的移动应用单点登录第二方法原理框图;
图4是本发明实施例提供的移动应用单点登录第二装置框图;
图5是本发明实施例提供的移动应用单点登录流程图;
图6是本发明实施例提供的加壳流程图。
以下结合附图对本发明的优选实施例进行详细说明,应当理解,以下所说明的优选实施例仅用于说明和解释本发明,并不用于限定本发明。
图1是本发明实施例提供的移动应用单点登录第一方法原理框图,如图1所示,步骤包括:
步骤S101:当首次进行移动应用单点登录时,终端经由伪单点登录服务器将携带用户登录信息(包括用户账号和密码)、第一应用的包名、用户标识的第一登录验证请求发送至应用服务器,使所述伪单点登录服务器在所述应用服务器验证所述第一登录验证请求之后,获取伪密码。
终端经由伪单点登录服务器将携带用户登录信息、第一应用的包名、用户标识的第一登录验证请求发送至应用服务器之前,终端拦截用来首次进行移动应用单点登录的携带用户登录信息的请求,并在所述请求中加入第一应用的包名、用户标识,形成第一登录验证请求。
步骤S102:当再次进行移动应用单点登录时,终端利用所述用户标识,从所述伪单点登录服务器获取所述伪密码,以自动登录第二应用。
步骤S103:终端利用所述用户登录信息和伪密码,进行第二应用的单点登录处理。
终端模拟用户输入用户账号和伪密码后,生成用来再次进行移动应用单点登录的携带用户账号和伪密码的请求,终端拦截所述请求,在所述请求中加入第二应用的包名、用户标识,形成第二登录验证请求,并发送至伪单点登录服务器,以供伪单点登录服务器将所述第二登录验证请求中的伪密码替换为密码后发送至应用服务器进行登录验证。
其中,所述第一应用和第二应用的用户登录信息相同,并通过所述用户标识相互关联。也就是说,一个用户标识可以与多个具有相同用户账号和密码的移动应用相关联,这样即便所述第二应用是首次登录,也可以实现自动登录,而无需用户再次手动输入用户账号和密码,实现同账号的多个移动应用的单点登录。
需要说明的是,上述步骤S101和步骤S102中的终端可以是同一终端,也可以是不同终
端,当两个终端不同时,实现跨终端的应用单点登录。
综上,本发明具体的使用场景是在不修改原系统源代码的情况下实现应用本身的单点登录功能、同账号的多个移动应用的单点登录、跨终端的应用单点登录。
图2是本发明实施例提供的移动应用单点登录第一装置框图,如图2所示,包括设置在移动终端侧的客户端请求拦截器11和自动登录处理器12。
客户端请求拦截器11设置为当首次进行移动应用单点登录时,经由伪单点登录服务器将携带用户登录信息(包括用户账号和密码)、第一应用的包名、用户标识的第一登录验证请求发送至应用服务器,使所述伪单点登录服务器在所述应用服务器验证所述第一登录验证请求之后,获取伪密码,并保存所述用户账号、密码、第一应用的包名、用户标识和伪用户。
进一步地,客户端请求拦截器11经由伪单点登录服务器将携带用户登录信息、第一应用的包名、用户标识的第一登录验证请求发送至应用服务器之前,拦截用来首次进行移动应用单点登录的携带用户登录信息的请求,并在所述请求中加入第一应用的包名、用户标识,形成第一登录验证请求。
自动登录处理器12设置为当再次进行移动应用单点登录时,利用所述用户标识,从所述伪单点登录服务器获取所述伪密码,并利用所述用户登录信息和伪密码,进行第二应用的单点登录处理。具体地说,自动登录处理器12自动模拟用户输入操作填写所获取的用户账号和伪密码,并发出用来再次进行移动应用单点登录的携带用户账号和伪密码的请求,此时客户端请求拦截器11拦截请求,在所述请求中加入第二应用的包名、用户标识,形成第二登录验证请求,并发送至伪单点登录服务器,以供伪单点登录服务器将所述第二登录验证请求中的伪密码替换为密码后发送至应用服务器进行登录验证。
上述第一应用和第二应用具有相同用户账号和密码,并与同一用户标识相关联,从而实现应用本身的单点登录功能、同账号的多个移动应用的单点登录、跨终端的应用单点登录。
图3是本发明实施例提供的移动应用单点登录第二方法原理框图,如图3所示,步骤包括:
步骤S201:当终端首次进行移动应用单点登录时,伪单点登录服务器将收到的携带用户登录信息(包括用户账号和密码)、第一应用的包名和用户标识的第一登录验证请求发送至应用服务器。
步骤S202:在所述应用服务器验证所述第一登录验证请求之后,所述伪单点登录服务器获取伪密码,并保存所述用户登录信息、第一应用的包名、用户标识和伪密码。
步骤S203:当终端再次进行移动应用单点登录时,所述伪单点登录服务器通过接收的第二应用的包名和用户标识,将其保存的伪密码发送至终端,以供终端利用所述伪密码,进行第二应用的单点登录处理。
其中,所述第一应用和第二应用的用户登录信息相同,并通过所述用户标识相互关联。
在所述伪单点登录服务器将其保存的伪密码发送至终端之后,所述伪单点登录服务器接收携带用户账号、伪密码、第二应用的包名和用户标识的第二登录验证请求,并将所述第二登录验证请求中的伪密码替换为密码后,发送至相应的应用服务器进行验证。在验证结束后,将校验结果通过伪单点登录服务器返回给终端。
图4是本发明实施例提供的移动应用单点登录第二装置框图,如图4所示,包括设置在伪单点登录服务器上的收发模块21、获取模块22、处理模块23。所述伪单点登录服务器设置在终端和应用服务器之间。
收发模块21设置为当终端首次进行移动应用单点登录时,将收到的携带用户登录信息(包括用户账号和密码)、第一应用的包名和用户标识的第一登录验证请求发送至应用服务器。具体地说,收发模块21携带用户账号、密码、用户标识、第一应用的包名的第一登录验证请求发送至应用服务器,由应用服务器对用户身份进行校验,并在校验结束后,将校验结果返回至终端。
获取模块22设置为在所述应用服务器验证所述第一登录验证请求之后,获取伪密码,并保存所述用户登录信息、第一应用的包名、用户标识和伪密码。其中,获取模块22可以在确认所述第一登录验证请求通过验证后自动生成伪密码,作为替代方案,也可以预先配置好伪密码。
处理模块23设置为当终端再次进行移动应用单点登录时,通过接收的来自终端的第二应用的包名和用户标识,将其保存的伪密码经由所述收发模块21发送至终端,以供终端利用所述伪密码,进行第二应用的单点登录处理。在将所述伪密码发送至终端之后,所述处理模块23经由所述收发模块接收携带用户账号、伪密码、第二应用的包名和用户标识的第二登录验证请求,并将所述第二登录验证请求中的伪密码替换为密码后,经由所述收发模块21发送至相应的应用服务器进行登录验证。
其中,所述第一应用和第二应用的用户登录信息账号和密码均相同,并通过所述用户标识相互关联。
图1至图4可以采用给应用加壳的方式实现,具体包括四个部分:加壳实现、移动设备管理(MDM)管理器、壳代码工程功能、伪SSO服务器部分。
一、加壳实现
需要伪单点登录功能的APK应用,采用加壳技术,将伪单点登录的壳代码融入到应用APK中,使得用户在使用加壳后的APK应用的时候,必须先经过伪单点登录的控制系统才能使用应用的后续功能。
加壳采用ApkTool工具首先反编译原始的APK,然后合并伪SSO壳代码及资源到反编译的原始APK中,包括处理AndroidManifest.xml文件、合并string.xml等资源文件,再使用ANT脚本工具将合并后的工程重新打包成APK。
二、MDM管理器
MDM管理器应用用于产生唯一的用户标识,设置为跨终端的单点登录实现,如果单终端的单点登录可以不使用MDM管理器,只需要使用设备唯一的移动设备国际身份码(International Mobile Equipment Identity,IMEI)或MAC地址作为唯一标识。
MDM管理器提供AIDL服务,当用户登录MDM管理器应用时产生唯一的用户标识,当打开关联的加壳后的应用时,从AIDL服务中取得此唯一的用户标识登录,携带此用户标识到伪SSO服务器;后续在另一个设备上用同一账户登录MDM管理器,再登录关联的加壳后的应用时,从MDM管理器的AIDL服务取到唯一的用户标识传到伪SSO服务器取到伪登录信息,实现自动登录。
三、壳代码工程功能
壳代码工程实现两部分功能,即客户端请求拦截器和自动登录处理器的功能。
1、客户端请求拦截器
要实现伪SSO功能,就必须能够拦截系统的登录请求,企业应用的请求一般是采用HTTP协议,因此可以在登录请求中添加设备信息(IMEI、MAC地址)、应用包名信息,然后携带这些信息引导到伪SSO服务器。
此处采用代理拦截技术来实现,代理拦截技术是基于代理服务器实现的。通过更改应用默认的代理选择器,来引导应用的登录请求首先转到自身的拦截器,添加额外的设备、用户标识和应用包名信息后,转发请求到伪SSO服务器。
2、自动登录处理器
自动登录处理器从伪SSO服务器取得已经登录过的用户名和伪密码,并且把所取到的用户名和伪密码自动的填充到对应登录界面的输入框中,然后自动进行登录。
四、伪SSO服务器
伪SSO服务器配置需要自动登录应用的信息,包括应用包名、登录url、请求消息格式、用户名和密码的标识字段、伪密码、响应消息格式、登录是否成功的标识以及哪些应用属于关联应用(使用相同的用户名和密码),以便能够正确解析登录请求,并转发请求到真正的应用认证服务器,当应用服务器告知认证成功后,保存登录用户名、密码、包名、标记等信息,为实现自动登录准备信息数据。
五、登录
安装加壳后的应用并启动,如果用户没有登录过应用,那么手动输入用户名和密码进行登录,如果已经登录过本应用或其它相关联的应用,壳代码工程的自动登录处理器的控制模块就会从伪SSO服务器获取用户名和伪密码,转到登录页面时,自动输入用户名、伪密码等信息,实现自动登录。
可见本发明实施例不是通过统一的ticket来验证用户的合法性,而是当用户第一次访问系统时,将用户的登录信息记录到统一的用户管理平台,当用户以后再次访问本系统或其它相关系统时从用户平台取得用户的登录信息,模拟用户输入用户登录信息,自动进行登录。
图5是本发明实施例提供的移动应用单点登录流程图,包括以下步骤:
步骤1.1:当用户第一次访问应用系统1的时候,因为还没有登录,用户通过登录界面进行登录;
步骤1.2:拦截登录请求,携带唯一标识(imei、mac或其它标识)、应用包名,引导用户登录请求到伪SSO服务器。
步骤1.3:伪SSO服务器引导登录请求到应用服务器的认证系统进行身份校验。
步骤1.4:应用服务器返回校验结果,例如通过校验。
步骤1.5:伪SSO服务器保存用户的登录信息。
步骤2.1:用户访问此应用或者别的相关应用,例如应用系统2。
步骤2.2:将应用唯一标识(imei、mac或其它标识)、应用包名带上,发送至伪SSO服务器,以获取用户账号和伪密码。
步骤2.3:伪SSO服务器根据唯一标识获取伪密码。
步骤2.4:将伪密码发送至终端,转到登录界面时,自动模拟用户填上取得的用户账号和伪密码,并自动登录。
步骤2.5:当引导登录请求到伪SSO服务器后,将伪密码替换为真正的密码;
步骤2.6:转发请求到应用服务器的认证系统进行校验,检查用户和真正的密码的合法性。
步骤2.7:应用服务器返回校验结果,例如通过效验,这样用户就可以在不用手动登录的情况下访问应用系统2和应用系统3了。
图6是本发明实施例提供的加壳流程图,如图6所示,包括以下步骤:
步骤S301:加壳开始。
步骤S302:APKTool反编译原始的APK文件。
步骤S303:拷贝伪SSO壳工程到目标目录。
步骤S304:合并伪SSO工程的AndroidManifest.xml和原始APK的AndroidManifest.xml,除了应用名称修改为伪SSO壳的应用名称之外,其它的应用信息修改为原始APK的信息,入口activity修改为伪SSO壳的activity。
步骤S305:合并伪SSO工程和解压后的原始APK资源文件
步骤S306:打包合并后的目录为加壳后APK。
步骤S307:加壳结束。
本发明实施例除了可以支持单应用的伪单点登录,也可以支持同账号多应用的伪单点登录和跨终端的伪单点登录。
同账号多应用的伪单点登录需要在伪SSO服务器测配置哪些应用属于同一个系统,只要其中的一个应用已经登录过,其它的应用再启动后就可以根据客户端端应用包名和唯一标识信息、伪SSO服务端配置信息,取到其它应用已经登录过得的登录账号和伪密码进行自动登录。
跨终端的伪单点登录使用MDM管理器应用实现,用户先登录此管理器产生唯一标记信息,当在一个设备上启动容器里面的某一个应用登录时,传递此标记信息、和应用包名到伪SSO服务器保存登录的用户名和密码,当在另一个设备上用同一个账号登录容器并启动应用时,根据客户端端应用报名、标记信息等、伪SSO服务端配置信息,取到应用的登录账号和伪密码进行自动登录。.
综上所述,本发明实施例具有以下技术效果:
1、移动互联网领域人员流动性很大,原来应用开发、设计等人员可能已经离职、系统众多,也没有更多时间维护改造系统,在这种没有人力情况下又需要实现自动登录功能,更改原来的系统新进员工又不是很熟悉的状况下,强行修改风险很大,又要投入人力熟悉原来的代码和流程,改造成本巨大,通过使用伪SSO可以很好的解决这方面问题。
2、采用本发明实施例的方案,首先使用简单,只需要提供终端应用安装包,就可以为应用添加伪SSO壳,无需修改第三方的源码,结合伪SSO服务器就可以实现单点登录功能,节省企业成本和降低应用二次开发带来的潜在风险。
3、用户使用加壳后的应用时,只需要手动登录一次,以后就可以自动登录。用户不再需要每次手动输入用户名称和用户密码,伪SSO改善了用户使用应用系统的体验。
通过以上的实施方式的描述,本领域的技术人员可以清楚地了解到根据上述实施例的方法可借助软件加必需的通用硬件平台的方式来实现,当然也可以通过硬件,但很多情况下前者是更佳的实施方式。基于这样的理解,本发明的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中,包括若干指令用以使得一台终端设备(可以是手机,计算机,服务器,或者网络设备等)执行本发明各个实施例所述的方法。
需要说明的是,上述各个模块是可以通过软件或硬件来实现的,对于后者,可以通过以下方式实现,但不限于此:上述模块均位于同一处理器中;或者,上述模块分别位于多个处理器中。
本发明的实施例还提供了一种存储介质。可选地,在本实施例中,上述存储介质可以包
括但不限于:U盘、只读存储器(ROM,Read-Only Memory)、随机存取存储器(RAM,Random Access Memory)、移动硬盘、磁碟或者光盘等各种可以存储程序代码的介质。
尽管上文对本发明进行了详细说明,但是本发明不限于此,本技术领域技术人员可以根据本发明的原理进行各种修改。因此,凡按照本发明原理所作的修改,都应当理解为落入本发明的保护范围。
如上所述,本发明实施例提供的一种移动应用单点登录方法及装置,具有以下有益效果:本发明实施例不需要改动应用的客户端和服务端源代码,就能实现“一次登录,多次使用”的功能,避免用户多次输入用户名和密码等用户登录信息的麻烦,也可以减少应用再次开发带来的成本和风险。
Claims (10)
- 一种移动应用单点登录方法,包括:当首次进行移动应用单点登录时,终端经由伪单点登录服务器将携带用户登录信息、第一应用的包名、用户标识的第一登录验证请求发送至应用服务器,使所述伪单点登录服务器在所述应用服务器验证所述第一登录验证请求之后,获取伪密码;当再次进行移动应用单点登录时,终端利用所述用户标识,从所述伪单点登录服务器获取所述伪密码,以登录第二应用;终端利用所述用户登录信息和伪密码,进行第二应用的单点登录处理;其中,所述第一应用和第二应用的用户登录信息相同,并通过所述用户标识相互关联。
- 根据权利要求1所述的方法,其中,终端经由伪单点登录服务器将携带用户登录信息、第一应用的包名、用户标识的第一登录验证请求发送至应用服务器之前,终端拦截用来首次进行移动应用单点登录的携带用户登录信息的请求,并在所述请求中加入第一应用的包名、用户标识,形成第一登录验证请求。
- 根据权利要求1所述的方法,其中,所述用户登录信息包括用户账号和密码,所述的终端利用所述用户登录信息和伪密码,进行第二应用的单点登录处理的步骤包括:终端拦截用来再次进行移动应用单点登录的携带用户账号和伪密码的请求;在所述请求中加入第二应用的包名、用户标识,形成第二登录验证请求,并发送至伪单点登录服务器,以供伪单点登录服务器将所述第二登录验证请求中的伪密码替换为密码后发送至应用服务器进行登录验证。
- 一种移动应用单点登录方法,包括:当终端首次进行移动应用单点登录时,伪单点登录服务器将收到的携带用户登录信息、第一应用的包名和用户标识的第一登录验证请求发送至应用服务器;在所述应用服务器验证所述第一登录验证请求之后,所述伪单点登录服务器获取伪密码,并保存所述登录信息、第一应用的包名、用户标识和伪密码;当终端再次进行移动应用单点登录时,所述伪单点登录服务器通过接收的来自终端的第二应用的包名和用户标识,将其保存的伪密码发送至终端,以供终端利用所述伪密码,进行第二应用的单点登录处理;其中,所述第一应用和第二应用的用户登录信息相同,并通过所述用户标识相互关联。
- 根据权利要求4所述的方法,其中,所述用户登录信息包括用户账号和密码,在所述伪单点登录服务器将其保存的伪密码发送至终端之后,所述伪单点登录服务器接收携带用户 账号、伪密码、第二应用的包名和用户标识的第二登录验证请求,并将所述第二登录验证请求中的伪密码替换为密码后,发送至相应的应用服务器进行验证。
- 一种移动应用单点登录装置,包括:客户端请求拦截器,设置为当首次进行移动应用单点登录时,经由伪单点登录服务器将携带用户登录信息、第一应用的包名、用户标识的第一登录验证请求发送至应用服务器,使所述伪单点登录服务器在所述应用服务器验证所述第一登录验证请求之后,获取伪密码;自动登录处理器,设置为当再次进行移动应用单点登录时,利用所述用户标识,从所述伪单点登录服务器获取所述伪密码,并利用所述用户登录信息和伪密码,进行第二应用的单点登录处理;其中,所述第一应用和第二应用的用户登录信息相同,并通过所述用户标识相互关联。
- 根据权利要求6所述的装置,其中,所述客户端请求拦截器经由伪单点登录服务器将携带用户登录信息、第一应用的包名、用户标识的第一登录验证请求发送至应用服务器之前,拦截用来首次进行移动应用单点登录的携带用户登录信息的请求,并在所述请求中加入第一应用的包名、用户标识,形成第一登录验证请求。
- 根据权利要求6所述的装置,其中,所述用户登录信息包括用户账号和密码,所述客户端请求拦截器拦截用来再次进行移动应用单点登录的携带用户账号和伪密码的请求,在所述请求中加入第二应用的包名、用户标识,形成第二登录验证请求,并发送至伪单点登录服务器,以供伪单点登录服务器将所述第二登录验证请求中的伪密码替换为密码后发送至应用服务器进行登录验证。
- 一种移动应用单点登录装置,包括:收发模块,设置为当终端首次进行移动应用单点登录时,将收到的携带用户登录信息、第一应用的包名和用户标识的第一登录验证请求发送至应用服务器;获取模块,设置为在所述应用服务器验证所述第一登录验证请求之后,获取伪密码,并保存所述用户登录信息、第一应用的包名、用户标识和伪密码;处理模块,设置为当终端再次进行移动应用单点登录时,通过接收的来自终端的第二应用的包名和用户标识,将其保存的伪密码经由所述收发模块发送至终端,以供终端利用所述伪密码,进行第二应用的单点登录处理;其中,所述第一应用和第二应用的用户登录信息均相同,并通过所述用户标识相互关联。
- 根据权利要求9所述的装置,其中,所述用户登录信息包括用户账号和密码,在将所述伪密码发送至终端之后,所述处理模块经由所述收发模块接收携带用户账号、伪密码、 第二应用的包名和用户标识的第二登录验证请求,并将所述第二登录验证请求中的伪密码替换为密码后,经由所述收发模块发送至相应的应用服务器进行登录验证。
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201510213974.2A CN106209726B (zh) | 2015-04-30 | 2015-04-30 | 一种移动应用单点登录方法及装置 |
CN201510213974.2 | 2015-04-30 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2016173199A1 true WO2016173199A1 (zh) | 2016-11-03 |
Family
ID=57198898
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2015/090563 WO2016173199A1 (zh) | 2015-04-30 | 2015-09-24 | 一种移动应用单点登录方法及装置 |
Country Status (2)
Country | Link |
---|---|
CN (1) | CN106209726B (zh) |
WO (1) | WO2016173199A1 (zh) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN111259355A (zh) * | 2020-02-12 | 2020-06-09 | 深信服科技股份有限公司 | 单点登录方法、门户系统、服务平台 |
CN111832000A (zh) * | 2020-07-17 | 2020-10-27 | 深信服科技股份有限公司 | 一种单点登录方法、系统、设备及计算机可读存储介质 |
CN112291188A (zh) * | 2019-09-23 | 2021-01-29 | 中建材信息技术股份有限公司 | 注册验证方法及系统、注册验证服务器、云服务器 |
CN114422229A (zh) * | 2022-01-14 | 2022-04-29 | 北京从云科技有限公司 | Web应用单点登录代理方法、装置、登录方法及服务器 |
Families Citing this family (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN106789987B (zh) * | 2016-12-08 | 2020-04-10 | 武汉斗鱼网络科技有限公司 | 移动终端单点登录多业务互联app的方法及系统 |
CN106850864B (zh) * | 2017-04-18 | 2020-03-03 | 北京京东尚科信息技术有限公司 | 应用于web服务器登录的方法和装置 |
CN108200060B (zh) * | 2018-01-03 | 2020-07-14 | 深圳壹账通智能科技有限公司 | 基于web子系统的单点登录验证方法、服务器及存储介质 |
CN108647501A (zh) * | 2018-05-09 | 2018-10-12 | 平安科技(深圳)有限公司 | 多应用程序共享密码解锁方法、装置、设备及存储介质 |
CN109639740B (zh) * | 2019-01-31 | 2022-02-22 | 平安科技(深圳)有限公司 | 一种基于设备id的登录态共享方法及装置 |
CN110278187B (zh) * | 2019-05-13 | 2021-11-16 | 网宿科技股份有限公司 | 多终端单点登录方法、系统、同步服务器及介质 |
CN111191202B (zh) * | 2019-12-31 | 2022-08-02 | 北京指掌易科技有限公司 | 移动应用的单点登录方法、装置及系统 |
CN111444495B (zh) * | 2020-05-20 | 2020-11-24 | 江苏易安联网络技术有限公司 | 一种基于容器实现单点登录的系统及方法 |
CN112532628A (zh) * | 2020-11-27 | 2021-03-19 | 广州三七互娱科技有限公司 | 跨应用登录管理方法、装置及系统 |
CN113067814B (zh) * | 2021-03-17 | 2023-02-28 | 成都飞鱼星科技股份有限公司 | 一种服务器与物联网终端的连接管控方法及装置 |
CN115242511B (zh) * | 2022-07-22 | 2024-04-12 | 成都中科大旗软件股份有限公司 | 一种多环境应用管理平台及管理方法 |
Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20140032902A1 (en) * | 2007-03-07 | 2014-01-30 | Adobe Systems Incorporated | Cryptographic binding of multiple secured connections |
EP2800330A1 (en) * | 2013-04-29 | 2014-11-05 | Wanin International Co., Ltd. | Secret key management method for multi-network platform |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102111410B (zh) * | 2011-01-13 | 2013-07-03 | 中国科学院软件研究所 | 一种基于代理的单点登录方法及系统 |
CN104065616B (zh) * | 2013-03-20 | 2017-06-20 | 中国移动通信集团公司 | 单点登录方法和系统 |
CN103179134A (zh) * | 2013-04-19 | 2013-06-26 | 中国建设银行股份有限公司 | 基于Cookie的单点登录方法、系统及其应用服务器 |
-
2015
- 2015-04-30 CN CN201510213974.2A patent/CN106209726B/zh active Active
- 2015-09-24 WO PCT/CN2015/090563 patent/WO2016173199A1/zh active Application Filing
Patent Citations (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20140032902A1 (en) * | 2007-03-07 | 2014-01-30 | Adobe Systems Incorporated | Cryptographic binding of multiple secured connections |
EP2800330A1 (en) * | 2013-04-29 | 2014-11-05 | Wanin International Co., Ltd. | Secret key management method for multi-network platform |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN112291188A (zh) * | 2019-09-23 | 2021-01-29 | 中建材信息技术股份有限公司 | 注册验证方法及系统、注册验证服务器、云服务器 |
CN112291188B (zh) * | 2019-09-23 | 2023-02-10 | 中建材信息技术股份有限公司 | 注册验证方法及系统、注册验证服务器、云服务器 |
CN111259355A (zh) * | 2020-02-12 | 2020-06-09 | 深信服科技股份有限公司 | 单点登录方法、门户系统、服务平台 |
CN111832000A (zh) * | 2020-07-17 | 2020-10-27 | 深信服科技股份有限公司 | 一种单点登录方法、系统、设备及计算机可读存储介质 |
CN111832000B (zh) * | 2020-07-17 | 2024-05-28 | 深信服科技股份有限公司 | 一种单点登录方法、系统、设备及计算机可读存储介质 |
CN114422229A (zh) * | 2022-01-14 | 2022-04-29 | 北京从云科技有限公司 | Web应用单点登录代理方法、装置、登录方法及服务器 |
Also Published As
Publication number | Publication date |
---|---|
CN106209726B (zh) | 2020-06-05 |
CN106209726A (zh) | 2016-12-07 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2016173199A1 (zh) | 一种移动应用单点登录方法及装置 | |
CN108475312B (zh) | 用于装置安全外壳的单点登录方法 | |
CN106936853B (zh) | 基于面向系统集成的跨域单点登录系统进行跨域单点登录的方法 | |
US20190199707A1 (en) | Using a service-provider password to simulate f-sso functionality | |
US8990911B2 (en) | System and method for single sign-on to resources across a network | |
US9401909B2 (en) | System for and method of providing single sign-on (SSO) capability in an application publishing environment | |
WO2016188256A1 (zh) | 一种应用接入鉴权的方法、系统、装置及终端 | |
CN111786969B (zh) | 单点登录方法、装置及系统 | |
CN104901970B (zh) | 一种二维码登录方法、服务器及系统 | |
CN105007280A (zh) | 一种应用登录方法和装置 | |
CN104125565A (zh) | 一种基于oma dm实现终端认证的方法、终端及服务器 | |
CN103139200A (zh) | 一种web service单点登录的方法 | |
CN111062023B (zh) | 多应用系统实现单点登录的方法及装置 | |
CN113922982B (zh) | 登录方法、电子设备及计算机可读存储介质 | |
CN112583834B (zh) | 一种通过网关单点登录的方法和装置 | |
CN112838951B (zh) | 一种终端设备的运维方法、装置、系统及存储介质 | |
CN105791249A (zh) | 一种第三方应用处理方法、装置以及系统 | |
CN105095729B (zh) | 一种二维码登录方法、服务器及系统 | |
CN112565236B (zh) | 信息鉴权方法、装置、计算机设备及存储介质 | |
CN109495458A (zh) | 一种数据传输的方法、系统及相关组件 | |
CN114338078B (zh) | 一种cs客户端登录方法及装置 | |
CN111193776B (zh) | 云桌面环境下客户端自动登录方法、装置、设备和介质 | |
CN112417403A (zh) | 一种基于GitLab API的系统自动化认证和授权处理方法 | |
CN115190483B (zh) | 一种访问网络的方法及装置 | |
CN115834252B (zh) | 一种服务访问方法及系统 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 15890574 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 15890574 Country of ref document: EP Kind code of ref document: A1 |