Authentication Configuration Tools
The tools included in the Windchill base product help identify user authentication configuration problems by exercising the authentication mechanism to verify that it is working and then reporting the user identities.
You can use the wt.auth.Authentication class as a tool for verifying user authentication within Windchill. This class includes a main method so that it can be run as a standalone application. It exercises the configured login scheme and reports the resulting authenticated user name as seen by the Windchill method server. The following is an example of output for a failed HTTP authentication (canceled login), followed by a successful Null authentication:
<HTML><HEAD>
<TITLE>401 Authorization Required</TITLE>
</HEAD><BODY>
<H1>Authorization Required</H1>
This server could not verify that you
are authorized to access the document
you requested. Either you supplied the wrong
credentials (e.g., bad password), or your
browser doesn't understand how to supply
the credentials required.<P>
</BODY></HTML>
HTTP Login failed: java.io.StreamCorruptedException:
InputStream does not contain a serialized object
Reading user.name system property
Authentication.getUserName() jhs
To test authentication from a browser, use the basic connectivity test page. Access the page by using the general URL logon format with the wtcore/test.html file:
http://<hostname>:<port>/<webapp>/wtcore/test.html
If you have set up HTTPS connectivity, you can specify https instead of http.
For example, to access the page using the local host, default port, and web application named Windchill, use the following:
http://localhost/Windchill/wtcore/test.html
From the basic connectivity test page, you can test anonymous and authenticated logons for the web server, servlet engine, and HTTP gateway servlets.
Was this helpful?