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

Skipping cookie signing


As you probably know, in addition to signing URLs in the contents of pages delivered to the client, UAG also performs a similar process with cookies sent by the server. The reason is the same — to be able to match the cookies to the application the user is using and forwarding them to the correct backend server, and only it. However, occasionally you might find yourself needing to avoid that process. Typically, this would be required for applications that have client-side handling code, which would not be able to see these cookies, as their name is different from what the application would be expecting.

One specific example of this is PeopleSoft, which uses multiple cookies, and quite a lot of client-side code to handle them. When publishing this application with the standard template, UAG will sign all the cookies, and that will cause the client-side code to think the user's session with the PeopleSoft server has expired, and send him/her to an error page:

This type...