Abstract: A connectivity state mapping system for mapping physical connections between interfaces of devices in a network is provided. The system includes at least one processor, at least one memory, and an application including instructions, which are executable by the at least one processor. The instructions are configured to: group the interfaces into groups; select one of the groups based on a predetermined fault plan; determine utilization parameters; based on the utilization parameters, cause at least one fault in one or more of the interfaces in the selected group; monitor events corresponding to the at least one fault and log data indicative of errors detected at the interfaces of the selected one of the groups; and based on the at least one fault and the predetermined fault plan, correlate the data to identify physical connections between two or more of the devices in the network.

Abstract: Described herein are various aspects pertaining to generating web tickets for use with authenticating computing devices to a computing system. Symmetric keys are used when generating the web tickets, wherein a symmetric key is valid for use when generating web tickets for a first period of time, and a web ticket generated based upon the symmetric key is valid for use when authenticating a computing device for a second period of time that is longer than the first period of time. Thus, the symmetric key is used for authenticating computing devices after it has ceased being used to generate web tickets.

Abstract: A connectivity state mapping system for mapping physical connections between interfaces of devices in a network is provided. The system includes at least one processor, at least one memory, and an application including instructions, which are executable by the at least one processor. The instructions are configured to: group the interfaces into groups; select one of the groups based on a predetermined fault plan; determine utilization parameters; based on the utilization parameters, cause at least one fault in one or more of the interfaces in the selected group; monitor events corresponding to the at least one fault and log data indicative of errors detected at the interfaces of the selected one of the groups; and based on the at least one fault and the predetermined fault plan, correlate the data to identify physical connections between two or more of the devices in the network.

Abstract: Described herein are various aspects pertaining to generating web tickets for use with authenticating computing devices to a computing system. Symmetric keys are used when generating the web tickets, wherein a symmetric key is valid for use when generating web tickets for a first period of time, and a web ticket generated based upon the symmetric key is valid for use when authenticating a computing device for a second period of time that is longer than the first period of time. Thus, the symmetric key is used for authenticating computing devices after it has ceased being used to generate web tickets.

Abstract: Described herein are various aspects pertaining to a web ticket that is used in connection with authenticating a user. The web ticket is generated through use of a symmetric key, and is less than two hundred bytes in size. A ticket issuer executing on a first computing device generates the web ticket responsive to receiving authentication data from a client computing device, and transmits the web ticket to such client computing device. The client computing device includes the web ticket in requests for data transmitted to a second server computing device that is in communication with the ticket issuer. The second server computing device includes a validator that validates the web ticket using the symmetric key, which is shared between the first server and the second server.

Abstract: Techniques to recursively discover services in a distributed environment may include receiving a request, including a unique client identifier, from a client device to access a home resource at a services site. The services site may identify which services site is mapped to the client domain of the unique client identifier in the request. If the services site that received the request is not the services site identified by the client domain, the services site that received the request may provide a redirect token that includes a link to the identified services site to the client device. Otherwise, the services site that received the request may provide one or more links to resources in a cluster within the services site. The links to resources may include a link to the requested home resource. Other embodiments are described and claimed.

Abstract: Described herein are various aspects pertaining to a web ticket that is used in connection with authenticating a user. The web ticket is generated through use of a symmetric key, and is less than two hundred bytes in size. A ticket issuer executing on a first computing device generates the web ticket responsive to receiving authentication data from a client computing device, and transmits the web ticket to such client computing device. The client computing device includes the web ticket in requests for data transmitted to a second server computing device that is in communication with the ticket issuer. The second server computing device includes a validator that validates the web ticket using the symmetric key, which is shared between the first server and the second server.

Abstract: Techniques to recursively discover services in a distributed environment may include receiving a request, including a unique client identifier, from a client device to access a home resource at a services site. The services site may identify which services site is mapped to the client domain of the unique client identifier in the request. If the services site that received the request is not the services site identified by the client domain, the services site that received the request may provide a redirect token that includes a link to the identified services site to the client device. Otherwise, the services site that received the request may provide one or more links to resources in a cluster within the services site. The links to resources may include a link to the requested home resource. Other embodiments are described and claimed.

Abstract: Techniques to manage transitions between private and public wireless networks for wireless devices are described. In one embodiment, for example, an apparatus may comprise a logic circuit and a memory unit. The apparatus may further include connection logic operative on the logic circuit to attempt a network connection by: retrieving a first access location value from the memory unit when attempting a network connection from the apparatus; retrieving a stored internal probe link from the memory unit when the access location value is internal; retrieving a stored external probe link from the memory unit when the access location value is external; attempting to connect to a network site referenced by the retrieved probe link; and connecting to a final location via the network site when the connection attempt to the network site is successful. Other embodiments are described and claimed.