Hi,
I’ve had a few occasions where a client has asked if they could have OWA or another application configured so that it can be reach directly. Sometimes they have done this themselves, and mostly they have had to ask why when a user navigates to the FQDN of the application does it not redirect to the correct path?
I normally come across this when I am publishing OWA, but its the same principle when publishing any resource. You must ensure that the redirects and default documents are configured correctly on the server we are going to reverse proxy through UAG.
When you configure the application, and lets use OWA as an example, you will most likely run through the wizard and entering the address of the backend server, the authentication repositories and perhaps some groups. Once you have this configured, open the newly created application again and add a “/” to the webserver paths configuration, then on the portal link remove the “owa/” from the initial URL and activate the changes.
Now the CAS servers would have a 302 redirect configured in IIS (only on the root directory, not the children), so any request that hits the root directory gets forwarded to the /owa/ directory.
When you navigate to the application URL without putting the path in, it will also redirect. So basically, UAG is doing what it is supposed to, the rest of the environment must be configured to support that.
