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

Creating a Post Post Validate file


To create a custom Post Post Validate file, follow these steps:

  1. 1. Navigate to<UAG Path>\Von\InternalSite\Inc\CustomUpdate.

  2. 2. Create a new text file in that folder.

  3. 3. Name the file according to your trunk name, type, and with the suffix of postpostvalidate.inc. As with most custom INC files, if you have named your trunk UAGPortal, and it is an HTTPS trunk, the resulting filename would be UAGPortal1postpostvalidate.inc. For an HTTP trunk, use 0 instead of 1.

  4. 4. Create ASP code inside that file, enclosed in the standard<% %> structure.

Activating UAG is not required for this new file to be acknowledged and testing can be performed immediately, but whatever happens, be sure to activate at some point as the change will need to be pushed into the TMG storage and ultimately received by other members if you run an array.

Naturally, keeping the code bug-free is important, because if your code errors out, no one will be able to log in to the portal until...