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

How does custom authentication work?


The process of authentication with UAG includes three key pieces:

  • UAG presents the login form to the user and collects the credentials

  • UAG verifies the credentials against the defined authentication repository or repositories, defined on the trunk

  • UAG stores the credentials and reuses them when single sign on (SSO) is required, such as when launching a published application

To do this, the login form (login.asp) contains the fields that are to be collected. Once the form is submitted, the validation page (validate.asp) is called, and it verifies the credentials against the selected repository or repositories. The following diagram illustrates the authentication flow and the various functions that UAG will step through when authenticating users against a repository:

The processes that go on afterwards are less relevant here, but will be discussed in the next chapter.

The actual validation is handled by a single file, often referred to as repository.inc...