Abstract: Techniques are described for managing cookies, including separately managing cookie data associated with different browser tabs. Cookie management includes the isolation of whitelisted cookies from server responses into background storage and then back onto server requests, removing those cookies from the response header and thus from the cookie store. This isolation is managed with the concept of tab ownership between parent and child tabs to maintain isolation separately for each owner (e.g., the parent) and its children. Exposure to client pages is handled by placing those cookies into a keyed location in session storage for every tab where that cookie is to be visible. An event is then triggered for that client page to let it know that session storage has been updated.

Abstract: Techniques are described for managing cookies, including separately managing cookie data associated with different browser tabs. Cookie management includes the isolation of whitelisted cookies from server responses into background storage and then back onto server requests, removing those cookies from the response header and thus from the cookie store. This isolation is managed with the concept of tab ownership between parent and child tabs to maintain isolation separately for each owner (e.g., the parent) and its children. Exposure to client pages is handled by placing those cookies into a keyed location in session storage for every tab where that cookie is to be visible. An event is then triggered for that client page to let it know that session storage has been updated.

Abstract: Method and system are disclosed for limiting use of a service account to only applications that have been authorized. The method and system provide a service account security infrastructure for verifying the identity of an application requesting credentials from a service account and for checking that the application is authorized to use the service account. The infrastructure also allows service account owners and security personnel to manage service accounts, including establishing a secure identity for each application and granting authorization to the application to use a service account.

Abstract: A user calling a payment center has the option of using an automated speech recognition payment system or a human representative to make the payment. If the user selects to make a payment using a human representative, the representative may, at some point, transfer the user into the automated speech recognition payment system. If the user has already been authenticated, he may not need to re-authenticate himself to the system. If the user selects to make a payment the automated system, and then gets transferred to a human representative during the payment process, the representative may, at some point, transfer the user into the automated speech recognition payment system. Again, if the user has already been authenticated either by the system initially or by the representative, he may not need to re-authenticate himself to the system.