Abstract: A method and system for secure authentication of a mobile computing device (MCD) are described. Data that identifies the MCD is obtained. Identification data is exchanged with a network service, which sends embedded data to trigger a secure browser instance on the MCD. A secure single action link specific to the requesting device is then provided, the secure single action link being actionable to communicate to the network service, through the secure browser instance, a session token corresponding to the mobile computing device. The user can perform a selection action on the secure single action link to authenticate the MCD.

Abstract: A method and system for secure authentication of a mobile computing device (MCD) are described. Data that identifies the MCD is obtained. Identification data is exchanged with a network service, which sends embedded data to trigger a secure browser instance on the MCD. A secure single action link specific to the requesting device is then provided, the secure single action link being actionable to communicate to the network service, through the secure browser instance, a session token corresponding to the mobile computing device. The user can perform a selection action on the secure single action link to authenticate the MCD.

Abstract: In an example embodiment, a container is downloaded, the container being an application natively executable by a first operating system of the user device, the container including: a container service including one or more libraries of functions designed by a container designer to natively operate on the first operating system; a browser; container metadata defining functions of the application, the functions compatible with the container service for the first operating system and also compatible with a container service for a second operating system; and a plug-in including one or more additional libraries of functions designed by an entity other than the container designer to perform additional native operations on the first operating system. Then, the container metadata can be executed using the browser, causing function calls to the container service and plug-in and thus controlling native functions of the user device.

Abstract: In an example embodiment, a container is downloaded, the container being an application natively executable by a first operating system of the user device, the container including: a container service including one or more libraries of functions designed by a container designer to natively operate on the first operating system; a browser; container metadata defining functions of the application, the functions compatible with the container service for the first operating system and also compatible with a container service for a second operating system; and a plug-in including one or more additional libraries of functions designed by an entity other than the container designer to perform additional native operations on the first operating system. Then, the container metadata can be executed using the browser, causing function calls to the container service and plug-in and thus controlling native functions of the user device.

Abstract: A providing computer system may receive a request, via a stateless protocol, to access a resource. An access control application may refer to administrative rules to set validation information associated with the request. Validation information may be in the form of electronic text that is stored in a location such as a cookie or state-table. Validation information may indicate the state of a session associated with a resource, such as whether a session is in a logged-in or logged-out state. When a request is received, validation information and authentication information may be utilized together to determine if access to a resource should be granted. When access to a resource is granted or denied, validation information may be updated to indicate that the state of the session has changed.

Abstract: A providing computer system may receive a request, via a stateless protocol, to access a resource. An access control application may refer to administrative rules to set validation information associated with the request. Validation information may be in the form of electronic text that is stored in a location such as a cookie or state-table. Validation information may indicate the state of a session associated with a resource, such as whether a session is in a logged-in or logged-out state. When a request is received, validation information and authentication information may be utilized together to determine if access to a resource should be granted. When access to a resource is granted or denied, validation information may be updated to indicate that the state of the session has changed.