WO2014005501A1 - 用户账户保持登录态的方法、系统及存储介质 - Google Patents

用户账户保持登录态的方法、系统及存储介质 Download PDF

Info

Publication number
WO2014005501A1
WO2014005501A1 PCT/CN2013/078615 CN2013078615W WO2014005501A1 WO 2014005501 A1 WO2014005501 A1 WO 2014005501A1 CN 2013078615 W CN2013078615 W CN 2013078615W WO 2014005501 A1 WO2014005501 A1 WO 2014005501A1
Authority
WO
WIPO (PCT)
Prior art keywords
session
identifier
user
login
access request
Prior art date
Application number
PCT/CN2013/078615
Other languages
English (en)
French (fr)
Inventor
熊鹏飞
Original Assignee
腾讯科技（深圳）有限公司
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 腾讯科技（深圳）有限公司 filed Critical 腾讯科技（深圳）有限公司
Priority to RU2015103818A priority Critical patent/RU2658873C2/ru
Priority to KR1020157002966A priority patent/KR20150053897A/ko
Publication of WO2014005501A1 publication Critical patent/WO2014005501A1/zh
Priority to US14/589,504 priority patent/US20150121503A1/en

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31—User authentication
    • G06F21/41—User authentication where a single sign-on provides access to a plurality of computers
    • 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/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
    • G06F21/31—User authentication
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals

Definitions

  • the present invention relates to the field of Internet technologies, and in particular, to a method, system, and storage medium for maintaining a login state of a user account.
  • the development of Internet technology has changed the way of life of human beings.
  • the social activities of human beings have gradually evolved from traditional door-to-door visits and party parties to virtual social activities on the Internet.
  • Internet users can communicate and interact with others through virtual communities such as forums, Weibo, and online games.
  • the user account represents the virtual identity of the user in the virtual community.
  • a user can have multiple virtual identities in a single virtual community, ie multiple user accounts. Users can communicate or interact with others in different virtual identities by logging into the corresponding user account.
  • the method for keeping the user account in the login state in the conventional technology generally adopts a session mechanism, and can maintain the login state by assigning a session corresponding to the client to the data access request issued by the client.
  • the user switches the user account on the client (that is, changes the user ID of the currently operating client)
  • since the user account corresponding to the session cannot be switched correspondingly it is necessary to log out the currently logged-in user account, and then input another user account and password.
  • frequent login and logout requests will cause the login server to spend a lot of resources to process account password queries and session creation and logout tasks, thereby increasing resource overhead.
  • each time the user is switched, it is necessary to input the user account and password to log in again to maintain the login state, so that the convenience of the user operation is insufficient.
  • a method for a user account to remain logged in including:
  • the obtained session is assigned to the data access request.
  • a system in which a user account remains logged in including:
  • An access request obtaining module configured to obtain a data access request corresponding to the user identifier, where the data access request includes a session identifier corresponding to the user identifier;
  • a session obtaining module configured to extract a session identifier according to the data access request, and obtain a session corresponding to the session identifier
  • a session allocation module configured to allocate the acquired session to the data access request.
  • One or more storage media containing computer executable instructions for performing a method of maintaining a login state of a user account, the method comprising the steps of:
  • the obtained session is assigned to the data access request.
  • the obtained data access request includes a session identifier corresponding to the user identifier (user account selected by the user), and then obtains a session corresponding to the session identifier and allocates the session identifier.
  • the session allocated to the data access request is a session corresponding to the user identifier, and the session corresponding to the user identifier can be used repeatedly, so that the function of the multi-user account at the same time in the login state can be implemented in the same client, without using
  • the user identification is repeatedly verified, and a new session is created to be assigned to the data access request corresponding to the user identifier.
  • the number of times of verifying the user identifier is reduced, which reduces the pressure on the login server to perform account password verification.
  • no new session is created to process the data access request, which reduces the frequency of creating and clearing the session, thereby reducing resource overhead.
  • 1 is a flow chart of a method for a user account to remain logged in an embodiment
  • FIG. 2 is a flow chart of a user login method in an embodiment
  • FIG. 3 is a schematic structural diagram of a system in which a user account remains in a login state in one embodiment
  • FIG. 4 is a schematic structural diagram of a system in which a user account remains in a login state in another embodiment.
  • a method for a user account to remain logged in includes:
  • Step S102 Obtain a data access request corresponding to the user identifier, where the data access request includes a session identifier corresponding to the user identifier.
  • the user ID is the identifier of the user account and can be a string or a number.
  • the data access request is issued by the client, corresponding to the user identity in an active state.
  • the user ID in the active state is the user ID currently in the operational state of the client, and corresponds to the user account currently operating on the client.
  • the client may obtain the input user identifier setting operation, and set the user identifier corresponding to the user identifier setting operation to an active state.
  • the client can be a browser, and the browser can display multiple user identifiers in the form of a pull-down menu on the page.
  • the user identifier in the selected state in the drop-down menu is the user identifier in the active state.
  • the user can set the activation state of the user identification by selecting the drop-down menu.
  • the data access request sent by the user to other sites through the browser corresponds to the user ID in the active state on the page.
  • the session identifier may be cached in advance corresponding to the user ID.
  • the client may search for a session identifier corresponding to the user identifier in the cache, and generate a data access request according to the found session identifier.
  • the method for the user account to remain in the login state further includes:
  • Step S202 Acquire a user login request, where the user login request includes a user identifier.
  • Step S204 Extract the user identifier according to the user login request, perform identity verification on the user identifier, and create a session corresponding to the user identifier after the verification succeeds.
  • Step S206 Acquire a session identifier corresponding to the created session.
  • Step S208 the session identifier is cached corresponding to the user identifier.
  • the password may also be included in the user login request.
  • the step of authenticating the user may be specifically: authenticating the user by verifying the password.
  • the step of caching the session identifier with the user identifier may be specifically: buffering the session identifier and the user identifier into a cookie and/or a page file of the client.
  • the client may search for a session identifier corresponding to the user identifier in a local cookie and/or a page file, and generate a data access request according to the found session identifier.
  • the user ID and session ID can be stored in a cookie as a key-value pair.
  • the user identifier in the activated state may be obtained, and the corresponding session identifier is searched in the cookie according to the user identifier, and the session identifier is added to the head of the data access request.
  • the page file It can also be stored in the page file in the form of a hidden tag ( ⁇ hidden> ⁇ /hidden>) corresponding to the user ID.
  • the user identifier in the activated state may be obtained, and the corresponding session identifier is searched for in the hidden label of the page file according to the user identifier, and the session identifier is attached to the requested URL (Uniform) Resource
  • "http://www.aaa.com/index.html” is the original access URL
  • "123456789" is the session identifier.
  • Step S104 Extract a session identifier according to the data access request, and obtain a session corresponding to the session identifier.
  • the session ID corresponds to the session one-to-one.
  • the session exists in the form of an object and is stored in the memory of the server.
  • the mapping relationship between the session identifier and the session object may be preset. Further, the mapping relationship may be cached through the key value table.
  • the step of obtaining the session corresponding to the session identifier may be specifically: searching for a session corresponding to the session identifier according to the session identifier in the key value table.
  • the session object can also be serialized into a binary stream persistent storage.
  • the step of obtaining the session corresponding to the session identifier may be: acquiring a persistent binary stream corresponding to the session identifier, and deserializing the obtained binary stream into a session object.
  • session objects Due to the limited memory of the server and the large amount of user access, there are many session objects, which will occupy a large amount of memory space of the server. Serialize the in-memory session object into a binary stream and store the binary stream in a persistent manner.
  • the session object can be stored as a file on the hard disk, and the tape can be stored in the database as a binary stream, thereby reducing the session object.
  • Memory usage saves system resources.
  • Step S106 the acquired session is allocated to the data access request.
  • Assigning a session to a data access request is to allocate the operation space and time represented by the session to the data access request for data interaction.
  • the session can be encapsulated into a session object, and the received data access request can be encapsulated into an access request object.
  • the step of assigning the obtained session to the data access request may be specifically: assigning the session object as an attribute to the access request object.
  • the session is also provided with a lifecycle. You can periodically check if the life cycle of the session is overdue, and if so, log out of the session.
  • the method further includes: if the session corresponding to the session identifier is not obtained, prompting to log in.
  • the session corresponding to a user ID may be logged out due to overdue.
  • the session When the session is logged out, the corresponding session will not be obtained when searching according to the session ID.
  • the user may be prompted to log in by jumping to the prompt page, thereby re-creating the session corresponding to the user identifier.
  • the step of obtaining the session corresponding to the session identifier may be specifically: sending a session acquisition request to the trust server, the session acquisition request includes a session identifier, and acquiring a session corresponding to the session identifier returned by the trust server.
  • the manner in which the user logs in is a single sign-on manner, that is, the logged-in user can access all trusted servers without logging in again.
  • the created session corresponding to the session identifier may be queried on the trusted server that the user has logged in by sending a session acquisition request.
  • the trust server can serialize the obtained session into a binary stream.
  • the returned binary stream can be deserialized into a session object.
  • a system in which a user account remains in a login state includes an access request acquisition module 102, a session acquisition module 104, and a session assignment module 106, wherein:
  • the access request obtaining module 102 is configured to obtain a data access request corresponding to the user identifier, where the data access request includes a session identifier corresponding to the user identifier.
  • the user ID is the identifier of the user account and can be a string or a number.
  • the data access request obtained by the access request obtaining module 102 is sent by the client, corresponding to the user identifier in the active state.
  • the user ID in the active state is the user ID currently in the operational state of the client, and corresponds to the user account currently operating on the client.
  • the client may obtain the input user identifier setting operation, and set the user identifier corresponding to the user identifier setting operation to an active state.
  • the client can be a browser, and the browser can display multiple user identifiers in the form of a pull-down menu on the page.
  • the user identifier in the selected state in the drop-down menu is the user identifier in the active state.
  • the user can set the activation state of the user identification by selecting the drop-down menu.
  • the data access request sent by the user to other sites through the browser corresponds to the user ID in the active state on the page.
  • the session identifier may be cached in advance corresponding to the user ID.
  • the client may search for a session identifier corresponding to the user identifier in the cache, and generate a data access request according to the found session identifier.
  • the system for keeping the user account in the login state further includes:
  • the login request obtaining module 108 is configured to obtain a user login request, and the user login request includes a user identifier.
  • the authentication module 110 is configured to extract a user identifier according to the user login request, and perform identity verification on the user identifier.
  • the session creation module 112 is configured to create a session corresponding to the user identifier after the verification succeeds.
  • the cache write module 114 is configured to obtain a session identifier corresponding to the created session, and cache the session identifier and the user identifier.
  • the password may also be included in the user login request.
  • the authentication module 110 can be used to authenticate the user by verifying the password.
  • the authentication module 110 can also be used to pass LDAP (Lightweight Directory Access Protocol, the Lightweight Directory Access Protocol, authenticates users with user IDs.
  • LDAP Lightweight Directory Access Protocol
  • the cache write module 114 can also be used to cache the session identifier and the user identifier in a cookie and/or a page file of the client.
  • the client may search for a session identifier corresponding to the user identifier in a local cookie and/or a page file, and generate a data access request according to the found session identifier.
  • the cache write module 114 can be used to store the user identification and session identification in the form of a key-value pair in the cookie.
  • the client When the client generates a data access request, the user identifier in the activated state is obtained, and the corresponding session identifier is searched in the cookie according to the user identifier, and the session identifier is added to the head of the data access request.
  • the cache write module 114 can also be used to store the user ID in the form of a hidden tag ( ⁇ hidden> ⁇ /hidden>) in the page file.
  • the client may obtain the user identifier in an active state, search for a corresponding session identifier in the hidden tag of the page file according to the user identifier, and append the session identifier to the requested URL (Uniform) Resource The end of the Locator, Uniform Resource Locator.
  • the session obtaining module 104 is configured to extract a session identifier according to the data access request, and obtain a session corresponding to the session identifier.
  • the session ID corresponds to the session one-to-one.
  • the session exists in the form of an object and is stored in the memory of the server.
  • the mapping relationship between the session identifier and the session object may be preset. Further, the mapping relationship may be cached through the key value table.
  • the session obtaining module 104 can be configured to find a session corresponding to the session identifier according to the session identifier in the key value table.
  • the session object can also be serialized into a binary stream persistent storage.
  • the session obtaining module 104 is further configured to obtain a persistent stored binary stream corresponding to the session identifier, and deserialize the obtained binary stream into a session object.
  • session objects Due to the limited memory of the server and the large amount of user access, there are many session objects, which will occupy a large amount of memory space of the server. Serialize the in-memory session object into a binary stream and store the binary stream in a persistent manner.
  • the session object can be stored as a file on the hard disk, and the tape can be stored in the database as a binary stream, thereby reducing the session object.
  • Memory usage saves system resources.
  • the session assignment module 106 is configured to allocate the obtained session to the data access request.
  • Assigning a session to a data access request is to allocate the operation space and time represented by the session to the data access request for data interaction.
  • the session can be encapsulated into a session object, and the received data access request can be encapsulated into an access request object.
  • the session assignment module 106 can be used to assign a session object as an attribute to an access request object.
  • the session is also provided with a lifecycle.
  • the system for keeping the user account in the login state further includes a session detection module (not shown) for periodically detecting whether the life cycle of the session is overdue, and if so, canceling the session.
  • the system for keeping the user account in the login state further includes a login prompting module 116, configured to prompt login when the session corresponding to the session identifier is not acquired.
  • the session corresponding to a user ID may be logged out due to overdue.
  • the login prompting module 116 can be used to prompt the user to log in by jumping to the prompting page, thereby re-creating the session corresponding to the user identifier.
  • the session obtaining module 104 is further configured to send a session acquisition request to the trust server, where the session acquisition request includes a session identifier; and obtain a session corresponding to the session identifier returned by the trust server.
  • the manner in which the user logs in is a single sign-on manner, that is, the logged-in user can access all trusted servers without logging in again.
  • the session obtaining module 104 extracts the session identifier according to the received data access request, the session obtaining request may query the created session corresponding to the session identifier on the trusted server that the user has logged in by sending a session acquisition request.
  • the trust server can serialize the obtained session into a binary stream.
  • Session acquisition module 104 can deserialize the returned binary stream into a session object.
  • the present invention also provides one or more storage media containing computer executable instructions for performing a method of maintaining a login state of a user account.
  • One of ordinary skill in the art can understand that all or part of the process of implementing the foregoing embodiments can be completed by a computer program to instruct related hardware, and the program can be stored in a computer readable storage medium. When executed, the flow of an embodiment of the methods as described above may be included.
  • the storage medium may be a magnetic disk, an optical disk, or a read-only storage memory (Read-Only) Memory, ROM) or Random Access Memory (RAM).
  • the obtained data access request includes a session identifier corresponding to the user identifier (user account selected by the user), and then obtains a session corresponding to the session identifier and allocates the session identifier.
  • the session allocated to the data access request is a session corresponding to the user identifier, and the session corresponding to the user identifier can be used repeatedly, so that the function of the multi-user account at the same time in the login state can be implemented in the same client, without using
  • the user identification is repeatedly verified, and a new session is created to be assigned to the data access request corresponding to the user identifier.
  • the number of times of verifying the user identifier is reduced, which reduces the pressure on the login server to perform account password verification.
  • no new session is created to process the data access request, which reduces the frequency of creating and clearing the session, thereby reducing resource overhead.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)
  • Computer And Data Communications (AREA)

Abstract

本发明涉及一种用户账户保持登录态的方法，包括：获取与用户标识对应的数据访问请求，所述数据访问请求中包括与所述用户标识对应的会话标识；根据所述数据访问请求提取会话标识，获取与所述会话标识对应的会话；将所述获取到的会话分配给所述数据访问请求。此外，还提供了一种用户账户保持登录态的系统及存储介质。上述用户账户保持登录态的方法、系统及存储介质可以减少资源开销。

Description

用户账户保持登录态的方法、系统及存储介质
本申请要求于2012年7月6日提交中国专利局，申请号为201210233708.2，发明名称为“用户账户保持登录态的方法及系统”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
【技术领域】
本发明涉及互联网技术领域，特别是涉及一种用户账户保持登录态的方法、系统及存储介质。
【背景技术】
互联网技术的发展改变了人类的生活方式，人类的社交活动渐渐地由传统的登门拜访、聚会派对演变为互联网上虚拟社交活动。互联网用户可通过论坛、微博、网络游戏等虚拟社区与他人进行沟通和互动。用户账户则代表了该用户在虚拟社区中的虚拟身份。
通常情况下，一个用户可在一个虚拟社区中拥有多个虚拟身份，即多个用户账户。用户可通过登录相应的用户账户来以不同的虚拟身份与他人沟通或互动。
传统技术中的用户账户保持登录态的方法通常采用会话（session）机制，可通过将与客户端对应的会话分配给其发出的数据访问请求来保持登录态。然而，当用户在客户端切换用户账户（即更改当前操作客户端的用户标识）时，由于会话对应的用户账户无法相应切换，需要通过注销当前已登录的用户账户，然后再输入其他用户账户和密码重新登录，从而创建新的会话来保持登录态。当用户较多时，频繁的登录和注销请求会使得登录服务器需要花费大量资源处理账户密码查询以及会话的创建和注销任务，从而增加了资源开销。且每次切换用户后都需要输入用户账户和密码重新登录来保持登录态，使得用户操作的便利性不足。
【发明内容】
基于此，有必要提供一种能降低资源开销的用户账户保持登录态的方法。
一种用户账户保持登录态的方法，包括：
获取与用户标识对应的数据访问请求，所述数据访问请求中包括与所述用户标识对应的会话标识；
根据所述数据访问请求提取会话标识，获取与所述会话标识对应的会话；
将所述获取到的会话分配给所述数据访问请求。
此外，还有必要提供一种能降低资源开销的用户账户保持登录态的系统。
一种用户账户保持登录态的系统，包括：
访问请求获取模块，用于获取与用户标识对应的数据访问请求，所述数据访问请求中包括与所述用户标识对应的会话标识；
会话获取模块，用于根据所述数据访问请求提取会话标识，获取与所述会话标识对应的会话；
会话分配模块，用于将所述获取到的会话分配给所述数据访问请求。
此外，还有必要提供一种能降低资源开销的存储介质。
一个或多个包含计算机可执行指令的存储介质，所述计算机可执行指令用于执行一种用户账户保持登录态的方法，所述方法包括以下步骤：
获取与用户标识对应的数据访问请求，所述数据访问请求中包括与所述用户标识对应的会话标识；
根据所述数据访问请求提取会话标识，获取与所述会话标识对应的会话；
将所述获取到的会话分配给所述数据访问请求。
上述用户账户保持登录态的方法、系统及存储介质，获取到的数据访问请求中包含了与用户标识（用户选择的用户账户）对应的会话标识，然后根据获取与该会话标识对应的会话并分配给获取到的数据访问请求。也就是说，分配给数据访问请求的会话为与用户标识对应的会话，且与用户标识对应的会话可反复使用，使得可在同一客户端实现多用户账户同时处于登录态的功能，而不用在切换用户账户时，重复对该用户标识进行验证，并创建新的会话来分配给与该用户标识对应的数据访问请求。使得对用户标识进行验证的次数减少，减少了登录服务器进行账户密码验证的压力，同时，没有创建新的会话来处理数据访问请求，减少了创建会话和清除会话的频率，从而降低了资源开销。
而对于用户而言，在切换用户账户时，不用频繁的输入登录的账户和密码信息。使得用户操作更简洁，从而提高了用户操作的便利性。
【附图说明】
图1为一个实施例中用户账户保持登录态的方法的流程图；
图2为一个实施例中用户登录方法的流程图；
图3为一个实施例中用户账户保持登录态的系统的结构示意图；
图4为另一个实施例中用户账户保持登录态的系统的结构示意图。
【具体实施方式】
在一个实施例中，如图1所示，一种用户账户保持登录态的方法，包括：
步骤S102，获取与用户标识对应的数据访问请求，数据访问请求中包括与用户标识对应的会话标识。
用户标识即用户账户的标识，可以为字符串或数字。在一个实施例中，数据访问请求由客户端发出，与处于激活态的用户标识对应。处于激活态的用户标识即为当前对客户端处于操作态的用户标识，对应当前在客户端进行操作的用户账户。在本实施例中，客户端可获取输入的用户标识设置操作，并将与该用户标识设置操作对应的用户标识设置为激活态。
例如，客户端可以为浏览器，浏览器可在页面上以下拉菜单的形式展示多个用户标识，下拉菜单中处于选中状态的用户标识即为处于激活态的用户标识。用户可通过对下拉菜单进行选中操作来设置用户标识的激活态。用户通过浏览器发出的对其他站点的数据访问请求即与页面上处于激活态的用户标识对应。
在一个实施例中，可预先将会话标识与用户标识对应缓存。本实施例中，客户端可在缓存中查找与用户标识对应的会话标识，根据查找到的会话标识生成数据访问请求。
在本实施例中，如图2所示，用户账户保持登录态的方法还包括：
步骤S202，获取用户登录请求，用户登陆请求中包括用户标识。
步骤S204，根据用户登录请求提取用户标识，对用户标识进行身份验证，验证成功后创建与用户标识对应的会话。
步骤S206，获取与创建的会话对应的会话标识。
步骤S208，将会话标识与用户标识对应缓存。
在本实施例中，用户登录请求中还可包括密码。对用户进行身份验证的步骤可具体为：通过验证密码对用户进行身份验证。在另一个实施例中，还可通过LDAP（Lightweight Directory Access Protocol，轻量目录访问协议）通过用户标识对用户进行身份验证。
在本实施例中，将会话标识与用户标识对应缓存的步骤可具体为：将会话标识和用户标识对应缓存到客户端的cookie和/或页面文件中。
在本实施例中，客户端可在本地的cookie和/或页面文件中查找与用户标识对应的会话标识，根据查找到的会话标识生成数据访问请求。
例如，可在cookie中以键值对的形式存储用户标识和会话标识。在生成数据访问请求时，可获取处于激活态的用户标识，根据该用户标识在cookie中查找对应的会话标识，并将该会话标识添加到数据访问请求的头部。
也可在页面文件中以隐藏标签（<hidden></hidden>）的形式与用户标识对应存储。在生成数据访问请求时，可获取处于激活态的用户标识，根据该用户标识在页面文件的隐藏标签中查找对应的会话标识，并将该会话标识附加在请求的URL（Uniform Resource Locator，统一资源定位符）的末尾。例如，生成的数据访问请求的URL可以为“http：//www.aaa.com/index.html?sid=123456789”。其中，“http：//www.aaa.com/index.html”为原始访问URL，“123456789”为会话标识。
步骤S104，根据数据访问请求提取会话标识，获取与会话标识对应的会话。
会话标识与会话一一对应。在一个实施例中，会话以对象的形式存在，存储于服务器的内存中。可预设会话标识和会话对象的映射关系，进一步的，可通过键值表缓存该映射关系。获取与会话标识对应的会话的步骤可具体为：在键值表中根据会话标识查找与会话标识对应的会话。
进一步的，还可将会话对象序列化成二进制流持久化存储。获取与会话标识对应的会话的步骤可具体为：获取与会话标识对应的持久化存储的二进制流，将获取到的二进制流反序列化成会话对象。
由于服务器的内存有限，用户访问量较大时，会话对象较多，会占用服务器的大量内存空间。将内存中的会话对象序列化成二进制流，并将该二进制流持久化存储，可将会话对象以文件的形式存储到硬盘，磁带或以二进制流的形式存储在数据库中，从而减少了会话对象的内存占用率，节省了系统资源。
步骤S106，将获取到的会话分配给数据访问请求。
将会话分配给数据访问请求即为将会话所表示的操作空间和时间分配给数据访问请求，用于数据交互。
在一个实施例中，可将会话封装成会话对象，可将接收到的数据访问请求封装成访问请求对象。将获取到的会话分配给数据访问请求的步骤可具体为：将会话对象作为属性赋值给访问请求对象。
在一个实施例中，会话还设置有生命周期。可定期检测会话的生命周期是否超期，若是，则注销该会话。
在本实施例中，获取与会话标识对应的会话的步骤之后还包括：若未获取到与会话标识对应的会话，则提示登录。
某个用户标识对应的会话由于超期，可能被注销。当会话被注销后，根据会话标识查找时则会获取不到对应的会话。在本实施例中，可通过跳转到提示页面来提示用户进行登录，从而重新创建与用户标识对应的会话。
在一个实施例中，获取与会话标识对应的会话的步骤可具体为：向信任服务器发送会话获取请求，会话获取请求包括会话标识；获取信任服务器返回的与会话标识对应的会话。
在本实施例中，用户登录的方式为单点登录的方式，即，登录用户可以访问所有信任服务器而不用再次登录。在根据接收到数据访问请求提取到会话标识后，可通过发送会话获取请求在该用户已登录的信任服务器上查询与会话标识对应的已创建的会话。信任服务器可将获取到的会话序列化成二进制流返回。可将返回的二进制流反序列化成会话对象。
在一个实施例中，如图3所示，一种用户账户保持登录态的系统，包括访问请求获取模块102、会话获取模块104、会话分配模块106，其中：
访问请求获取模块102，用于获取与用户标识对应的数据访问请求，数据访问请求中包括与用户标识对应的会话标识。
用户标识即用户账户的标识，可以为字符串或数字。在一个实施例中，访问请求获取模块102获取到的数据访问请求由客户端发出，与处于激活态的用户标识对应。处于激活态的用户标识即为当前对客户端处于操作态的用户标识，对应当前在客户端进行操作的用户账户。在本实施例中，客户端可获取输入的用户标识设置操作，并将与该用户标识设置操作对应的用户标识设置为激活态。
例如，客户端可以为浏览器，浏览器可在页面上以下拉菜单的形式展示多个用户标识，下拉菜单中处于选中状态的用户标识即为处于激活态的用户标识。用户可通过对下拉菜单进行选中操作来设置用户标识的激活态。用户通过浏览器发出的对其他站点的数据访问请求即与页面上处于激活态的用户标识对应。
在一个实施例中，可预先将会话标识与用户标识对应缓存。本实施例中，客户端可在缓存中查找与用户标识对应的会话标识，根据查找到的会话标识生成数据访问请求。
在本实施例中，如图4所示，用户账户保持登录态的系统还包括：
登陆请求获取模块108，用于获取用户登录请求，用户登陆请求中包括用户标识。
身份验证模块110，用于根据用户登录请求提取用户标识，对用户标识进行身份验证。
会话创建模块112，用于验证成功后创建与用户标识对应的会话。
缓存写入模块114，用于获取与创建的会话对应的会话标识，将会话标识与用户标识对应缓存。
在本实施例中，用户登录请求中还可包括密码。身份验证模块110可用于通过验证密码对用户进行身份验证。在另一个实施例中，身份验证模块110还可用于通过LDAP（Lightweight Directory Access Protocol，轻量目录访问协议）通过用户标识对用户进行身份验证。
在本实施例中，缓存写入模块114还可用于将会话标识和用户标识对应缓存到客户端的cookie和/或页面文件中。
在本实施例中，客户端可在本地的cookie和/或页面文件中查找与用户标识对应的会话标识，根据查找到的会话标识生成数据访问请求。
例如，缓存写入模块114可用于在cookie中以键值对的形式存储用户标识和会话标识。客户端生成数据访问请求时，可获取处于激活态的用户标识，根据该用户标识在cookie中查找对应的会话标识，并将该会话标识添加到数据访问请求的头部。
缓存写入模块114也可用于在页面文件中以隐藏标签（<hidden></hidden>）的形式与用户标识对应存储。客户端在生成数据访问请求时，可获取处于激活态的用户标识，根据该用户标识在页面文件的隐藏标签中查找对应的会话标识，并将该会话标识附加在请求的URL（Uniform Resource Locator，统一资源定位符）的末尾。例如，生成的数据访问请求的URL可以为：“http：//www.aaa.com/index.html?sid=123456789”
其中，“http：//www.aaa.com/index.html”为原始访问URL，“123456789”为会话标识。
会话获取模块104，用于根据数据访问请求提取会话标识，获取与会话标识对应的会话。
会话标识与会话一一对应。在一个实施例中，会话以对象的形式存在，存储于服务器的内存中。可预设会话标识和会话对象的映射关系，进一步的，可通过键值表缓存该映射关系。会话获取模块104可用于在键值表中根据会话标识查找与会话标识对应的会话。
进一步的，还可将会话对象序列化成二进制流持久化存储。会话获取模块104还可用于获取与会话标识对应的持久化存储的二进制流，将获取到的二进制流反序列化成会话对象。
由于服务器的内存有限，用户访问量较大时，会话对象较多，会占用服务器的大量内存空间。将内存中的会话对象序列化成二进制流，并将该二进制流持久化存储，可将会话对象以文件的形式存储到硬盘，磁带或以二进制流的形式存储在数据库中，从而减少了会话对象的内存占用率，节省了系统资源。
会话分配模块106，用于将获取到的会话分配给数据访问请求。
将会话分配给数据访问请求即为将会话所表示的操作空间和时间分配给数据访问请求，用于数据交互。
在一个实施例中，可将会话封装成会话对象，可将接收到的数据访问请求封装成访问请求对象。会话分配模块106可用于将会话对象作为属性赋值给访问请求对象。
在一个实施例中，会话还设置有生命周期。用户账户保持登录态的系统还包括会话检测模块（图中未标示），用于定期检测会话的生命周期是否超期，若是，则注销该会话。
在本实施例中，如图4所示，用户账户保持登录态的系统还包括登录提示模块116，用于在未获取到与会话标识对应的会话时提示登录。
某个用户标识对应的会话由于超期，可能被注销。当会话被注销后，根据会话标识查找时则会获取不到对应的会话。在本实施例中，登录提示模块116可用于通过跳转到提示页面来提示用户进行登录，从而重新创建与用户标识对应的会话。
在一个实施例中，会话获取模块104还用于向信任服务器发送会话获取请求，会话获取请求包括会话标识；获取信任服务器返回的与会话标识对应的会话。
在本实施例中，用户登录的方式为单点登录的方式，即，登录用户可以访问所有信任服务器而不用再次登录。会话获取模块104在根据接收到数据访问请求提取到会话标识后，可通过发送会话获取请求在该用户已登录的信任服务器上查询与会话标识对应的已创建的会话。信任服务器可将获取到的会话序列化成二进制流返回。会话获取模块104可将返回的二进制流反序列化成会话对象。
此外，本发明还提供了一个或多个包含计算机可执行指令的存储介质，所述计算机可执行指令用于执行一种用户账户保持登录态的方法。本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机程序来指令相关的硬件来完成，所述的程序可存储于一计算机可读取存储介质中，该程序在执行时，可包括如上述各方法的实施例的流程。其中，所述的存储介质可为磁碟、光盘、只读存储记忆体（Read-Only Memory，ROM）或随机存储记忆体（Random Access Memory，RAM）等。
上述用户账户保持登录态的方法、系统及存储介质，获取到的数据访问请求中包含了与用户标识（用户选择的用户账户）对应的会话标识，然后根据获取与该会话标识对应的会话并分配给获取到的数据访问请求。也就是说，分配给数据访问请求的会话为与用户标识对应的会话，且与用户标识对应的会话可反复使用，使得可在同一客户端实现多用户账户同时处于登录态的功能，而不用在切换用户账户时，重复对该用户标识进行验证，并创建新的会话来分配给与该用户标识对应的数据访问请求。使得对用户标识进行验证的次数减少，减少了登录服务器进行账户密码验证的压力，同时，没有创建新的会话来处理数据访问请求，减少了创建会话和清除会话的频率，从而降低了资源开销。
而对于用户而言，在切换用户账户时，不用频繁的输入登录的账户和密码信息。使得用户操作更简洁，从而提高了用户操作的便利性。
以上所述实施例仅表达了本发明的几种实施方式，其描述较为具体和详细，但并不能因此而理解为对本发明专利范围的限制。应当指出的是，对于本领域的普通技术人员来说，在不脱离本发明构思的前提下，还可以做出若干变形和改进，这些都属于本发明的保护范围。因此，本发明专利的保护范围应以所附权利要求为准。

Claims (24)

  1. 一种用户账户保持登录态的方法，包括：
    获取与用户标识对应的数据访问请求，所述数据访问请求中包括与所述用户标识对应的会话标识；
    根据所述数据访问请求提取会话标识，获取与所述会话标识对应的会话；
    将所述获取到的会话分配给所述数据访问请求。
  2. 根据权利要求1所述的用户账户保持登录态的方法，其特征在于，所述方法还包括：
    获取用户登录请求，所述用户登陆请求中包括用户标识；
    根据所述用户登录请求提取用户标识，对所述用户标识进行身份验证，验证成功后创建与所述用户标识对应的会话；
    获取与所述创建的会话对应的会话标识；
    将所述会话标识与所述用户标识对应缓存。
  3. 根据权利要求2所述的用户账户保持登录态的方法，其特征在于，所述将所述会话标识与所述用户标识对应缓存的步骤为：
    将所述会话标识与所述用户标识对应缓存到客户端的cookie和/或页面文件中。
  4. 根据权利要求2所述的用户账户保持登录态的方法，其特征在于，所述将所述会话标识与所述用户标识对应缓存的步骤为：
    在页面文件中以隐藏标签的形式将所述会话标识与用户标识对应存储。
  5. 根据权利要求1至4任一项所述的用户账户保持登录态的方法，其特征在于，所述获取与所述会话标识对应的会话的步骤为：
    向信任服务器发送会话获取请求，所述会话获取请求包括所述会话标识；
    获取所述信任服务器返回的与所述会话标识对应的会话。
  6. 根据权利要求1至4任一项所述的用户账户保持登录态的方法，其特征在于，所述获取与所述会话标识对应的会话的步骤之后还包括：
    若未获取到与所述会话标识对应的会话，则提示登录。
  7. 根据权利要求1至4任一项所述的用户账户保持登录态的方法，其特征在于，所述方法还包括：
    将所述会话对象序列化成二进制流持久化存储；
    所述获取与会话标识对应的会话的步骤为：
    获取与所述会话标识对应的持久化存储的二进制流，将获取到的二进制流反序列化成会话对象。
  8. 根据权利要求1至4任一项所述的用户账户保持登录态的方法，其特征在于，所述方法还包括：
    定期检测会话的生命周期是否超期，若是，则注销该会话。
  9. 一种用户账户保持登录态的系统，其特征在于，包括：
    访问请求获取模块，用于获取与用户标识对应的数据访问请求，所述数据访问请求中包括与所述用户标识对应的会话标识；
    会话获取模块，用于根据所述数据访问请求提取会话标识，获取与所述会话标识对应的会话；
    会话分配模块，用于将所述获取到的会话分配给所述数据访问请求。
  10. 根据权利要求9所述的用户账户保持登录态的系统，其特征在于，还包括登陆请求获取模块，用于获取用户登录请求，所述用户登陆请求中包括用户标识；
    身份验证模块，用于根据所述用户登录请求提取用户标识，对所述用户标识进行身份验证；
    会话创建模块，用于验证成功后创建与所述用户标识对应的会话；
    缓存写入模块，用于获取与所述创建的会话对应的会话标识，将所述会话标识与所述用户标识对应缓存。
  11. 根据权利要求10所述的用户账户保持登录态的系统，其特征在于，所述缓存写入模块还用于将所述会话标识与所述用户标识缓存到客户端的cookie和/或页面文件中。
  12. 根据权利要求10所述的用户账户保持登录态的系统，其特征在于，所述缓存写入模块还用于在页面文件中以隐藏标签的形式将所述会话标识与用户标识对应存储。
  13. 根据权利要求9至12任一项所述的用户账户保持登录态的系统，其特征在于，所述会话获取模块还用于向信任服务器发送会话获取请求，所述会话获取请求包括所述会话标识；获取所述信任服务器返回的与所述会话标识对应的会话。
  14. 根据权利要求9至12任一项所述的用户账户保持登录态的系统，其特征在于，还包括登录提示模块，用于在未获取到与会话标识对应的会话时提示登录。
  15. 根据权利要求9至12任一项所述的用户账户保持登录态的系统，其特征在于，所述会话对象对应持久化存储的序列化后的二进制流；
    所述会话获取模块还用于获取与所述会话标识对应的持久化存储的二进制流，将获取到的二进制流反序列化成会话对象。
  16. 根据权利要求9至12任一项所述的用户账户保持登录态的系统，其特征在于，所述系统还包括会话检测模块，用于定期检测会话的生命周期是否超期，若是，则注销该会话。
  17. 一个或多个包含计算机可执行指令的存储介质，所述计算机可执行指令用于执行一种用户账户保持登录态的方法，其特征在于，所述方法包括以下步骤：
    获取与用户标识对应的数据访问请求，所述数据访问请求中包括与所述用户标识对应的会话标识；
    根据所述数据访问请求提取会话标识，获取与所述会话标识对应的会话；
    将所述获取到的会话分配给所述数据访问请求。
  18. 根据权利要求17所述的存储介质，其特征在于，所述方法还包括：
    获取用户登录请求，所述用户登陆请求中包括用户标识；
    根据所述用户登录请求提取用户标识，对所述用户标识进行身份验证，验证成功后创建与所述用户标识对应的会话；
    获取与所述创建的会话对应的会话标识；
    将所述会话标识与所述用户标识对应缓存。
  19. 根据权利要求18所述的存储介质，其特征在于，所述将所述会话标识与所述用户标识对应缓存的步骤为：
    将所述会话标识与所述用户标识对应缓存到客户端的cookie和/或页面文件中。
  20. 根据权利要求18所述的存储介质，其特征在于，所述将所述会话标识与所述用户标识对应缓存的步骤为：
    在页面文件中以隐藏标签的形式将所述会话标识与用户标识对应存储。
  21. 根据权利要求17至20任一项所述的存储介质，其特征在于，所述获取与所述会话标识对应的会话的步骤为：
    向信任服务器发送会话获取请求，所述会话获取请求包括所述会话标识；
    获取所述信任服务器返回的与所述会话标识对应的会话。
  22. 根据权利要求17至20任一项所述的存储介质，其特征在于，所述获取与所述会话标识对应的会话的步骤之后还包括：
    若未获取到与所述会话标识对应的会话，则提示登录。
  23. 根据权利要求17至20任一项所述的存储介质，其特征在于，所述方法还包括：
    将所述会话对象序列化成二进制流持久化存储；
    所述获取与会话标识对应的会话的步骤为：
    获取与所述会话标识对应的持久化存储的二进制流，将获取到的二进制流反序列化成会话对象。
  24. 根据权利要求17至20任一项所述的存储介质，其特征在于，所述方法还包括：
    定期检测会话的生命周期是否超期，若是，则注销该会话。
PCT/CN2013/078615 2012-07-06 2013-07-01 用户账户保持登录态的方法、系统及存储介质 WO2014005501A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
RU2015103818A RU2658873C2 (ru) 2012-07-06 2013-07-01 Способ, система и информационный носитель для сохранения состояния входа в пользовательскую учетную запись
KR1020157002966A KR20150053897A (ko) 2012-07-06 2013-07-01 사용자 계정이 로그인 상태를 유지하기 위한 방법, 시스템, 및 저장 매체
US14/589,504 US20150121503A1 (en) 2012-07-06 2015-01-05 Method, system and storage medium for user account to maintain login state

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201210233708.2A CN103532919B (zh) 2012-07-06 2012-07-06 用户账户保持登录态的方法及系统
CN201210233708.2 2012-07-06

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US14/589,504 Continuation US20150121503A1 (en) 2012-07-06 2015-01-05 Method, system and storage medium for user account to maintain login state

Publications (1)

Publication Number Publication Date
WO2014005501A1 true WO2014005501A1 (zh) 2014-01-09

Family

ID=49881333

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/078615 WO2014005501A1 (zh) 2012-07-06 2013-07-01 用户账户保持登录态的方法、系统及存储介质

Country Status (5)

Country Link
US (1) US20150121503A1 (zh)
KR (1) KR20150053897A (zh)
CN (1) CN103532919B (zh)
RU (1) RU2658873C2 (zh)
WO (1) WO2014005501A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104506555A (zh) * 2015-01-06 2015-04-08 北京艾力泰尔信息技术有限公司 客户端零存储的单点登录方法

Families Citing this family (44)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103841188B (zh) * 2014-02-27 2018-10-23 北京奇虎科技有限公司 一种浏览器中Cookie信息的处理方法和装置
CN104239776B (zh) * 2014-09-23 2018-04-20 浪潮(北京)电子信息产业有限公司 多控存储系统单点登录方法及多控存储系统
US9680938B1 (en) * 2014-10-06 2017-06-13 Exabeam, Inc. System, method, and computer program product for tracking user activity during a logon session
US9798883B1 (en) 2014-10-06 2017-10-24 Exabeam, Inc. System, method, and computer program product for detecting and assessing security risks in a network
CN105681258B (zh) * 2014-11-19 2019-09-17 腾讯科技（武汉）有限公司 基于第三方服务器的会话方法和会话装置
US10250594B2 (en) 2015-03-27 2019-04-02 Oracle International Corporation Declarative techniques for transaction-specific authentication
CN105141605B (zh) * 2015-08-19 2019-04-19 金蝶软件（中国）有限公司 会话方法、网站服务器及浏览器
CN105138649B (zh) * 2015-08-26 2018-11-30 小米科技有限责任公司 数据的搜索方法、装置及终端
CN106533685B (zh) * 2015-09-09 2020-12-08 腾讯科技（深圳）有限公司 身份认证方法、装置及系统
US10164971B2 (en) 2015-10-22 2018-12-25 Oracle International Corporation End user initiated access server authenticity check
US10257205B2 (en) * 2015-10-22 2019-04-09 Oracle International Corporation Techniques for authentication level step-down
US10225283B2 (en) 2015-10-22 2019-03-05 Oracle International Corporation Protection against end user account locking denial of service (DOS)
JP6895431B2 (ja) 2015-10-23 2021-06-30 オラクル・インターナショナル・コーポレイション アクセス管理のためのパスワードレス認証
US20170140134A1 (en) * 2015-11-16 2017-05-18 Welch Allyn, Inc. Medical device user caching
US10496815B1 (en) 2015-12-18 2019-12-03 Exabeam, Inc. System, method, and computer program for classifying monitored assets based on user labels and for detecting potential misuse of monitored assets based on the classifications
US11140167B1 (en) 2016-03-01 2021-10-05 Exabeam, Inc. System, method, and computer program for automatically classifying user accounts in a computer network using keys from an identity management system
US10178108B1 (en) 2016-05-31 2019-01-08 Exabeam, Inc. System, method, and computer program for automatically classifying user accounts in a computer network based on account behavior
CN106899564B (zh) * 2016-07-01 2020-05-19 阿里巴巴集团控股有限公司 一种登录方法和装置
US10395027B2 (en) * 2016-12-09 2019-08-27 Vmware, Inc. Co-existence of management applications and multiple user device management
US10887325B1 (en) 2017-02-13 2021-01-05 Exabeam, Inc. Behavior analytics system for determining the cybersecurity risk associated with first-time, user-to-entity access alerts
US10645109B1 (en) 2017-03-31 2020-05-05 Exabeam, Inc. System, method, and computer program for detection of anomalous user network activity based on multiple data sources
US10841338B1 (en) 2017-04-05 2020-11-17 Exabeam, Inc. Dynamic rule risk score determination in a cybersecurity monitoring system
CN106973062A (zh) * 2017-04-27 2017-07-21 努比亚技术有限公司 一种会话管理方法以及服务器
CN107707522A (zh) * 2017-08-14 2018-02-16 北京奇安信科技有限公司 一种基于云代理的权限控制方法及装置
CN107682397B (zh) * 2017-08-28 2019-02-26 平安科技（深圳）有限公司 客户资源获取方法、装置、终端设备及存储介质
CN107485858A (zh) * 2017-08-28 2017-12-19 昆明理工大学 一种网络游戏防沉迷验证方法
US11423143B1 (en) 2017-12-21 2022-08-23 Exabeam, Inc. Anomaly detection based on processes executed within a network
US11334287B2 (en) * 2018-02-09 2022-05-17 Micron Technology, Inc. Data stream identification and processing in data storage device
US11431741B1 (en) 2018-05-16 2022-08-30 Exabeam, Inc. Detecting unmanaged and unauthorized assets in an information technology network with a recurrent neural network that identifies anomalously-named assets
CN108683679B (zh) * 2018-05-30 2022-08-02 深圳壹账通智能科技有限公司 Web APP的多账号登录方法、装置、设备及存储介质
US11178168B1 (en) 2018-12-20 2021-11-16 Exabeam, Inc. Self-learning cybersecurity threat detection system, method, and computer program for multi-domain data
CN110213356B (zh) * 2019-05-21 2021-11-12 深圳壹账通智能科技有限公司 一种基于数据处理的登录处理方法及相关设备
US11625366B1 (en) 2019-06-04 2023-04-11 Exabeam, Inc. System, method, and computer program for automatic parser creation
CN112291182B (zh) * 2019-07-23 2022-06-21 腾讯科技（深圳）有限公司 保持用户账户登录态的方法、装置、电子设备及存储介质
CN112839016B (zh) * 2019-11-25 2023-03-21 上海哔哩哔哩科技有限公司 会话控制方法及装置
CN111241504B (zh) * 2020-01-16 2024-01-05 远景智能国际私人投资有限公司 身份验证方法、装置、电子设备及存储介质
US11956253B1 (en) 2020-06-15 2024-04-09 Exabeam, Inc. Ranking cybersecurity alerts from multiple sources using machine learning
CN113824675B (zh) * 2020-09-17 2023-08-08 京东科技控股股份有限公司 管理登录态的方法和装置
CN112261134B (zh) * 2020-10-21 2023-06-30 阳光保险集团股份有限公司 网络数据访问审计方法、装置、设备及存储介质
US11196728B1 (en) * 2021-03-29 2021-12-07 Fmr Llc Caching login sessions to access a software testing environment
CN113221083B (zh) * 2021-06-02 2023-05-16 湖北央中巨石信息技术有限公司 一种能够提升服务器性能的区块链用户会话缓存方法
CN113596116B (zh) * 2021-07-13 2024-02-06 成都安恒信息技术有限公司 一种运维审计系统ssh会话恢复的方法
CN114679302B (zh) * 2022-03-01 2024-05-10 中信百信银行股份有限公司 对接单点登陆类系统的方法、装置、设备及存储介质
CN114760139A (zh) * 2022-04-21 2022-07-15 北京金堤科技有限公司 登录态同步方法、装置、电子设备及计算机存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101163113A (zh) * 2006-10-12 2008-04-16 阿里巴巴公司 一种即时通信的断线重连系统及方法
CN101193089A (zh) * 2006-11-20 2008-06-04 阿里巴巴公司 有状态会话系统及其实现方法
WO2009134051A1 (en) * 2008-05-02 2009-11-05 Samsung Electronics Co., Ltd. System and method for transferring a session between multiple clients
CN101754112A (zh) * 2008-12-05 2010-06-23 中兴通讯股份有限公司 移动电子邮件业务处理方法和装置

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP3807961B2 (ja) * 2001-08-01 2006-08-09 インターナショナル・ビジネス・マシーンズ・コーポレーション セッション管理方法、セッション管理システムおよびプログラム
US6993596B2 (en) * 2001-12-19 2006-01-31 International Business Machines Corporation System and method for user enrollment in an e-community
US7401235B2 (en) * 2002-05-10 2008-07-15 Microsoft Corporation Persistent authorization context based on external authentication
US7363539B1 (en) * 2004-04-30 2008-04-22 Sap Ag Restoring communication sessions and components with state information
US7552219B2 (en) * 2004-09-30 2009-06-23 International Business Machines Corporation Methods for sharing session data on a network
US7668904B2 (en) * 2005-07-28 2010-02-23 International Business Machines Corporation Session replication
CN101635707A (zh) * 2008-07-25 2010-01-27 国际商业机器公司 在Web环境中为用户提供身份管理的方法和装置
US8051465B1 (en) * 2008-09-26 2011-11-01 Amazon Technologies, Inc. Mitigating forgery of electronic submissions
WO2012144909A1 (en) * 2011-04-19 2012-10-26 Invenia As Method for secure storing of a data file via a computer communication network

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101163113A (zh) * 2006-10-12 2008-04-16 阿里巴巴公司 一种即时通信的断线重连系统及方法
CN101193089A (zh) * 2006-11-20 2008-06-04 阿里巴巴公司 有状态会话系统及其实现方法
WO2009134051A1 (en) * 2008-05-02 2009-11-05 Samsung Electronics Co., Ltd. System and method for transferring a session between multiple clients
CN101754112A (zh) * 2008-12-05 2010-06-23 中兴通讯股份有限公司 移动电子邮件业务处理方法和装置

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104506555A (zh) * 2015-01-06 2015-04-08 北京艾力泰尔信息技术有限公司 客户端零存储的单点登录方法

Also Published As

Publication number Publication date
CN103532919A (zh) 2014-01-22
US20150121503A1 (en) 2015-04-30
RU2015103818A (ru) 2016-08-27
KR20150053897A (ko) 2015-05-19
RU2658873C2 (ru) 2018-06-25
CN103532919B (zh) 2018-06-12

Similar Documents

Publication Publication Date Title
WO2014005501A1 (zh) 用户账户保持登录态的方法、系统及存储介质
US9063971B2 (en) Schema and query abstraction for different LDAP service providers
US11616690B2 (en) Discovery of virtualization environments
Turcotte et al. Unified host and network data set
US7822980B2 (en) Authenticated identity propagation and translation within a multiple computing unit environment
US10187275B2 (en) Monitoring network traffic by using event log information
US6240512B1 (en) Single sign-on (SSO) mechanism having master key synchronization
US8667575B2 (en) Systems and methods for AAA-traffic management information sharing across cores in a multi-core system
JP5587732B2 (ja) ドメイン・ネーム・サービス（ｄｎｓ）データベースへのアクセスを管理するコンピュータ実施方法、コンピュータ・プログラム、およびシステム
KR101720160B1 (ko) 인간의 개입이 없는 어플리케이션들을 위한 인증 데이터베이스 커넥티비티
WO2018161478A1 (zh) 多区块链的分片处理方法、装置、服务器和存储介质
US20030177388A1 (en) Authenticated identity translation within a multiple computing unit environment
CN103905572B (zh) 域名解析请求的处理方法及装置
US9697379B2 (en) Database virtualization
WO2016169410A1 (zh) 登录方法、服务器和登录系统
US20120311167A1 (en) Non-intrusive single sign-on mechanism in cloud services
JP2010524082A (ja) 仮想マシンのためのネットワークグループ名
CN1487437A (zh) 提供全程会话持续性的设备和方法
WO2014089872A1 (zh) 支持域名组dns解析的方法和系统
JP2005535032A (ja) 柔軟なトップレベルドメインのための、ローカルネームサーバを持つ内部自然ドメインサービスシステム
CN111695108B (zh) 一种异构计算环境中多源账号的用户统一账号标识系统
US20210092134A1 (en) Threat intelligence information access via a DNS protocol
US8296853B2 (en) Method and system for authenticating a user
CN110213398B (zh) 别名管理方法、装置、服务器及存储介质
JP5495188B2 (ja) Ｗｅｂサービス提供システム、サーバ装置、方法およびプログラム

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: 13812489

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20157002966

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2015103818

Country of ref document: RU

Kind code of ref document: A

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 11/06/2015)

122 Ep: pct application non-entry in european phase

Ref document number: 13812489

Country of ref document: EP

Kind code of ref document: A1