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

Putting data into the session


We just saw how you can retrieve session data, but in a similar fashion, you can also put your own data into the session. The following is a function that does that:

AddSessionUser g_cookie,"User","Password","Repository"

The function AddSessionUser resides in \Von\InternalSite\Inc\SessionMgr.inc, and as you've probably guessed, is used to add a user's submitted credentials into the session, so as to use them later for single sign on. By invoking this function ourselves in PostPostValidate.inc, we can also take advantage of this to add extra credentials into the session for any chosen repository. What would that be good for, do you ask? Well, one good example is when users are required to authenticate to an application that does not use the same repository that a trunk is configured with for initial login. In this scenario, the application would need credentials that it can expect to validate and authenticate against whatever directory or scheme it is configured...