Title of Invention: Method and apparatus for providing authentication session sharing Abstract: An approach is provided for providing authentication session sharing between browsers and run time environments in network communication. An interface receives an authentication context associated with a first service. The interface causes, at least in part, storage of the authentication context in a first cache associated with the interface. The interface causes, at least in part, population of the authentication context to a second cache associated with a second service. The second cache is not directly linked to the interface. The authentication context in the second cache authenticates access to the second service. Detailed Description: Part general_description_paragraphs: Part CROSS-REFERENCE TO RELATED APPLICATION: This application is a continuation-in-part of U.S. application Ser. No. 12/707,941, filed Feb. 18, 2010, titled METHOD AND APPARATUS FOR PROVIDING AUTHENTICATION SESSION SHARING, the entire disclosure of which is hereby incorporated by reference herein in its entirety. Part BACKGROUND: Network service providers and device manufacturers are continually challenged to deliver value, convenience, and security to consumers by, for example, providing compelling network services. It is noted that the number and variety of applications provided on user devices is continually growing. For example, modern user devices can include several applications (e.g., browsers, client applications, etc.) that enable a user to access network services provided by different application servers. Convenience and security of access to these servers are important challenges that service providers face every day. Accordingly, in one embodiment, authentication servers can be used to provide security for such applications to access application servers. Traditionally, authentication information between browser applications and different client applications is not shared, therefore, network resources can be wasted and user experience can be diminished when an authentication process is repeated for different applications accessed from the same device. Part SOME EXAMPLE EMBODIMENTS: Therefore, there is a need for an approach for providing authentication session sharing between different applications (such as, but not limited to, browsers and run time environments). According to one embodiment, a method comprises receiving, at an interface, an authentication context associated with a first service. The method also comprises causing, at least in part, storage of the authentication context in a first cache associated with the interface. The method further comprises causing, at least in part, population of the authentication context to a second cache. The second cache is associated with a second service and the second cache is not directly linked to the interface. The authentication context in the second cache authenticates access to the second service. According to another embodiment, an apparatus comprising at least one processor, and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause, at least in part, the apparatus to receive an authentication context associated with a first service. The apparatus is also caused to cause, at least in part, storage of the authentication context in a first cache associated with the apparatus. The apparatus is further caused to cause, at least in part, population of the authentication context to a second cache. The second cache is associated with a second service and the second cache is not directly linked to the apparatus. The authentication context in the second cache authenticates access to the second service. According to another embodiment, a computer-readable storage medium carrying one or more sequences of one or more instructions which, when executed by one or more processors, cause, at least in part, an apparatus to receive an authentication context associated with a first service. The apparatus is also caused to cause, at least in part, storage of the authentication context in a first cache associated with the apparatus. The apparatus is further caused to cause, at least in part, population of the authentication context to a second cache. The second cache is associated with a second service and the second cache is not directly linked to the apparatus. The authentication context in the second cache authenticates access to the second service. According to another embodiment, an apparatus comprises means for an authentication context associated with a first service. The apparatus also comprises means for causing, at least in part, storage of the authentication context in a first cache associated with the apparatus. The apparatus further comprises means for causing, at least in part, population of the authentication context to a second cache. The second cache is associated with a second service and the second cache is not directly linked to the apparatus. The authentication context in the second cache authenticates access to the second service. Still other aspects, features, and advantages of the invention are readily apparent from the following detailed description, simply by illustrating a number of particular embodiments and implementations, including the best mode contemplated for carrying out the invention. The invention is also capable of other and different embodiments, and its several details can be modified in various obvious respects, all without departing from the spirit and scope of the invention. Accordingly, the drawings and description are to be regarded as illustrative in nature, and not as restrictive. Part DESCRIPTION OF SOME EMBODIMENTS: Examples of a method, apparatus, and computer program for providing authentication session sharing between browsers and run time environments are disclosed. In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the invention. It is apparent, however, to one skilled in the art that the embodiments of the invention may be practiced without these specific details or with an equivalent arrangement. In other instances, well-known structures and devices are shown in block diagram form in order to avoid unnecessarily obscuring the embodiments of the invention. As used herein, the term network resource refers to any service or data structure or communication link available through connection to a network. A single sign-on (SSO) process refers to any process of a single provider, which enables a user, during one session connected to the network, to access a plurality of network resources from that provider without redundant entry by the user of user identification or authentication information. A single provider is often identified by a single network domain name in the uniform resource identification (URI) naming system, as used for example with a uniform resource locator (URL) naming system. However, it also contemplated that the SSO process can extend to services provided over multiple network domains. An example single sign-on process is the single sign-on processes for the OVI™ system of the NOKIA CORPORATION™ of Espoo, Finland. An access provider is a network service provider that grants access for user equipment (e.g., UE 101, described below) to access a network (e.g., communication network 105, described below). FIG. 1 is a diagram of a system capable of providing authentication session sharing, according to one embodiment. Applications (such as, but not limited to, applications executing in run-time environments (e.g., Java runtime, Web runtime, etc.), browsers, etc.) can be executed on user devices to enable access to services provided by application servers. As previously noted, the number and variety of these client applications are continually increasing; and security and convenience of access to the application servers through the client applications are important challenges facing service providers. Traditionally, for each client application (e.g., a browser or client application) to access an application server, the client application (and/or a user of the client application) needs to authenticate itself to an authentication server to receive an authentication context. The authentication context is further used by the client application to access the server application. However, this authentication context is not traditionally shared between different types of client applications. Therefore, each client application type performs its own authentication process to access the application servers, for instance, even when accessing the same servers or when the application servers provide related services. This can waste network resources by causing potentially high traffic loads on participating application servers and authentication servers, thereby diminishing user experience. For example, an authentication context historically is not shared between an application that runs in a run time environment and a client application such as browser. Therefore, even if a run time client application has been authenticated and an authentication context exists, when a user uses a browser to access the same or related application server (such as a web server), the user and/or the browser performs another authentication process to obtain an authentication context specific to the browser. This repeated authentication can result in potentially high traffic loads on participating authentication server. To address these problems, a system 100 of FIG. 1 can advantageously provide a platform to share authentication session information, such as authentication context, between different applications such as client applications running in run time environments and client applications such as browsers. As used herein, the term “authentication context” can include: (1) information regarding initial identification mechanisms of a user, client, customer, etc.; (2) information regarding authentication mechanism or method (e.g., passwords, one time password, a cookie, a limited use key, a secret key, a consumer key, an access token, etc.); (3) information regarding storage and protection of credential (e.g., password rules, smart carts, etc.); and the like. According to an embodiment of FIG. 1, a user equipment (UE) 101 can communicate with multiple network resources, including application servers 103a-130n (collectively referenced hereinafter as application servers 103), through, for example, communication network 105. In one example, authentication server 107 can be used to identify, authentication, and/or verify the UE 101, a user of the UE 101, client applications, browsers, etc., associated with the UE 101, for access to application servers 103. The UE 101 can include an interface, such as device enabler (DE) 109, which can provide a platform to share authentication session information, such as authentication context, between, for example, client applications 111a-111m (collectively referenced hereinafter as client applications 111) and the browser 113. According to an embodiment, when one of the client applications 111 is authenticated with the authentication server 107 through the DE 109, an authentication context can be received, for example, at the DE 109 and the authentication context can then be cached and/or stored at, for example, a cache and/or an authentication database 117 associated with the DE 109. The DE 109 can advantageously cause population of the authentication context from, for example, the cache and/or authentication database 117 associated with the DE 109 to another cache and/or database, such as database 115, which is not directly linked to the DE 109. According to one embodiment, this method can be a push method wherein the authentication context from the authentication database 117 is transmitted or caused to be transmitted to the database 115 without a specific request from the database 115 or application associated with the database 115 (e.g., the browser 113). In this example, the browser 113 can use the populated authentication context from the cache and/or database 115 to access the application servers 103 without the need for further authentication. According to certain embodiments, one of the client applications 111, for example, client application 111a, desires to access the application servers 103. An interface, such as the DE module 109, which may be implemented as a chip set as shown in FIG. 7 and described below, with or without one or more computer program instructions, can receive an authentication request from the client application 111a. The authentication request can be used to authenticate the client application 111a, a user of the client application 111a, or a combination thereof. In one example, the DE 109 determines whether the client application 111a, a user of the client application 111a, or a combination thereof, has already been authenticated to access the requested application server 103 in a current session over the communication network 105. If the DE 109 determines that an authentication is necessary (e.g., if the user has not yet been authenticated), a user interface (UI) is generated and a user of the client application 111a is prompted for inputs employed to identify and authenticate the user. In one embodiment, the determination that an authentication is necessary can be based on lack of an authentication context for the client application 111a and/or a user of the client application 111a, an outdated authentication context, etc. In one example, the DE 109 can initiate the UI to prompt the user for user authentication and/or identification inputs. Alternatively or additionally, the authentication server 107 can initiate the UI. User input, which can include, but are not limited to, user credentials is received by the interface DE 109. The user credentials can include username, password, biometrics, one time password, network address filtering, etc. However, it is contemplated that other authentication and/or identification schemes can be used. The DE 109 generates an authentication request for the client application 111a and/or a user of the client application 111a and conveys the authentication request to the authentication server 107. The authentication server 107 determines if the client application 111a and/or a user of the client application 111a can be authenticated based, at least in part, on the user inputs, such as user credentials. If the authentication fails, the authentication server 107 informs the DE 109 of the failed authentication and the DE 109 returns the result of the authentication to the client application 111a. However, if the authentication is successful (e.g., the user credentials are valid), the authentication server 107 generates and returns a valid authentication context to the DE 109. In one example, the success of the authentication is determined by the authentication server 107 by comparing the received user credentials with user credentials stored in a database (not shown) associated with the authentication server 107. However, it is contemplated that other authentication schemes and protocols can be used to authenticate the client applications 111 and/or user(s) of the client applications. When the DE 109 receives the valid authentication context, in case of a successful authentication, the DE 109 informs the client application 111a that the authentication has been successful. Further, the DE 109 can cache and/or store the received authentication context in a cache and/or database, such as authentication database 117 that is associated with the DE 109. Therefore, if other client applications that are associated with the DE 109 (such as client applications 111) request authentication from the DE 109, the existence and validity of the stored authentication context can be checked by the DE 109 and authentication response can be sent to the requesting client application without further contacting the authentication server 107. Further, the DE 109 can advantageously cause population of the authentication context cached and/or stored in authentication database 117 in another cache and/or database, which is not directly linked with and/or utilizes the DE 109 (such as database 115). In one example, this population of the authentication context provides the platform for sharing authentication session information between applications that utilize the DE 109 and applications that do not use the DE 109 (such as browser 113). Therefore, if the browser 113 desires to access the application server 103, the browser 113 can utilize the populated authentication context in, for example, the database 115 to authenticate itself (and/or its user) to the application servers 103. By way of example, the database 115 can be a cookie store accessible by the browser 113. In this way, the browser 113 need not perform an additional authentication because the authentication context would already be available in the cookie store (e.g., database 115). Moreover, the browser 113 (or other similar client application) need not be aware of the transfer or population of the authentication context from the DE 109. Instead, the browser 113 need only check for the presence of the authentication context in the cookie store or cache where it normally stores such authentication contexts. In one example, populating the authentication context between the databases 115 and 117 can include copying the authentication context from the authentication database 117 to the database 115. Additionally or alternatively, populating the authentication context can include converting the authentication context received for the client application 111a to another authentication context based, at least in part, on an authentication protocol associated with, for example, the browser 113 and caching and/or storing the converted authentication context in the cache and/or database 115. In one example, the authentication context received for the client application 111a can include a token and populating the authentication context in cache and/or database 115 can include converting the authentication context to an encrypted cookie associated to the browser 113. A cookie (e.g., a browser cookie or Hypertext Transport Protocol (HTTP) cookie) is generally a small piece of text stored on a user device by, for instance, a web browser or other application. A cookie consists of one or more name-value pairs containing limited bits of information such as user preferences, shopping cart contents, an identifier for a server-based session, or other data used by websites and the application servers 103. In one embodiment, the client applications 111 can include applications that run on run time environments, such as Java Runtime, Web Runtime (WRT), etc. Also, although various embodiments are explained with respect to browser 113 as a client application that is not directly linked to the DE 109, it is contemplated that other client applications that do not directly utilize the DE 109 can be used (e.g., other native client applications). Also, by way of example, the authentication server 107 can include a single sign-on (SSO) authentication server. Single sign-on is an authentication process that enables a user (e.g., a user device, a client application, user of a user device, etc.) to authenticate once and gain access to resources of multiple software, applications, servers, etc., without being prompted to authenticate itself again at each of the resources. Therefore, when a client application (such as one of client applications 111 and/or browser 113) and/or a user of the client application is authenticated with the authentication server 107, for example, as discussed above, to access one of the application servers 103, the client application (and/or the user) can access other application servers (which are supported by the single sign-on scheme) during one session connected to the network, without redundant entry by, for example, the user of the user identification or authentication information. According to this example, the interface DE 109 can be implemented as an SSO authentication enabler to advantageously share authentication session information between different client applications (e.g., client applications 111 and/or browser 113) of the UE 101. As discussed above, when the interface DE 109 receives an authentication request from one of client applications 111, such as client application 111b, the DE 109 determines whether an authentication process has already been performed for the client applications 111. For example, the DE 109 determines whether the authentication context already exists, has not expired, or is otherwise valid for authentication other client applications 111. If the DE 109 determines that the authentication process has already been performed, the DE 109 informs the client application 111b of the outcome of the authentication process. For example, the DE 109 generates and initiates transmission of a message to the client application 111b to inform the client application 111b of a successful or failed authentication attempt. If the DE 109 determines that the authentication context exists (and for example, is not outdated), the authentication context is retrieved from, for example, the cache and/or authentication database 117 and is returned to the client application 111b. Therefore, the interface DE 109 implements single sign-in functionality by caching and/or storing the authentication context and retrieving it for requesting client applications. The client application 111b can use the retrieved authentication context to connect to, for example, the application server 103a. In one example, the connection request from the client application 111b to the application server 103a can include the retrieved authentication context. The application server 103a can utilize the authentication server 107 to verify the authentication context and allow access by the client application 111b if the authentication context is verified. In one embodiment, the verification of the authentication context can include a verification message (that for example includes the authentication context) from the application server 103a to the authentication server 107, verification of the authentication context at the authentication server 107 (for example, by comparing the received authentication context with the stored authentication contexts), and a verification message from the authentication server 107 to the application server 103a indicating the result of the verification. In one embodiment, after a client application 111 has been authenticated (e.g., received a valid authentication context), the received authentication context can be cached in, for instance, the database 117 which has a direct link to the DE 109. The DE 109 can then populate the authentication context to the database 115 that is directly accessible by the browser 113. This population of the authentication context from the database 117 to the database 115 advantageously enables the DE 109 share an authentication context (e.g., an SSO authentication context) with another application such as the browser 113 that would otherwise have no direct link to the authentication context via the DE 109. In this way, the system 100 also advantageously reduces the use of computing resources, network resources (e.g., bandwidth), power resources, etc. of the UE 101 and/or the communication network 105 by enabling sharing of an authentication context among different client applications 111 for accessing previously authenticated servers (e.g., the application servers 103). For example, the browser 113 may desire to access one or more of the application servers 103 (e.g., application server 103a). In this example, the browser 113 generates and initiates transmission of an access request to the application server 103a. Since the client applications 111 have been authenticated, an authentication context has been received and cached and/or stored, and a populated authentication context exists for the browser 113 in, for example, cache and/or database 115, the access request can include the populated authentication context. Therefore, the authentication session information can be shared between different client applications and no further entry of, for example, user credentials for further authentication is necessary. As mentioned, the populated authentication context can be a copy of the authentication context, a converted version of the authentication context, etc. By way of example, the application server 103a that receives the access request, can also generate and initiate transmission of a verification request to verify the received populated authentication context. The verification request is sent to the authentication server 107. The authentication server 107 verifies the validity of the authentication context, for example, by comparison with stored authentication contexts. The authentication server 107 generates and initiates transmission of a verification response based, at least in part, on the verification of the populated authentication context. If the authentication context is valid, the access request is granted. According to certain embodiments, DE 109 can also determine whether an authentication context is stored or otherwise available in a cache and/or database (such as database 115) associated with the browser 113. If the authentication is available in the database 115, the DE 109 can retrieve the authentication context to populate the authentication context in the cache and/or database (such as authentication database 117) associated with the client applications 111. In one embodiment, this process can be called the pull method for populating the authentication context to the database 117. In another example, the browser 113 may desire to access one or more of the application servers 103 (for example application server 103a). If the browser 113, a user of the browser 113, UE 101, a user of UE 101, or a combination thereof has not already been authenticated to access the application server 103a (e.g., no valid authentication context is stored in the database 115 associated with the browser 113), the browser 113 can be directed to the authentication server 107 for authentication. In one embodiment, the browser 113 receives a request for user credentials, for example, from the authentication server 107 and, in response, sends the user credentials to the authentication server 107. In this example, the authentication server 107 can determine the validity of user credentials by, for example, a comparison of the presented credentials against stored credentials. It is contemplated that any other authentication mechanism can be implemented to ensure that only authorized users are able to access the application servers 103. If the browser 113, a user of the browser 113, UE 101, a user of UE 101, or a combination thereof is authenticated, the authentication server 107 can generate and transmit an authentication context to the browser 113. The browser 113 can then store the received authentication context in the database 115 of the browser 113. Further access requests to application servers 103 by the browser 113 can be authenticated using the cached authentication context. In certain embodiments, DE 109 can also populate the authentication context stored in the database 115 that is directly accessible by the browser 113 to a cache and/or database (e.g., database 117) that is associated with the client applications 111. In one embodiment, DE 109 can determine that an authentication context associated to the browser 113 is available and can populate the authentication context to the authentication database 117 to be used by client applications 111. More specifically, the authentication of the browser 113, a user of the browser 113, UE 101, a user of UE 101, or a combination thereof can be through the DE 109, therefore, the DE 109 can determine existence of the authentication context for the browser 113. This population of the authentication context from the database 115 to the database 117 advantageously enables the DE 109 share an authentication context (e.g., an SSO authentication context) with other applications such as the client applications 111 that would otherwise have no direct link to the database 115. As discussed, in one example, populating the authentication context between the databases 115 and 117 can include copying the authentication context from the authentication database 115 to the database 117. Additionally or alternatively, populating the authentication context can include converting the authentication context received for the browser 113 to another authentication context based, at least in part, on an authentication protocol associated with, for example, the client applications 111 and caching and/or storing the converted authentication context in the authentication cache and/or database 117. In one embodiment, the authentication context that was generated for the browser 113 can be a cookie-based authentication context (for example, but not limited to, an encrypted cookie). In one example, populating the authentication context from database 115 to authentication database 117 can include converting the cookie-based authentication context to a token-based authentication context. As discussed previously, implementing a platform to share authentication context between, for example, client applications 111 and the browser 113 can advantageously reduce communication load on the authentication server 107 by reducing number of authentication requests generated by the client applications 111 and the browser 113 that is destined for the authentication server 107. By way of example, the communication network 105 of system 100 includes one or more networks such as a data network (not shown), a wireless network (not shown), a telephony network (not shown), or any combination thereof. It is contemplated that the data network may be any local area network (LAN), metropolitan area network (MAN), wide area network (WAN), a public data network (e.g., the Internet), short range wireless network, or any other suitable packet-switched network, such as a commercially owned, proprietary packet-switched network, e.g., a proprietary cable or fiber-optic network, and the like, or any combination thereof. In addition, the wireless network may be, for example, a cellular network and may employ various technologies including enhanced data rates for global evolution (EDGE), general packet radio service (GPRS), global system for mobile communications (GSM), Internet protocol multimedia subsystem (IMS), universal mobile telecommunications system (UMTS), etc., as well as any other suitable wireless medium, e.g., worldwide interoperability for microwave access (WiMAX), Long Term Evolution (LTE) networks, code division multiple access (CDMA), wideband code division multiple access (WCDMA), wireless fidelity (WiFi), wireless LAN (WLAN), Bluetooth®, Internet Protocol (IP) data casting, satellite, mobile ad-hoc network (MANET), and the like, or any combination thereof. The UE 101 is any type of mobile terminal, fixed terminal, or portable terminal including a mobile handset, station, unit, device, multimedia computer, multimedia tablet, Internet node, communicator, desktop computer, laptop computer, Personal Digital Assistants (PDAs), audio/video player, digital camera/camcorder, positioning device, television receiver, radio broadcast receiver, electronic book device, game device, or any combination thereof. It is also contemplated that the UE 101 can support any type of interface to the user (such as “wearable” circuitry, etc.). By way of example, the UE 101, the application servers 103a-103n, and the authentication server 107, communicate with each other and other components of the communication network 105 using well known, new or still developing protocols. In this context, a protocol includes a set of rules defining how the network nodes within the communication network 105 interact with each other based on information sent over the communication links. The protocols are effective at different layers of operation within each node, from generating and receiving physical signals of various types, to selecting a link for transferring those signals, to the format of information indicated by those signals, to identifying which software application executing on a computer system sends or receives the information. The conceptually different layers of protocols for exchanging information over a network are described in the Open Systems Interconnection (OSI) Reference Model. Communications between the network nodes are typically effected by exchanging discrete packets of data. Each packet typically comprises (1) header information associated with a particular protocol, and (2) payload information that follows the header information and contains information that may be processed independently of that particular protocol. In some protocols, the packet includes (3) trailer information following the payload and indicating the end of the payload information. The header includes information such as the source of the packet, its destination, the length of the payload, and other properties used by the protocol. Often, the data in the payload for the particular protocol includes a header and payload for a different protocol associated with a different, higher layer of the OSI Reference Model. The header for a particular protocol typically indicates a type for the next protocol contained in its payload. The higher layer protocol is said to be encapsulated in the lower layer protocol. The headers included in a packet traversing multiple heterogeneous networks, such as the Internet, typically include a physical (layer 1) header, a data-link (layer 2) header, an internetwork (layer 3) header and a transport (layer 4) header, and various application headers (layer 5, layer 6 and layer 7) as defined by the OSI Reference Model. It is noted that although FIG. 1 illustrates the application servers 103 and the authentication server 107 as separate entities, it is contemplated that any combination of these servers can be implemented such that the functions of these components may be combined in one or more components or performed by other components of equivalent functionality. Also, it is contemplated that the client applications 111, browser 113, and DE 109 can be distributed on different devices and/or equipment and the authentication context can be shared using a communication network. In one embodiment, the client applications 111 and the browser 113 interact with the application servers 103 according to a client-server model. It is noted that the client-server model of computer process interaction is widely known and used. According to the client-server model, a client process sends a message including a request to a server process, and the server process responds by providing a service. The server process may also return a message with a response to the client process. Often the client process and server process execute on different computer devices, called hosts, and communicate via a network using one or more protocols for network communications. The term “server” is conventionally used to refer to the process that provides the service, or the host computer on which the process operates. Similarly, the term “client” is conventionally used to refer to the process that makes the request, or the host computer on which the process operates. As used herein, the terms “client” and “server” refer to the processes, rather than the host computers, unless otherwise clear from the context. In addition, the process performed by a server can be broken up to run as multiple processes on multiple hosts (sometimes called tiers) for reasons that include reliability, scalability, and redundancy, among others. FIG. 2 is a diagram of the components of a device enabler, according to one embodiment. By way of example, the device enabler (DE) 109 can include one or more components for providing a platform to share authentication session information, such as authentication context, between different applications such as client applications running on run time environments and client applications such as browsers. It is contemplated that the functions of these components may be combined in one or more components or performed by other components of equivalent functionality. In this embodiment, the DE 109 can include a processor 201 or other logic for executing at least one algorithm for performing the functions of the DE 109. For example, when the DE 109 is accessed by one of the client applications 111 of FIG. 1 for authentication, the processor 201 in communication with the retrieval module 203, determines whether an authentication procedure has already been processed for the client application (and/or related client applications). For example, the retrieval module 203 can determine whether an authentication context exists for the client application requesting authentication. In one example, the retrieval module 203 can query the authentication database 117 to determine if the authentication context is available. Additionally, the retrieval module 203 can further determine if the authentication context is still valid, for example, if it has not expired. If the processor 201 in communication with the retrieval module 203 determines that a valid authentication context is available for the requesting client application, the retrieval module 203 retrieves the authentication context from a cache and/or a database such as the authentication database 117 and initiates transmission of the authentication context to the client application 111 requesting authentication. However, if the retrieval module 203 determines that an authentication procedure has already been processed by the DE 109 for the client application, which resulted in a failed authentication, the failed authentication result is further provided to the client application. Alternatively, according to certain embodiments, if the retrieval module 203 determines that no valid authentication context exists for the client application that requested authentication, user interface module 205 is invoked to launch a user interface (UI) to prompt a user of the client application 111 to provide authentication and/or identification information, such as user credentials. Data collection module 207 can collect the user authentication information and prepare an authentication request message to be sent to an authentication server, such as authentication server 107 of FIG. 1. The authentication server 107 can verify the user authentication information and generate an authentication context if the user and/or the client application is authorized or otherwise validated. In one example, the user information can include user credentials such as username and password and the authentication server 107 can compare the user credentials with stored credentials to authenticate the user and/or client application. Data collection module 207 can receive the authentication context from the authentication server 107. Further, the data collection module 207 can receive a failed authentication message from the authentication server 107 if the user information is not valid. The result of the authentication request (authentication context or failed authentication message) is conveyed to the client application. According to certain embodiments, if the authentication is successful and the authentication context is received by, for example, the data collection module 207, the caching/storage/population module 209 can cache and/or store the authentication context in, for example, the authentication database 117. Therefore, the authentication context can be used by, for example, the retrieval module 203 for authenticating subsequent requests from the same and/or other client applications associated with the DE 109. Further, the caching/storage/population module 209 can advantageously initiate population of the authentication context in another cache and/or database that is not directly linked with and/or utilizes the DE 109. For example, the caching/storage/population module 209 can populate the received authentication context in database 115 of FIG. 1 associated with the browser 113 of FIG. 1. Therefore, browser 113 of FIG. 1 can use the populated authentication context to access application servers 103 of FIG. 1 without a need to first authenticate itself with the authentication server 107. As mentioned, the caching/storage/population module 209 can populate the authentication context by copying it, converting it based, at least in part, on an authentication scheme supported by, for example, browser 113 of FIG. 1, etc. FIG. 3 is a flowchart of a process for sharing authentication session information, such as authentication context, between different applications (such as client applications running on run time environments and client applications such as browsers), according to one embodiment. In one embodiment, the device enabler (DE) 109 of FIG. 1 performs the process 300 and is implemented in, for instance, a chip set including a processor and a memory as shown in FIG. 7. In step 301, an authentication request is received. In one embodiment, the authentication request is received from a client application (such as client applications 111a-111m of FIG. 1) that is directly linked with and/or utilizes the DE 109. The authentication request can include information associated with the client application, a user of the client application, etc. In step 303, a determination is made regarding whether an authentication context already exists for the client application requesting authentication. In one example, the determination can be based on generating a query to a database, such as authentication database 117, to determine whether an authentication context associated with the client application was previously received and stored in the database 117. Additionally, according to certain embodiments, if the authentication context exists, in step 303 a determination can be made whether the authentication is valid, for example, if it has not expired. If a (valid) authentication context is available, in step 305 the authentication context is retrieved from, for example, a cache and/or a database, such as the authentication database 117 of FIG. 1. In step 307, the retrieved authentication context is transmitted to the client application requesting authentication. The client application can use the authentication context to access network services such as application servers 103 of FIG. 1. However, if in step 303 it is determined that a valid authentication context is not available, a request to receive authentication credentials associated with a user of the client application, which requests authentication, is generated in step 309. In one example, a user interface is initiated to prompt the user for authentication credentials, such as username, password, one time password, biometrics, etc. In step 311, the authentication credentials are received from the client application based, at least in part, on the request. In step 313, an authentication message is generated based, at least in part, on the received authentication credentials and the authentication message is transmitted to an authentication server, such as authentication server 107 of FIG. 1. The authentication server validates the authentication credentials (for example, by comparing it to stored credentials) to determine whether the user and/or the client application is authorized. In step 315, the result of the user and/or client authentication is received. More specifically, if the user and/or the client application are authorized, in step 315, an authentication context is received. In step 317, the authentication context is cached and/or stored in a cache and/or a database associated with the DE 109 such as the authentication database 117 of FIG. 1. The cached and/or stored authentication context can be further used by other client applications, which, for example, are directly linked with and/or utilize the DE 109. In step 319, the authentication context is further populated in a second cache and/or database, which is not directly linked with and/or utilizes the DE 109, for example, the database 115 of FIG. 1. In one example, the database 115 can be a cookie store associated with the browser 113 of FIG. 1. As mentioned, in one embodiment, in step 319, the population of the authentication context can include converting the authentication context based, at least in part, on an authentication scheme associated with the client application associated with the second cache and/or database. For example, the authentication context can include a token and in step 319 the authentication context is converted to a converted authentication context that include a cookie encrypted using username and password of the user. FIGS. 4A and 4B are time sequence diagrams that illustrate a sequence of messages and processes for providing a platform to share authentication session information, according to various embodiments. A network process is represented by vertical line. A message passed from one process to another is represented by horizontal arrows. A step performed by a process is indicated by the text. The processes represented in FIGS. 4A and 4B are the application servers 103, the authentication server 107, the device enabler (DE) 109, the client applications 111, the browser 113, the database 115, and the authentication database 117. The example of FIG. 4A discusses the process 400 of authenticating a client application and/or a user of the client application, receiving authentication context, storing the authentication context in a first cache and/or database, and populating the authentication context in a second cache and/or database. Also, the example of FIG. 4B discusses the process 420 of requesting authentication by a client application and accessing an application server by the browser. At 401 of process 400, one of the client applications 111 of FIG. 1, such as client application 111a initiates an authentication request to the device enabler (DE) 109. In one example, the authentication request can include information associated to the client application 111a, a user of the client application, an application server that the client application 111a desires to access, etc. At 403, the device enabler 109 initiates a dialog, such as a user interface (UI), to prompt the user for authentication credentials, if the DE 109 determines that the client application 111a has not already been authenticated. In one example, the determination is based, at least in part, on a search on a cache and/or a database associated with the DE 109 (such as the authentication database 117) to determine whether an authentication context associated with the client application 111a exists. During the dialog 403, the DE 109 can collect authentication credentials of, for example, a user of the client application 111a (and/or a user of the UE 101). At 405, the DE 109 generates and transmits an authentication request to the authentication server 107 to validate the authentication credentials collected by the DE 109. In one example, the authentication request can include the authentication credentials and/or information associated to the credentials. By way of example, the credentials can include username, password, one time password, consumer key, secret key, biometrics, etc. At 407, the authentication server 107 verifies the authentication credentials to determine whether the client application and/or the user are authorized. In one example, the received authentication credentials (or information associated to them) are compared with stored credentials. If authorized, at 409, an authentication context is conveyed to the DE 109. According to one embodiment, the authentication context can include a cookie or a token. The DE 109, at 411, initiates caching and/or storage of the authentication context in a cache and/or a database that is directly linked to and/or utilizes the DE 109, such as authentication database 117. The cached/stored authentication context can be further used by client applications directly linked to and/or utilizing the authentication database 117 and/or DE 109. At 413, the DE 109 conveys the authentication context received from the authentication server 107 to the client application 111a that requested authentication. Further, at 415 the authentication context is populated at a cache and/or a database that is not directly linked with and/or utilizes the DE 109. In one example, the authentication context is populated from the authentication database 117 to database 115. As mentioned, according to certain embodiments, at 415, the authentication context is converted based, at least in part, on an authentication protocol associated with the client application (such as the browser 113) that utilizes the database 115. It is contemplated that the messages and/or processes illustrated can be combined in one or more messages and/or processes or performed in other sequences. FIG. 4B illustrates exemplary processes of a client application (such as client application 111b) requesting authentication and a browser requesting access to an application server. At 421, the client application 111b sends an authentication request to the DE 109. In one example, the authentication request can include information associated with the client application 111b, a user of the client application 111b, etc. At 423, the authentication context associated with the client application 111b is retrieved and at 425 the retrieved authentication context is conveyed to the client application 425. According to certain embodiments, at 423, the DE 109 determines whether an authentication process has already been performed for the client application 111b and/or client applications (such as client applications 111) related to the client application 111b. In one example, the determination can be based, at least in part, on a query to the authentication database 117 of FIG. 1 to determine whether a valid authentication context is available. If no valid authentication context is available, process 400 of FIG. 4A can be performed. If the valid authentication context is available, it is retrieved and is conveyed to the client application 111b. The client application 111b can use the authentication context to, for example, access application servers 103 of FIG. 1. FIG. 4B further illustrates steps 427 through 435 which describe an exemplary process of the browser 113 accessing the application server 103 using authentication context populated at 415 of FIG. 4A. At 427, the browser 113 sends a data request to the application server 103. The data request can include information related to the browser 113, the application server 103, the populated authentication context, etc. In an embodiment, the authentication context has been populated in, for example, a cache and/or database associated with the browser 113 in a process such as process 400 of FIG. 4A. In one example, the populated authentication context can be a cookie that is stored in a browser cookie store. The browser 113 can access the browser cookie store to retrieve the cookie and include it in the data request 427. At 429 through 433, the application server 103 with the authentication server 107 verifies the validity of the populated authentication context. At 429, the application server 103 generates an authentication verification message and conveys the message to the authentication server 107. The authentication verification message can include the populated authentication context and/or information associated with it. At 431, the authentication server 107 verifies if the populated authentication context is valid. In one example, the authentication context 431 compares the authentication context (and/or information associated with it) to the authentication context (information associated with it, and/or authentication credentials of a user or client application) that was generated, for example at 407 of process 400 of FIG. 4A. At 433, the authentication server 107 sends a verification response to the application server 103 based, at least in part, on 431. If the populated authentication context is valid, at 435, the application server 103 returns the requested data to the browser 113. Although the embodiments discussed are concerned with processes that authentication context is first generated for client applications running on run time environment and is populated for other applications, such as browsers (e.g., via a push method for sharing authentication contexts), however it is contemplated reverse process (e.g., via a pull method for sharing authentication contexts) can also be implemented. For example, a client application, such as a browser, can be authenticated against an authentication server (such as authentication server 107 of FIG. 1), an authentication context can be generated and be cached and/or stored in a first cache and/or database associated with the client application, and the authentication context can be further populated in a second cache and/or database for other client applications that are not directly linked with and/or utilize the first cache and/or database. FIG. 5 is a diagram of an example user interface for providing data related to authentication credentials, according to one embodiment. As described previously, when the DE 109 of FIG. 1 receives an authentication request from one of the client applications 111 and determines that valid authentication context is not available, the DE can initiate a user interface (UI) to prompt a user of the client application for authentication credentials. FIG. 5 is a sample user interface 500 requesting such information. In this example, the user and/or the UE 101 can enter the user ID and password for authentication purposes. It is contemplated that the DE 109 may request any information for
{'bibliographic_information': "{'country': 'US', 'doc-number': '15091293', 'kind': 'B2', 'date': '20160405', 'invention_title': 'Method and apparatus for providing authentication session sharing'}", 'source_file': './grant/2017/ipg171031.xml', 'source_data': 'USPTO-Grant'}