This past year we upgraded out Windchill environment from V9.1 M060 to M10.2 M020. One of the features we had in our V9.1 environment was an external portal that the users entered with additional links and info. A portlet on certain pages of the external portal would list all of the documents in a specific Windchill folder. The code that created this portlet used a UrlConnection to run an InfoEngine task that did the query. To launch this InfoEngine task properly, the authorization header is used. We also have an action from the Windchill Quick Links menu that will launch this external portal in a new window. In V9, Windchill produced the authorization header (as seen from the launching jsp) and passed it to the external portal which in turn passed it back to Windchill with the UrlConnection. In V10, I am no longer seeing that authorization header when the jsp launches, and therefore the external portal is getting a AuthorizationException from Windchill when trying to connect with the UrlConnection. Our environment is HTTPS, but the communication between the external portal and Windchill is http on the backend. A little confusing, I know. The users come into Windchill or the portal using https://www...., but the portal communicates directly with Windchill via http://servername.... If the user comes into the portal directly, everything works just fine, but if they get to the portal by clicking on the action in Windchill, the error occurs.
My question is, what do I need to do to configure Windchill, in the HTTPS setting, to produce the authorization header like it used to? Any thoughts?
