When you use Forefront Unified Access Gateway (UAG) with Active Directory Federation Services (AD FS) 2.0 authentication, you may encounter a number of errors when activating the configuration in the Forefront UAG Management console.
The following table provides links to troubleshooting topics for the errors that you may encounter:
Forefront UAG Troubleshooting - The AD FS 2.0 application does not allow unauthenticated access
Forefront UAG Troubleshooting - The application uses KCD for SSO, but no claim type is provided
Forefront UAG Troubleshooting - The AD FS 2.0 authentication server is used in more than one trunk
The AD FS 2.0 authentication server 'authentication_server' is used in more than one trunk: trunk_list. Configure Forefront UAG to use the AD FS 2.0 authentication server in one trunk only.
The trunk 'trunk_name' contains applications that have the same public host name and path. Configure unique public host names and paths for these applications:
An AD FS 2.0 authentication server is used in trunk 'trunk_name'. The authentication server should be associated with an AD FS 2.0 application to provide automatic management of the AD FS 2.0 application. You can associate your current AD FS 2.0 application 'application_name' or you can create a new AD FS 2.0 application. Do you want to associate your current AD FS 2.0 application with the authentication server?
Maheshkumar S Tiwari edited Revision 3. Comment: Added tags
Ed Price MSFT edited Revision 2. Comment: Title and tag updates.