04.12.2012 Views

Windchill System Administrator's Guide

Windchill System Administrator's Guide

Windchill System Administrator's Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Server Codebase Property<br />

Using HTTPS Protocol<br />

The server codebase property, wt.server.codebase, specifies the URL to the<br />

<strong>Windchill</strong> codebase virtual directory used by <strong>Windchill</strong> servers when producing<br />

URLs to static files. Most often, the server codebase property is used in a<br />

tag within dynamic HTML pages. This allows relative HREFs to be<br />

used within the page for static resources, such as style sheets and images. It is also<br />

used by client-side Java code to access files from the server's codebase, such as<br />

wt.properties or JAR files.<br />

All files in the <strong>Windchill</strong> codebase virtual directory can be available<br />

anonymously, except JSPs. This is because the dynamic nature of the JSPs<br />

typically requires that most pages are unique to a particular user.<br />

When standalone Java applications are run outside of a browser, some files in the<br />

server codebase must be available anonymously because the HTTP protocol<br />

handler in the standard Java Runtime Environment, does not support<br />

authentication challenges. These files include wt.properties and JAR files.<br />

HTTPS is the HTTP protocol layered over the Secure Socket Layer (SSL)<br />

protocol to allow secure data transfer using encrypted data streams. This section<br />

describes the <strong>Windchill</strong> configuration necessary. It assumes the web server has<br />

been set up for HTTPS. See your web server documentation for details on this<br />

procedure. RMI is not encrypted, but may be tunneled over HTTPS. See RMIover-HTTP<br />

for more information.<br />

The Java 2 platform does not include default support for HTTPS until version 1.4.<br />

The Java Secure Socket Extension (JSSE) enables secure communication,<br />

including HTTPS. To install this extension into a pre-1.4 Java runtime:<br />

1. Install the JSSE JAR files. Copy jsse.jar, jnet.jar, and jcert.jar from<br />

/lib to /lib/ext<br />

2. Add the JSSE provider to your list of approved security providers. Edit<br />

/lib/security/java.security to contain<br />

security.provider.n=com.sun.net.ssl.internal.ssl.Provider where n is the next<br />

provider preference available.<br />

Add an HTTPS protocol handler to the runtime. <strong>Windchill</strong> servers have this<br />

set by default, so no action is needed there. Any java application, including<br />

the servlet engine process, that creates URL objects with an HTTPS protocol<br />

will need to set a system property on the command line.<br />

<strong>Windchill</strong> includes a HTTPS protocol handler via the HTTPClient package.<br />

To use, specify "-Djava.protocol.handler.pkgs=HTTPClient".<br />

Alternatively, the JSSE includes a handler. To use it, specify:<br />

"-Djava.protocol.handler.pkgs=com.sun.net.ssl.internal.www.protocol"<br />

<strong>Windchill</strong> Considerations for Security Infrastructures B-5

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!