Please Help - Virtual Path of WorkSite

Hello all,
I have setup everything on my .net web application to work with WorkSite (Web Control). But the biggest problem I encountered is, I have my web app sitting under IIS under a web site and the worksite virtual path sitting under a different web site - default (both on same m/c)

When I go to the page, the web control resolves the url path by getting the virtual path - which in my case is getting the path of the parent:
web app: http://mywebapp/home.aspx
worksite web control url is resolving to: http://mywebcontrol/worksite/portal.aspx.... (instead of http://mycomputer/worksite/portal.aspx....)

how/where can I change this setting, I tried to hard-code the virtual paths in the utilities.js file which reads the path from a cookie - no luck. I cannot change the worksite virtual path to my web application's web site since it has a host header file (www.xyz.com..)

this is really a pressgin issue and I am pulling my hair to find a solution. any help greatly greatly appreciated.

thanks much.

Find more posts tagged with

Comments

das

an extra note to my question:

If I am inside the companies network I can access the worksite web control without any problem, but if this page is accessed from outside then I get a popup prompt asking for a user/pswd, I then have to enter my network credentials. Is there a way to by pass this?
I gave anonymus access to the worksite virtual path, gave full access to asp.net user and IUSR of my machine.
Is there a setting in options.xml that I can use to allow outside public access?

any help will be really helpful.

dabird

This reply is from our in-house SharePoint expert:

"We recommend the WSW to be on same server as WebControl, otherwise you run into cross-site scripting issue. You could in theory run both app on separate machine as long as your main domain is same (i.e. app.domain.com and worksite.domain.com) to avoid the cross-site scripting issue. For later case, you need to modify the virtualPath() and you need to set document.domain = "domain.com" in any one of the JS files)

Other simpler approach is render our control in <iframe>. This way you won't run into any cross-site scripting issue."

dabird

The web control has been designed using auto trusted login. To circumvent this, you would have to modify the authentication process in WorkSite for SharePoint. First you would have to enable impersonation on your DMS. Next you would have to set the impersonation password in WS for SP using a utility that is shipped with WS for SP. Lastly you would have to modify the authentication procedure to login as a virtual user using the impersonation password. We have a recorded webcast that explains how to create a custom authentication module @ http://devnet.interwoven.com/site.fcgi/webcasts/docs/webcast-recordings.html. It's entitled "Creating a Custom Authentication Module for WorkSite Web 8.1".

You will need source code from IWOV for this, so you need to send a request to worksite-devsupport@interwoven.com. When you send your request, you need to include the following information:

your company name
if you're a partner, include the company for whom you are providing the customization
a brief synopsis of what you are trying to accomplish

The management team reviews and grants requests for the source code on a case-by-case basis. Incomplete email requests will delay processing.

das

Great, We sill send out a request if we need the source code.

But the iFrame seems promising. Thanks a lot!