Book Image

Mastering Microsoft Forefront UAG 2010 Customization

Book Image

Mastering Microsoft Forefront UAG 2010 Customization

Overview of this book

While UAG is built to integrate with many environments and publish dozens of application types, many organizations require a certain level of customization to meet their needs. With this book in hand, you will be equipped to deal with these types of customization scenarios, and you will be confident in using such workarounds without hassle and trial and error. Written by some of the leading experts on UAG, "Mastering Microsoft Forefront UAG 2010 Customization" covers the most complex and challenging options for customizing UAG in a way that is friendly and easy to follow. It walks you through various customization tasks, including explanations and code samples, as well as creative ideas for troubleshooting your work. Until now, only a few of the extensions to UAG's services have been publicly available, and most were only known to a select few. Now, this can include you! Throughout this book, you will tackle how to change the system's look-and-feel, deal with advanced authentication schemes and write special functions that need to be executed as part of the client interaction. With "Mastering Microsoft Forefront UAG 2010 Customization", you too can learn how to customize various aspects of UAG's functionality to enhance your organization or customers' experience.
Table of Contents (16 chapters)
Mastering Microsoft Forefront UAG 2010 Customization
Credits
About the Authors
About the Reviewers
www.PacktPub.com
Preface

The UAG authentication flow


The UAG authentication flow actually starts before the logon page is seen by the user. As the browser calls the initial trunk URL, UAG automatically directs the user to a page that initializes the session parameters (Initparams.aspx) in case the user does not yet have an existing session. Once a session is initiated, UAG attempts to detect the presence of its endpoint components on the client, and if they do not yet exist, they are offered to the user through the normal Active-X installation dialogs. Only then is the user sent to the login page, following their decision to allow component installation, or decline and continue with limited functionality (web application publishing only and also no socket forwarding, no SSTP or network connector, no endpoint detection, and no endpoint-cleanup).

While the preceding info is not directly related to authentication, it's important to know that information collected during this phase can be vital to what then follows...