Another nice trick you can pull with PostPostValidate
is pushing data directly to a backend server in the HTTP Headers or the URL parameters. This could be useful, for example, if you want your backend server to be able to recognize that a request is coming from UAG, as opposed to a regular user that is accessing it. Another use could be if you want the app to be aware of the user even if there's no single-sign-on happening. For this, the following function is used:
SetSessionResourceParam g_cookie, <Application ID>, <Authorization Key>, <Value>
For this to work, you also need to configure the relevant application. Let's say you are publishing your organization's ERP application and you want to give it the user's username in the request header. To do this, follow these steps:
1. Create the application and test it normally.
2. Open the Application Properties window, and obtain the Application ID from the General tab, as shown in the following...