In the Filter Name field, enter osso for the filter name.

A-24 Oracle Fusion Middleware Administrators Guide for Oracle HTTP Server a. In Windows Explorer, right-click the ORACLE_HOME\bin folder, select Properties from the menu, and then click the Security tab. b. Add the IIS_WPG, NETWORK and NETWORK SERVICE groups with Read and Execute permissions.

c. Click OK.

4. Restart the Microsoft IIS server by opening the Services Control Panel, and then stopping and restarting the World Wide Web Publishing Service. A.2.8 Troubleshooting Oracle SSO Plug-In This section describes common problems and solutions. Oracle Dependency Libraries Not Found You may not have included ORACLE_HOME in your path. Solution Check to see that you have ORACLE_HOMElib included in your library path variable on UNIX. On Microsoft Windows, ensure that you have ORACLE_HOME\bin in your path. If you continue to recieve this message in your osso.log file, then verify that all configuration files are properly configured, as described in Section A.2.5, Configuring Sun Java System Listener for Single Sign-on . Microsoft IIS Oracle SSO Plug-In Does not Work with HTML Authentication The Oracle SSO Plug-In is designed not to work with other authentication modules. Authentication is either a native listener authentication module or a third-party module. Notes: ■ To restart Microsoft IIS 7.0, you must stop all the Microsoft IIS 7.0 services through the Services Control Panel or restart the computer. This is the only way to ensure that the .dll file is reloaded. Restarting Microsoft IIS 7.0 through the management console is not sufficient. ■ If you want multiple Oracle installations on the same home, then the ORACLE_HOME\bin PATH entry for the installation that you plan to use in conjunction with the Oracle SSO Plug-In must appear first in your PATH. B Frequently Asked Questions B-1 B Frequently Asked Questions This appendix provides answers to frequently asked questions about Oracle HTTP Server. Documentation from the Apache Software Foundation is referenced when applicable. B.1 How Do I Create Application-Specific Error Pages? Oracle HTTP Server has a default content handler for dealing with errors. You can use the ErrorDocument directive to override the defaults. B.2 What Type of Virtual Hosts Are Supported for HTTP and HTTPS? For HTTP, Oracle HTTP Server supports both name-based and IP-based virtual hosts. Name-based virtual hosts are virtual hosts that share a common listening address IP plus port combination, but route requests based on a match between the Host header sent by the client and the ServerName directive set within the VirtualHost. IP-based virtual hosts are virtual hosts that have distinct listening addresses. IP-based virtual hosts route requests based on the address they were received on. For HTTPS, only IP-based virtual hosts are possible with Oracle HTTP Server. This is because for name-based virtual hosts, the request must be read and inspected to determine which virtual host is used to process the request. If HTTPS is used, an SSL handshake must be performed before the request can be read. In order to perform the SSL handshake, a server certificate must be provided. In order to have a meaningful server certificate, the hostname in the certificate must match the hostname the client requested, which implies a unique server certificate per virtual host. However, because the server cannot know which virtual host to route the request to until it has read the request, and it cant properly read the request unless it knows which server certificate to provide, there is no way to make name-based virtual hosting work with HTTPS. Note: Readers using this guide in PDF or hard copy formats will be unable to access third-party documentation, which Oracle provides in HTML format only. To access the third-party documentation referenced in this guide, use the HTML version of this guide and click the hyperlinks. See Also: ErrorDocument directive in the Apache Server documentation