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

SRA syntax


The SRA engine is very similar to AppWrap, but it does offer a few additional strengths. The primary difference is that SRA is the engine that performs the HAT signing of URLs for every piece of content UAG goes through. It can do regular search and replace just like AppWrap, but its real power is in our ability to teach UAG to recognize and sign HTML code that it wasn't initially designed to.

The need for this sort of situation would arise if some application generates HTML code that UAG cannot recognize, leading to HAT signing failure. There are additional mechanisms that help UAG deal with that, but if all fails, you may need to address this manually. Dealing with missed links can be done by locating the missed links, and adding a custom AppWrap or SRA file that will perform the necessary search and sign of these rogue links A better way would be to configure UAG to correctly recognize the code for the link so that it can sign it automatically, rather than by us having to fix...