The vast majority of user interactions between an end-user and a UAG server are performed within the context of a UAG session. This includes access to all kinds and types of applications that we covered so far in this book—web, client/server , browser-embedded , Remote Desktop Services, Remote Network Access (both when using Network Connector and when using SSTP), and so on. In most cases, these sessions are authenticated sessions, meaning that the user's identity is verified at the very beginning of the session. In reality, only a very small number of real world scenarios require or allow anonymous access through UAG, so the authentication mechanism is an important part of the entire UAG solution.
So what is a UAG session? A UAG session is a logical grouping of client requests and of server responses, whether issued by the UAG server itself of by a backend application. The common denominator is that all of these are sent by (or to) the same client...