Dan Walther - Bellevue WA, US Michael Kramer - Yonkers NY, US Anthony Kueh - Issaquah WA, US Leszek Mazur - Bellevue WA, US
International Classification:
H04L009/00
US Classification:
713/151000, 713/168000
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.
A system and method for displaying an electronic program guide are disclosed. In one embodiment the method comprises receiving, for a plurality of first events, first event metadata comprising a first event description and a first logical channel number, receiving, for a plurality of second events, second event metadata comprising a second event description and a second logical channel number, assigning the first logical channel number associated with a particular first event to a particular second event, wherein the assignment is based on the first event metadata of the particular first event and the second event metadata of the particular second event, and displaying a program guide comprising at least a portion of the second event metadata of the particular second event.
Hero Cards That Display Contextual Information And Actions For Backend Systems
- Palo Alto CA, US Adam Cianfichi - Newark DE, US Neal Foster - Atlanta GA, US Marshall Anne Busbee - Atlanta GA, US Dan Zeck - Roswell GA, US Rob Worsnop - Atlanta GA, US Anthony Kueh - San Jose CA, US Andrew Eye - Atlanta GA, US
Systems herein supply hero cards that display contextual information and actions based on backend systems. The information and actions are related to a trigger content item in an application that does not have access to the backend systems. A hero agent running a user device can communicate the trigger content to a hero server. The hero server can determine which connectors to backend systems relate to the user device, and then can retrieve result information from one or more of the backend systems. The result information populates the hero card, which the hero agent displays within the application. Action buttons on the hero card cause the hero agent to contact one or more of the backend systems to cause an action to take place there.
Determining A Device Posture Using A Device Posture Token
Disclosed are various approaches for generating a device posture token corresponding to a client device. The device posture token can be used by a verification computing device to determine whether the client device complies with the security policies of a particular facility.
Systems And Methods For Dynamically Applying Information Rights Management Policies To Documents
- Palo Alto CA, US Yugansh Arora - Atlanta GA, US Kunal Muchhala - Sandy Springs GA, US Gaurav Arora - Cumming GA, US Anthony Kueh - San Jose CA, US Deep Singh - Atlanta GA, US
International Classification:
G06F 21/62 G06F 21/10 H04L 9/32 G06F 16/11
Abstract:
Systems and methods are disclosed herein for dynamically applying information rights management (“IRM”) policies to documents. An example system for dynamically applying IRM policies to documents can include a document repository, a proxy server, and a dynamic IRM wrapping service (also referred to herein as an IRM engine). A user can request a document on the document repository by, for example, attempting to access the document from a user device. The user device can be managed by a management server that enrolls the user device and enforces compliance rules and other policies at the user device. The user's request for the document can be received at the proxy server, and the proxy server can then request the document from the document repository.
In one example of federated mobile device management, a first management service federates with a second management service based on an exchange of one or more identity authentication certificates. After the management services have federated or affiliated, the first service can enroll a client device for management based on federated management data, where the federated management data includes first device management data of the first management service and second device management data of the second management service. The first service can also identify a change in affiliation associated with at least one of the client device or the second management service and cause the client device to check in for a device management update based on the change in affiliation.
Determining A Device Posture Using A Device Posture Token
Disclosed are various approaches for generating a device posture token corresponding to a client device. The device posture token can be used by a verification computing device to determine whether the client device complies with the security policies of a particular facility.
Hero Cards That Display Contextual Information And Actions For Backend Systems
- Palo Alto CA, US Adam Cianfichi - Newark DE, US Neal Foster - Atlanta GA, US Marshall Anne Busbee - Atlanta GA, US Dan Zeck - Roswell GA, US Rob Worsnop - Atlanta GA, US Anthony Kueh - San Jose CA, US Andrew Eye - Atlanta GA, US
Systems herein supply hero cards that display contextual information and actions based on backend systems. The information and actions are related to a trigger content item in an application that does not have access to the backend systems. A hero agent running a user device can communicate the trigger content to a hero server. The hero server can determine which connectors to backend systems relate to the user device, and then can retrieve result information from one or more of the backend systems. The result information populates the hero card, which the hero agent displays within the application. Action buttons on the hero card cause the hero agent to contact one or more of the backend systems to cause an action to take place there.