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

What content alteration can do for you


Altering content is critical for the HAT process that we discussed in the Chapter 1, Customization Building Blocks, and for a lot of applications, it is equally important to maintain basic functionality alone. For example, when UAG publishes Citrix, altering some of the page content is necessary because Citrix was never designed to be published in this scenario. Without the specific alterations, the user would not even be able to launch the Citrix web page, and instead, the browser would go into an error loop.

In other circumstances, the content alteration makes the user experience more savory. For example, when OWA is published through UAG, the Sign out button that OWA usually displays is removed by UAG, with the intention that the user would instead be forced to use the portal frame's Log Off button, located on the UAG toolbar as shown in the following screenshot:

UAG has two mechanisms for manipulating content. One is called The Application Wrapper...