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.

The HTTP authentication implementation, described in more detail in the<br />

<strong>Windchill</strong> Application Developer’s <strong>Guide</strong>, results in the following <strong>Windchill</strong><br />

configuration requirements:<br />

1. Authenticated user names are Web server user names.<br />

2. <strong>Windchill</strong>'s authenticated HTTP gateway (defined by the<br />

wt.httpgw.url.authenticated property in the <strong>Windchill</strong> wt.properties file) must<br />

be subject to access control by the Web server, allowing only authenticated<br />

users to access it.<br />

3. On the Web server, the <strong>Windchill</strong> HTTP gateway URLs must be aliased to the<br />

provided <strong>Windchill</strong> gateway servlet implementations.<br />

<strong>Windchill</strong>'s internal access controls are applied through the <strong>Windchill</strong><br />

Administrator, as described in this guide. The <strong>Windchill</strong> Administrator<br />

application, in turn, associates each <strong>Windchill</strong> user ID with an authentication ID<br />

maintained by the Web server. The procedures that follow show you how to create<br />

user accounts and implement access controls for data residing on the file system:<br />

Note: In the wt.properties file, the property wt.auth.toLowerCase is set to true by<br />

default, which forces authentication IDs to become lowercase. Therefore, you<br />

should not rely upon case to distinguish user IDs, unless you have changed the<br />

value of this property to false.<br />

See the <strong>Windchill</strong> Application Developer’s <strong>Guide</strong> for information about<br />

customizing <strong>Windchill</strong>'s authentication mechanism. See the <strong>Windchill</strong> Installation<br />

and Configuration <strong>Guide</strong> for more information about specifying anonymous<br />

access.<br />

Troubleshooting User Authentication<br />

Two tools included in the <strong>Windchill</strong> base product help identify user authentication<br />

configuration problems by exercising the authentication mechanism to verify that<br />

it is working and then reporting the user identities.<br />

The wt.auth.Authentication class is the focal point for user authentication within<br />

<strong>Windchill</strong>. This class includes a main method so that it can be run as a stand-alone<br />

application. It exercises the configured login scheme and reports the resulting<br />

authenticated user name as seen by the <strong>Windchill</strong> method server. The following is<br />

an example of output for a failed HTTP authentication (canceled login), followed<br />

by a successful Null authentication:<br />

<br />

401 Authorization Required<br />

<br />

Authorization Required<br />

This server could not verify that you<br />

are authorized to access the document<br />

you requested. Either you supplied the wrong<br />

credentials (e.g., bad password), or your<br />

browser doesn't understand how to supply<br />

Administering Runtime Services 1-39

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

Saved successfully!

Ooh no, something went wrong!