Enabling Windows Integrated Authentication
- About This Document
- Enabling Kerberos on the Search Appliance
- Using SAML Bridge with the Search Appliance
- Configuring SAML Bridge in IIS
- Additional Steps to Configure SAML Bridge for POST Binding
- Verifying the SAML Bridge Configuration
- Configuring the Search Appliance to use SAML Bridge for Authentication
- Completing the Configuration Process
- Troubleshooting SAML Bridge for Authentication
- Authorize Content with SAML Bridge
- Uninstalling the SAML Bridge Installer
By default, Google Search Appliance users who search for and view secure content must enter credentials. In a Windows domain environment, you can configure the search appliance to use one of two methods that remove the need for redundant logins.
The preferred method to enable Windows Integrated Authentication on the search appliance is to enable onboard Kerberos. However, for environments in which Kerberos is not an option, SAML Bridge for Windows is provided for Windows integration.
This section describes the audience for this document and some additional sources of information.
This document assumes that you are an experienced Windows administrator. You must have privileges to configure Active Directory and to configure the Internet Information Services (IIS) server that will host SAML Bridge, or access to someone who can do that.
For background information on Kerberos refer to these sources:
- The topic “Configuring Crawl and Serve for Kerberos” in the document Managing Search for Controlled-Access Content and the online help topics on the pages cited in that topic.
- A Google search on Kerberos (http://www.google.com/search?q=kerberos can provide background information on the Kerberos network authentication protocol.
For background information on the technology described in this document, refer to these sources:
- The topic "The SAML Authentication Service Provider Interface (SPI)" in the document Managing Search for Controlled-Access Content, and the online help topics on the pages cited in that topic.
- The Authentication/Authorization for Enterprise SPI Guide. SAML Bridge is an application of the Google Search Appliance Authentication/Authorization SPI, for which it has the roles of Identity Provider and Policy Decision Point. These terms are explained in the SPI Guide.
- A Google search on SAML (http://www.google.com/search?q=saml) can provide background information on the SAML protocol.
There are two options for enabling silent authentication in Windows on the Google Search Appliance:
- Enable Kerberos on the search appliance.
This is called “Kerberizing” the search appliance and is preferred because Kerberos is onboard and easy to configure.
- Use SAML Bridge for Windows.
SAML Bridge mediates between your users and your Windows domain. It is implemented as an ASP.NET website that resides in Windows Internet Information Services (IIS). Scenarios for deployment that require the use of SAML Bridge instead of onboard Kerberos are:
- Mixed environments in which not all browsers support Kerberos and SAML Bridge is required because it supports NT LAN Manager (NTLM).
- Environments that do not allow key tab use for Kerberos, which is how the search appliance is “Kerberized”.
In addition, you can use either a Kerberized search appliance or SAML Bridge to authorize web content. You do this by using an HTTP head request. While the Kerberos implementation on the search appliance supports IIS websites authorization, it does not support Kerberos constrained delegation. SAML Bridge for Windows provides a workaround for this.
Choose one of the following based on how your environment will provide authentication:
On board Kerberos can be used for both crawling and for serving controlled-access content. You must configure the search appliance to use Kerberos authentication at serve time. For information about configuring Kerberos-based authentication for serving, refer to the topics "Configuring Crawl and Serve for Kerberos" and "Kerberos-Based Authentication" in the document Managing Search for Controlled-Access Content.
It is preferable to achieve silent authentication by enabling Kerberos on the search appliance (called “Kerberizing”). However, if your implementation requires the use of SAML Bridge for authentication (see examples in the Overview), then SAML Bridge can be used to mediate between your users and your Windows domain. SAML Bridge is implemented as an ASP.NET website that resides in IIS.
SAML Bridge can be used to
The following process describes the role of SAML Bridge in the lifecycle of a search query when SAML bridge is used for authentication:
- A user performs a secure search.
- The search appliance redirects the user to SAML Bridge.
- SAML Bridge authenticates the user.
- The search appliance gets the user name (and domain, if configured) from SAML Bridge. This is the verified identity.
- The search appliance passes the verified identity of the search user to the authorization phase.
The following prerequisites apply to the IIS content server that hosts SAML Bridge:
- IIS must be at version 7.5 or later.
To verify the version of IIS, do this: In the Start menu, choose Administrative Tools > Internet Information Services (IIS) Manager. In the IIS Manager, choose Help > About.
- The server must be running .NET Framework Version 2.0 or later. To verify the version, in the IIS Manager tree view, under the host name, choose Web Service Extensions. In the Web Service Extensions panel, look for ASP.NET version 2.0 or later.
- Ensure the Windows authentication role service is enabled on IIS. To enable the Windows authentication on IIS:
- In Server Manager, click Add Roles and Features wizard, then click Next.
- On Server Roles page, go to Web Server (IIS) > Security > Windows Authentication, and click Next.
- On Features Page, click Next, then click Install.
Additional prerequisites apply to content servers when using SAML Bridge for Authorization. For details, see Prerequisites for Using SAML Bridge for Authorization.
Note: If you have already installed Search Box for SharePoint or Content Services for SharePoint using the installer (Google Search Appliance Resource Kit 3.2.4), please uninstall them before using the SAML Bridge for Windows 4.1.3 installer.
You can install SAML Bridge on any IIS server that meets the prerequisites described above.
To install SAML Bridge:
- Start a web browser and navigate to https://github.com/googlegsa/samlbridge/releases.
- Download the samlbridge-install-4.1.3 file, which has the extension
- Double-click the installer file. The Welcome screen is displayed.
- Click Next.
- On the Installer Type panel, select Custom and click Next. On the Custom Setup panel, select SAML Bridge for Windows 4.1.3.
- Click Next, and Install.
- Enter the port number on which the SAML Bridge applications will run.
- Configure the SAML Bridge for Windows Configuration Wizard:
- Enter the GSA artifact_consumer URL. For multi-host GSA configurations, include the artifact consumer URLs, separated by commas.
- Enter certificate_friendly_name.
- Enable debug logs.
- Click Save.
- Click Finish.
If you’re installing SAML Bridge for silent authentication, see Configuring SAML Bridge in IIS.
If you’re installing SAML Bridge to authorize web content, see Configuring the Search Appliance to Use SAML Bridge for Authorization. This is no longer a common use but might be needed in some environments, as described in the Overview.
After you install SAML bridge, proceed to the next section, Configuring SAML Bridge in IIS 7.5 with Windows 2008 R2.
SAML Bridge is implemented as a virtual directory that runs in IIS. In SAML Bridge 4.1.3, the virtual directory is created automatically when you install SAML Bridge, and files in the
saml-bridge virtual directory have anonymous access. The following steps apply when you use IIS 7.5 or later.
Verifying the .NET Framework Version
To verify the version of .Net framework in Windows 2008 R2:
- Open IIS Manager.
- Under Application Pools, look for the version in the .Net framework version column.
- Verify that the value is version 2.0 or later.
This process verifies that the Application Pool Identity for SAML Bridge is Network Service.
- In the IIS Manager tree view, click to expand the Application Pools.
- Select the name of the application pool that was configured for SAML Bridge and select Advanced Setting from the Actions pane.
- Under Process Model, verify that the value of Identity is set to Network Service.
- Click OK to close the dialog box.
Next, configure the IdP endpoint in IIS for SAML Bridge.
SAML Bridge supports both POST Binding, which is recommended, and Artifact Binding. As a SAML IdP, SAML Bridge uses different endpoints for these binding types. The endpoint is where the search appliance redirects the client to be authenticated. For POST Binding,
Post.aspx is the authentication endpoint. For Artifact Binding,
Login.aspx is the authentication endpoint.
To configure the IdP endpoint so that the user’s browser sends Windows login credentials for authentication:
- In the IIS Manager under Web Sites, select
- Select the Content view.
- Select the appropriate endpoint:
- If you are using POST Binding (recommended), select
- If you are using Artifact Binding, select
- If you are using POST Binding (recommended), select
- In the Actions pane, click Switch to Features view, which displays either the
Login.aspxhome, depending on the endpoint you previously selected.
- Double-click the Authentication icon.
- Select Anonymous Authentication and click Disable in the Actions pane.
- Select Windows Authentication and click Enable in the Actions pane.
The endpoint file is treated differently from other files in SAML Bridge. The endpoint file identifies users by enabling authentication. Other files (in particular,
Authz.aspx used for Artifact Binding and authorization) must allow anonymous access in the virtual directory.
To grant permission for users to write to the SAML Bridge log file:
- Right-click the
saml-bridgeweb site in IIS and select Explore.
- Right-click the
ac.logfile and select Properties.
- In the Security tab click Add.... The Select Users, Computers or Groups dialog box appears.
- Click Check Names. The
saml-bridgeweb site is mapped to everyone in the current domain.
- Click OK.
- In the Permissions for Everyone list, check the box in the Full Control row and the Allow column.
- Click OK.
POST Binding requires a public key and private key pair that are used to encrypt and decrypt the response message from the SAML IdP. The SAML IdP uses the private key to encrypt the message, and the search appliance uses the public key to decrypt it.
SAML Bridge looks for the certificate located in the server key store. You can follow the standard process of enabling HTTPS for the IIS web site to create a key request, generate a certificate from your certificate authorityCA, and upload it to the IIS server where SAML Bridge is installed. Although the certificate is available for HTTPS serving, SAML Bridge can still use HTTP to serve.
To configure SAML Bridge for POST Binding, you must:
If there is a certificate on the server where SAML Bridge is installed, locate the certificate name in the server key store. You must copy the certificate name to the
If there is not a ready-to-use certificate, you must create one. The certificate for SAML POST Binding can be generated the same way it is for HTTPS serving in IIS. See http://technet.microsoft.com/en-us/library/cc753127(v=ws.10).aspx for details on generating a certificate in Windows.
To locate the name of the certificate on the server and copy the certificate name to the
- Select Run in the Start menu, and type
mmcto display the management console.
- Choose File > Add/Remove Snap-in, and click Add to select a certificate to add. A wizard displays, which lets you choose the account to manage certificates.
- Choose Computer Account, and click Next.
- Select Local Computer, and click Finish.
- In the previous dialog box, click Close , and then click OK to return to the main window.
- In the certificates tree, navigate to and expand the node named Personal. This is where certificates are stored in IIS.
- Double click the certificate to display its properties.
- In the Details tab, locate the Friendly Name attribute, and copy it as the value for the
certificate_friendly_nameattribute in the SAML Bridge
Also, note the value of the Subject attribute in the Details tab. You will need it in the next step to grant SAML Bridge access to the certificate.
In order for SAML Bridge to load the certificate that contains the private key, the Application Pool Identity that runs SAML Bridge requires permission to access the certificate. Check permissions using the WinnHttpCertCfg tool, which you might have to download.
To list accounts that have access to this certificate, type:
winhttpcertcfg -l -c LOCAL_MACHINE\My -sany_word_in_the_subject_attribute_of_the_certificate
To grant the Network Service account access to the certificate, type:
winhttpcertcfg -g -c LOCAL_MACHINE\My -sany_word_in_the_subject_attribute_of_the_certificate
-a "Network Service"
You must copy the public key in text format into the SAML configuration in the search appliance Admin Console: Search > Secure Search > Universal Login Auth Mechanisms > SAML tab (Public Key of IDP field). If the public key is in PEM format, you can obtain the base64 encoded text from the certificate. If the certificate is not in PEM format, you must convert it to PEM format.
If the certificate is also used for HTTPS, you can use FireFox. Open a FireFox browser, and go to the website where the certificate is used for HTTPS.
To convert a certificate to PEM format:
- Open a FireFox browser, and click the lock icon that appears in the status bar. The Certificate Viewer window displays.
- Click View Certificate,
- In the Details tab, click Export.
- Click Save.
This step verifies that the SAML Bridge Application Pool is using Network Service and that SAML Bridge can obtain a user’s identity.
In the address field of an Internet Explorer browser, enter one of the following depending on the type of binding you are using:
- For POST Binding (recommended):
- For Artifact Binding:
You’ll see a response such as the following, which assumes that your domain is
sam1 and your Windows account is
Application Pool Identity = NT AUTHORITY\NETWORK SERVICE Your Windows account = sam1\davidd Use Login.aspx?subject=user@domain to test impersonation
The NETWORK SERVICE keyword shows that SAML Bridge is properly configured to use Network Service. If Application Pool Identity is not set to Network Service, follow steps in Verifying the Configuration in IIS 7.5 of the SAML Bridge Application Pool, depending on the version of IIS you use.
In the response, you’ll see your own domain and login information, because you accessed the file. When the system is in use, the file obtains the domain and login information for each authenticated user.
When you configure the search appliance to use SAML Bridge for authentication, you configure it to use the authentication SPI.
To configure the search appliance, do the following:
- In the search appliance Admin Console, click Search > Secure Search > Universal Login Auth Mechanisms.
- In the SAML tab, select the credential group from the drop-down list.
- Type a value in the Mechanism Name field.
The name you enter will appear as an Authentication ID on the Search > Secure Search > Flexible Authorization page. The Mechanism Name enables you to instruct the authorization mechanism to use a session identity from a specific credential group or instance of an authentication mechanism.
- Type a value in the IDP Entity ID field.
The IDP Entity ID uniquely identifies the SAML Bridge installation. To locate this value, navigate to the
saml-bridgevirtual directory and open the
web.configfile. If this value is blank in the
web.configfile, use the host name for this value.
- In the Login URL field, type the login URL of SAML Bridge, which is in the format:
- Specify the binding in which the search appliance communicates with the SAML Bridge server:
- If you're using POST Binding, which is recommended, enter the Public Key of IDP. Leave Artifact Resolver URL blank. The POST Binding URL is in the format:
- If you're using Artifact Binding, enter the Artifact Resolver URL. Do not specify a Public Key of IDP. The Artifact Resolver URL is in the format:
- If you're using POST Binding, which is recommended, enter the Public Key of IDP. Leave Artifact Resolver URL blank. The POST Binding URL is in the format:
- Click Save.
Follow steps in this section to complete the configuration process.
The system clock of the SAML Bridge host and the system clock of the search appliance must be synchronized to prevent the search appliance from invalidating authentication responses. The search appliance treats an authentication response as invalid if the timestamp of the response is not close to the time of the search appliance system clock.
Verify that these system clocks are synchronized.
If your environment uses Network Time Protocol (NTP), do the following:
- Check that an NTP server is running on your network.
- Test that the search appliance is configured to use NTP:
- In the search appliance Admin Console, go to Administration > Network Settings.
- Ensure that the NTP server is specified.
- Use the Network Diagnostics box to test connectivity between the search appliance and the NTP server.
- Check that the NTP service is running on the SAML Bridge host, on the content servers, and on the domain controller.
Verify that the two systems can communicate with each other:
- In the Admin Console, go to Administrator > Network Settings.
- In Network Diagnostics, enter the URL for the
Login.aspxfile in the URLs to Test box as follows, where your_ac_host is the name of the host on which SAML Bridge is installed:
- Click Update and Perform Diagnostics.
If you discover problems here, check for network connectivity issues as you would for any two hosts.
SSL is required by the SAML artifact consumer URL on the Google Search Appliance but not by the search page or SAML Bridge. However, if you do not enable SSL on both the search appliance and SAML Bridge host, secure searches display warnings about redirection to secured sites from non-secured sites. Therefore, Google recommends that you enable SSL on both the search appliance and SAML Bridge.
For information on how to enable SSL for the search appliance, in the Admin Console, click Administration > SSL Settings. Use the online help that is available from that page for information.
For information on how to enable SSL for SAML Bridge, refer to the Microsoft IIS documentation.
Perform a search of secure content. You should not be prompted to log in. You can now proceed to configure policy ACLs or a connector for authorization.
This section contains some troubleshooting tips that apply to authentication. Some general tips for narrowing your problem are:
- If one account can’t be impersonated, try a different account.
- If one URL doesn’t work, try another.
- If one content server can’t be authorized, set up a simple web server and use it as the content server.
- Set the log level in the SAML Bridge
web.configfile to ‘debug’, and then view the
ac.logfile for log messages.
- Monitor these additional files: the web server log, the Windows audit events in the event viewer, and the results produced by Kerberos tracing tools.
When you test impersonation (see Verifying the SAML Bridge Configuration) by accessing one of the following URLs, you are prompted to enter your username and password when you should not be prompted:
If you enter credentials and are granted access, the cause of this problem can be one of the following:
- Security for the
.aspxfile might be configured incorrectly.
- Your Internet Explorer browser is using enhanced security settings, and the SAML Bridge host is not recognized as an Intranet site.
If you enter credentials but are not granted access, the Kerberos configuration may be incorrect and might have duplicate SPNs configured. Contact Microsoft Support.
When you test impersonation (see Verifying the SAML Bridge Configuration), some users can be impersonated but others cannot.
There are many reasons why user security can be inconsistent. One method to resolve this problem is as follows:
- Select a couple of users from the group that can be impersonated and a couple of users from the group that cannot be impersonated.
- Open the Active Directory Users and Computers console.
- Click View > Advanced.
- Select a user account that cannot be impersonated and double click to display the Properties window.
- Select the Security Window.
- By default, the permissions for Authenticated Users is Read.
- If the user you selected does not have Read access, grant that user Read access.
- Click Apply and then click OK.
Although SAML Bridge can also be used to authorize content that resides on web servers, this is no longer a common use for it. If you will be using SAML Bridge for authorization because your environment requires it as described in the Overview, follow steps in this section to meet prerequisites for installing and configuring it.
The following process describes the role of SAML Bridge in the lifecycle of a search query when SAML Bridge is used for authorization:
- A user creates a search query that includes secure content.
- The search appliance authenticates the user and passes the verified identity to the authorization process.
- The search appliance determines the search results for the user. If the results include secure content, the search appliance uses the Authorization SPI to send an authorization request to SAML Bridge. SAML Bridge then verifies the user's permissions to view the results.
- SAML Bridge checks the user's access to the search results content by impersonating the user to the content server.
- If SAML bridge is using NTLM, it sends a headrequest on the user's behalf to content server.
- If SAML Bridge is using Kerberos, it obtains a Kerberos ticket to use on the user's behalf. This is possible because the domain server is configured to enable SAML Bridge to impersonate the user to the content server.
- SAML bridge tells the search appliance which documents the user can access.
Review "Authentication/Authorization for Enterprise SPI Guide" for more details about communications between search appliance and SAML Bridge host.
If you are using SAML Bridge for authorization, the following prerequisites apply:
- Content Server Kerberos Prerequisites
- Active Directory and Domain Controller Prerequisites
- Modifying the Windows Registry
- Granting ‘Act as Part of the Operating System’ Privilege
When SAML bridge is used for authorization, Kerberos must be running on each content server whose content requires authorization.
To verify whether Kerberos is being used, you can use tools such as Windows Network Monitor or tcp trace or a browser extension that shows HTTP headers. You can view the headers that result from any communication with the content server. The content server should send the following header when Kerberos is in use.
For example, in the following header, look for the Negotiate header in the server responses.
GET /saml-bridge/login.aspx HTTP/1.1 Accept: text/html, image/gif, image/x-xbitmap, image/jpeg, / Accept-Language: en-us Accept-Encoding: gzip, deflate User-Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.3; .NET CLR 2.0.50727) Host: myhost Connection: Keep-Alive HTTP/1.1 401 Unauthorized Content-Length: 1656 Content-Type: text/html Server: Microsoft-IIS/7.5 WWW-Authenticate: Negotiate WWW-Authenticate: NTLM MicrosoftOfficeWebServer: 5.0_Pub X-Powered-By: ASP.NET Date: Monday, 24 Apr 2017 21:26:01 GMT
You can refer to an unsupported Wiki page on configuring Kerberos for more information (http://code.google.com/p/google-saml-bridge-for-windows/wiki/ConfigKerberos).
If SAML Bridge is only used for authentication, Kerberos is not required on the content servers. However, because the search appliance requires the authorization service to be specified to allow the basic authentication prompt to be muted, you must properly configure SAML Bridge for authorization. To do this, perform the steps in Active Directory and Domain Controller Prerequisites on the domain controller machine, and perform the steps in Granting ‘Act as Part of the Operating System’ Privilege.
The domain controller that is running Active Directory must meet the following requirements:
- Windows Server 2008 R2 Kerberos Extension must be available. Kerberos is used for authentication between SAML Bridge and the content server.
- The domain functional level must be set to Windows Server 2008 R2. Refer to the Microsoft Technet site for instructions about how to raise the domain functional level.
- Active Directory must be configured to permit SAML Bridge to use delegated credentials from the user to access server content.
To configure Active Directory to permit SAML Bridge to use delegated credentials:
- Open the Microsoft Management Console (MMC) Active Directory Users and Computers snap-in.
- In the tree view, click Computers.
- In the right pane, select the server hosting SAML Bridge, right click, and select Properties.
- In the Properties dialog box, click the Delegation tab.
- Select Trust this computer for delegation to specified services only.
- Select Use any authentication protocol.
- Click Add. The Add Services dialog box appears.
- Click Users or Computers. The Select Users or Computers dialog box appears.
- Under Enter the object names to select, enter the Service Principal Name (SPN) for the Kerberized content server to which the SAML Bridge host will delegate.
- If you are using Network Service to run an HTTP service, enter the name of the content server.
- If you are using a domain account to run an HTTP service, enter the name of the domain account.
- If you are using Microsoft Cluster Server to run a CIFS server, enter the Network Name of the group that contains the file share.
- Optionally, click Check Names to verify that you entered the name correctly.
- Click OK. The Add Services dialog box reappears, showing the available services for the object whose SPN you specified.
- To select one or more services to which SAML Bridge will delegate, first identify the service type, and then select the name in the User or Computer column.
To find the service type if the content server is a web server or SharePoint server, the service will be listed in the Service Type column as HTTP.
To select the name of the services in the User or Computer column:
- If users will access the content server using the NetBIOS name, select that name.
- If users will access the content server using a DNS alias, select the DNS alias.
- If the content server is a load balanced web server, select the associated virtual host name. You’ll also need to select the NetBIOS name of each physical server represented by the virtual host.
- Click OK. The Properties dialog box reappears. Under Services to which this account can present delegated credentials, you can view the list of services that you just specified.
- Click OK to close the Properties dialog box and then close the Active Directory Users and Computers snap-in.
This step is required only if the same IIS server is both a SAML Bridge host and a content server.
To avoid problems that occur when SAML Bridge attempts to access the local web files, you’ll need to update the Registry, by following the instructions in Microsoft KB article 896861 (http://support.microsoft.com/kb/896861/).
When the search appliance sends an authorization request with a user name, SAML Bridge can generate a Windows token by impersonation. However, it can use the token to access remote resources only if it has the privilege to ‘Act as part of the operating system’. The Network Service that represents the identity of the SAML Bridge Application Pool must now be configured to act as part of the operating system, if it is not already configured that way.
In some environments, you cannot configure a host individually, because the domain controller sets security settings for all hosts in the domain. If your environment is set up that way, you’ll need to get access to the domain controller or ask the administrator to perform this configuration.
If you can configure the SAML Bridge host, follow these steps:
- Select Control Panel > Administrative Tools > Local Security Settings.
- In the left panel, select Security Settings > Local Policies > User Rights Assignment.
- Open Act as part of operating system.
- In the Act as part of the operating system Properties dialog box, click Add User or Group.
- In the Add User or Group dialog box, enter Network Service and click OK. The Act as part of the operating system Properties dialog box reappears, with Network Service in the box.
- Click OK to close the Properties dialog box.
Once the prerequisites are met, refer to the steps for Installing SAML Bridge.
To configure the search appliance to use SAML Bridge for authorization, add a SAML rule for a URL pattern that the search appliance can use to send a SAML authorization request to the Policy Decision Point.
To configure the search appliance to use SAML for authorization:
- In the search appliance Admin Console, click Search > Secure Search > Flexible Authorization.
- Choose SAML from the pull-down menu, and click Add another rule. The Add Flexible Authorization Rule page appears.
- In the URL Pattern field, type the URL pattern identifying the protected content.
- Select an Authentication ID from the pull-down menu or accept the default credential group. By selecting the Authentication ID, you are instructing the authorization mechanism to use a session identity from a specific credential group or instance of an authentication mechanism.
- If you want to override the default value of 3 seconds for making a network connection, enter the time in seconds in the Timeout field.
- In the Authorization service ID field, enter the Entity ID of the SAML server.
- In the Authorization service URL field, enter:
- Check Use batched SAML AuthZ requests to send multiple URLs for authorization in a single AuthZ HTTP request for improved serve time performance (recommended).
- Click Save.
- On the Flexible Authorization page, select the added rule and click Move Up to move it ahead of the HEADREQUEST rule. This causes the SAML rule to take precedence over the HEADREQUEST rule.
- Click Save Rules Order.
Continue to Completing the Configuration Process.
This section contains some troubleshooting tips that apply to authorization. For general tips to narrow your problem, refer to Troubleshooting SAML Bridge for Authentication. For more troubleshooting steps, visit the SAML Bridge wiki (http://code.google.com/p/google-saml-bridge-for-windows/wiki/SAMLBridgeFAQsTroubleshooting).
Authorization Testing Results in Indeterminate Status
When you run an authorization test, the permit code ‘Indeterminate’ appears and the following messages appear in the
3/13/2007 5:17:59 PM, GetPermission: after WindowsIdentity 3/13/2007 5:17:59 PM, GetPermission: AuthImpl::caught exception 3/13/2007 5:17:59 PM, GetPermission: Either a required impersonation level was not provided, or the provided impersonation level is invalid.
This error indicates that the host on which SAML Bridge resides might have an incompatible version of the .NET framework. Refer to the section Prerequisites for Using SAML Bridge for the correct version.
If you’ve checked the .NET version and determined that it meets the requirements, you can reconfigure the .NET framework for IIS as follows:
When your IIS server is reconfigured to use the specified version of .NET, the following message displays:
Finished installing ASP.NET (2.0.50727).
The log file lists a 401 error (unauthorized):
1/4/2007 9:14:19 AM, GetURL: GetURL =http://host.domain.domain.com:82/deny.html 1/4/2007 9:14:19 AM, GetURL: inside GetURL internal 1/4/2007 9:14:19 AM, GetURL: Sending a Head request to target URL 1/4/2007 9:14:19 AM, GetPermission: AuthImpl::caught WebException 1/4/2007 9:14:19 AM, GetPermission: e = System.Net.WebException: The remote server returned an error: (401) Unauthorized. at System.Net.HttpWebRequest.CheckFinalStatus() at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult) at System.Net.HttpWebRequest.GetResponse() at SAMLServices.Common.GetURL(String url, ICredentials cred) at SAMLServices.Common.GetURL(String url) at SAMLServices.Wia.AuthImpl.GetPermission(String url, String subject)
This problem indicates a Kerberos configuration error. Check that Kerberos is properly configured, following steps in Content Server Kerberos Prerequisites.
To uninstall the SAML Bridge:
- Navigate to SAML Bridge for Windows Installer 4.1.3 in the Shortcut Panel.
- Click Uninstall SAMLBridge for Windows.
The SAML Bridge for Windows page appears.
- Click Next and Remove.
Files are uninstalled.
- Click Done.