Discussions
Categories
Groups
Community Home
Categories
INTERNAL ENABLEMENT
POPULAR
PUBLIC CLOUD
PRIVATE CLOUD
Quick Links
MY LINKS
HELPFUL TIPS
Back to website
Home
Web CMS (TeamSite)
IWOVServices and History entries
zephyr2000
Hi,
We have written some web pages that use IWOVServices to display a list of documents for a Client or Matter (CUSTOM1 or CUSTOM2).
It does this by calling the SearchDocuments method on the web service.
When the HTML is created to show the user the documents, this also includes a hyperlink to view the document.
When the user clicks the hyperlink, our web software then calls the GetDocuments method on the web service, and writes out the binary information for the document to the browser. This all works fine.
However, in Interwoven, opening the document writes out a history line for the document to say it has been opened.
For our web service calls to work (and not get an Unauthorized error) we have to specify the credentials for a particular user (either in the Impersonate line of the web.config for our web application, or hard coding the credentials when calling the web service).
This means that the history line is created with the User set to the user for the credentials the web service is being called under, and not the actual user that is using the web software and opening the document.
Is there any way to get the history line to show the user that is actually performing the Open action at the front end, and not the user that the web service is called under?
Or any way to be able to call the web service under the context of the front-end user?
Any ideas would be very much appreciated!
Chris
Find more posts tagged with
Comments
dabird
Inside WorkSite Web, the History logging only supports adding an entry for the currently logged-on user. There is no way to pass a user ID, either from web services or from within WorkSite Web.
If your web app is on the same physical machine as the IWOVServices, you should be able to get the token for the current user and login as that user via trusted login. If your web app is deployed to a different physical machine than the IWOVServices, then you're running into the classic "two-hop" or "double-hop" limitation of IIS.
wwest
If you use Kerberos authentication you can run under the credentials of the user at the browser, and also get around the double hop issue.
-w