Abstract: Techniques for validating digital certificate information before signing are described. A method of validating digital certificate information before signing may include generating a to-be-signed (TBS) certificate, providing the TBS certificate to a certificate pre-issuance validation service to perform one or more validations on the TBS certificate, and receiving a request to issue a signed certificate based on the TBS certificate following validation of the TBS certificate by the certificate pre-issuance validation service.

Abstract: As provided herein, a first device may be registered as authorized to authenticate a user login into a service from a second device (e.g., a smart phone may be used to log the user into a webmail service on a computer without the user having to enter a password through the computer). Responsive to the user attempting to access the service through the second device, a login interface may be displayed on the first device. The user may confirm or deny that the user wants to log into the service on the second device, thus allowing the user to seamlessly log into the service on the second device (e.g., without entering a password) while mitigating unauthorized logins into the service from unknown devices. Further, the user may use the first device to delegate the authority to authenticate the user login into the service to one or more other devices.

Abstract: As provided herein, a first device may be registered as authorized to authenticate a user login into a service from a second device (e.g., a smart phone may be used to log the user into a webmail service on a computer without the user having to enter a password through the computer). Responsive to the user attempting to access the service through the second device, a login interface may be displayed on the first device. The user may confirm or deny that the user wants to log into the service on the second device, thus allowing the user to seamlessly log into the service on the second device (e.g., without entering a password) while mitigating unauthorized logins into the service from unknown devices. Further, the user may use the first device to delegate the authority to authenticate the user login into the service to one or more other devices.

Abstract: In one embodiment, a first set of applications installed on a first device is identified. Device characteristics of a second device may be ascertained. An application store for the second device may be determined based, at least in part, on the device characteristics of the second device. A second set of applications corresponding to the first set of applications is selected, where the second set of applications is available from the application store and compatible with the device characteristics of the second device.

Abstract: As provided herein, a first device may be registered as authorized to authenticate a user login into a service from a second device (e.g., a smart phone may be used to log the user into a webmail service on a computer without the user having to enter a password through the computer). Responsive to the user attempting to access the service through the second device, a login interface may be displayed on the first device. The user may confirm or deny that the user wants to log into the service on the second device, thus allowing the user to seamlessly log into the service on the second device (e.g., without entering a password) while mitigating unauthorized logins into the service from unknown devices. Further, the user may use the first device to delegate the authority to authenticate the user login into the service to one or more other devices.

Abstract: In one embodiment, an attempt to log in to a user account, by an application on a client device, is detected. It is determined whether the client device is a trusted device. An application password is generated and stored, by a server, in association with the client device and the user account based, at least in part, upon whether the client device is a trusted device.

Abstract: As provided herein, a first device may be registered as authorized to authenticate a user login into a service from a second device (e.g., a smart phone may be used to log the user into a webmail service on a computer without the user having to enter a password through the computer). Responsive to the user attempting to access the service through the second device, a login interface may be displayed on the first device. The user may confirm or deny that the user wants to log into the service on the second device, thus allowing the user to seamlessly log into the service on the second device (e.g., without entering a password) while mitigating unauthorized logins into the service from unknown devices. Further, the user may use the first device to delegate the authority to authenticate the user login into the service to one or more other devices.

Abstract: As provided herein, a first device may be registered as authorized to authenticate a user login into a service from a second device (e.g., a smart phone may be used to log the user into a webmail service on a computer without the user having to enter a password through the computer). Responsive to the user attempting to access the service through the second device, a login interface may be displayed on the first device. The user may confirm or deny that the user wants to log into the service on the second device, thus allowing the user to seamlessly log into the service on the second device (e.g., without entering a password) while mitigating unauthorized logins into the service from unknown devices. Further, the user may use the first device to delegate the authority to authenticate the user login into the service to one or more other devices.

Abstract: In one embodiment, a first set of applications installed on a first device is identified. Device characteristics of a second device may be ascertained. An application store for the second device may be determined based, at least in part, on the device characteristics of the second device. A second set of applications corresponding to the first set of applications is selected, where the second set of applications is available from the application store and compatible with the device characteristics of the second device.

Abstract: In one embodiment, a first set of applications installed on a first device is identified. Device characteristics of a second device may be ascertained. An application store for the second device may be determined based, at least in part, on the device characteristics of the second device. A second set of applications corresponding to the first set of applications is selected, where the second set of applications is available from the application store and compatible with the device characteristics of the second device.

Abstract: In one embodiment, a first set of applications installed on a first device is identified. Device characteristics of a second device may be ascertained. An application store for the second device may be determined based, at least in part, on the device characteristics of the second device. A second set of applications corresponding to the first set of applications is selected, where the second set of applications is available from the application store and compatible with the device characteristics of the second device.

Abstract: In one embodiment, an attempt to log in to a user account, by an application on a client device, is detected. It is determined whether the client device is a trusted device. An application password is generated and stored, by a server, in association with the client device and the user account based, at least in part, upon whether the client device is a trusted device.

Abstract: As provided herein, a first device may be registered as authorized to authenticate a user login into a service from a second device (e.g., a smart phone may be used to log the user into a webmail service on a computer without the user having to enter a password through the computer). Responsive to the user attempting to access the service through the second device, a login interface may be displayed on the first device. The user may confirm or deny that the user wants to log into the service on the second device, thus allowing the user to seamlessly log into the service on the second device (e.g., without entering a password) while mitigating unauthorized logins into the service from unknown devices. Further, the user may use the first device to delegate the authority to authenticate the user login into the service to one or more other devices.

Abstract: A method for determining an action to be performed for a content item includes the following operations: presenting a content item on a touch screen; receiving input via the touch screen indicating selection of the content item, wherein the selection of the content item produces a reduced version of the content item; in response to receiving the first input, displaying a plurality of options on the touch screen, each of the options identifying an action to be taken for the content item; detecting a dragging action on the reduced version of the selected content item that places the reduced version of the content item proximate to one of the plurality of options to indicate selection of the one of the plurality of options; performing the action identified by the selected one of the options for the content item.

Abstract: A user of a calendar application subscribes to a syndication feed corresponding to an event recorded at the calendar application in a calendar data format. The syndication feed commences sending feed data to the user upon occurrence of the event. The feed data indicates a status of the event. The syndication feed binds to a feed data entry in the calendar application that is associated with the calendar item. The feed data of the syndication feed is converted from a feed format to the calendar data format usable by the calendar application to produce converted feed data. The converted feed data is presented in the calendar application proximate to the calendar item. One or more of the subscribing, binding, converting, and presenting is performed by a computing device.

Abstract: A user of a calendar application subscribes to a syndication feed corresponding to an event recorded at the calendar application in a calendar data format. The syndication feed commences sending feed data to the user upon occurrence of the event. The feed data indicates a status of the event. The syndication feed binds to a feed data entry in the calendar application that is associated with the calendar item. The feed data of the syndication feed is converted from a feed format to the calendar data format usable by the calendar application to produce converted feed data. The converted feed data is presented in the calendar application proximate to the calendar item. One or more of the subscribing, binding, converting, and presenting is performed by a computing device.

Abstract: The present invention discloses a solution for adding syndication feeds to calendar data exchange enabled programs, such as programs conforming to the iCalendar (iCal) standard. Default syndication feed links can be established by a publisher of iCalendar data. Subscribers of iCalendar data can replace default syndication feeds with feeds from other sources and/or add their own syndication feeds to a program that supports iCalendar data. Information obtained from the syndication feeds can be stored in a calendar entry indexed fashion, so that users accessing a iCalendar program can view information obtained from the syndication feeds as well as information related to an iCalendar subscription.

Abstract: Techniques for supporting bundled services of network operators and service providers include generating a view to be presented on a display, the view comprising data that indicates a service provided by a vendor over a network. It is determined whether the service is associated with a service feature of a network operator of at least a portion of the network. If the service is associated with the service feature of the network operator, then data that indicates the service feature of the network operator is inserted into the view. The view is provided for transmission over the network.

Abstract: An apparatus including: a processor configured to determine whether there is a match between first identifier data received from a remote user terminal and second identifier data, and if there is a match to subsequently acquire and provide application service data to the user terminal; and one or more interfaces configured to receive the first identifier data, the second identifier data and the application service data.

Abstract: The present invention discloses a solution for adding syndication feeds to calendar data exchange enabled programs, such as programs conforming to the iCalendar (iCal) standard. Default syndication feed links can be established by a publisher of iCalendar data. Subscribers of iCalendar data can replace default syndication feeds with feeds from other sources and/or add their own syndication feeds to a program that supports iCalendar data. Information obtained from the syndication feeds can be stored in a calendar entry indexed fashion, so that users accessing a iCalendar program can view information obtained from the syndication feeds as well as information related to an iCalendar subscription.