More Impersonation Problems

S

Simon Taylor

I solved my previous problem by using default credentials to logon to project server rather than specifying them using a NetworkCredential object. I also had to follow the steps in 1b of http://msdn.microsoft.com/en-us/library/bb428835.aspx, add the user I was logging in as, as a Farm administrator and restart IIS.

Everything is now working fine in my dev and qa environments, but I'm having problems when the application is deployed to the clients site.

To rule out my code being the problem, I have tried downloading the ProjTool sample application from Microsoft and running that on the clients machine - I get the same problem: 401 Unauthorized.

AT the office, project server is installed on a single server, however my client has project server installed on a web farm consisting of 4 servers:

APP-1: Runs as a MOSS application server. Performs indexing on content for the MOSS search functionality and runs the project server application. The MOSS administration sites are hosted on this server 0 central administration and shared services provider administration

APP-2: Runs as a MOSS web front end server. This is the machine that serves all web content on MOSS. This server also runs a number of other separate applications.

SQL-2: Runs a SQL Server 2008 Database. This contains all the MOSS search, config shared service provider and content databases. It also hosts databases for some other separate applications.

SQL-3: Runs a sql server 2008 reporting services instance. This is not currently running in sharepoint integrated mode. The reporting side of things is currently under development.

I have run through the instructions at http://msdn.microsoft.com/en-us/library/bb428835.aspx on both application servers and restarted both instances of IIS.

I want to be able to connectot http://APP-2/projectweb/_vti_bin/psi/Project.asmx as an impersonated user.

I haven't tried editing the proj tool code, but I have configured my code to use http://APP-1:56737/SharedServices1/psi/Project.asmx and http://APP-2:56737/psi/Project.asmx to perform the impersonation. I get the 401 error using both urls.

The fact that everything is working fine in my dev and qa environments (which are a considerably simpler installation) suggests to me that I am just missing a setting or I'm pointing my application at the wrong endpoint - I just don't know what.

Any help would be extremely greatfully received.




Posted as a reply to:

Same impersonation problem

Have you had any luck with this?

I am having the exact same problem. It seems to me that you can only perform impersonation if you are running as the user set up as the adminsitrator of the SSP, despite plenty of posts suggesting that this shouldn't be the case. Have you come to this conclusion or is there anyone else who can confirm this?

Thanks

EggHeadCafe - Software Developer Portal of Choice
WCF Workflow Services Using External Data Exchange
http://www.eggheadcafe.com/tutorial...a-6dafb17b6d74/wcf-workflow-services-usi.aspx
 
R

Ray McCoppin

I have seen this problem before. In enviroments where there are multiple Web
and App servers. The problem is that project server load balances the calls
to the APP servers from the web servers, and the credentials are not passed
because the http headers are changed when using impersonation. To solve this
you can try using localhost or 127.0.0.1 instead of the APP server name this
assumes that you are running both web and app servers on the project server
hardware. Or try a entry in the host file for the app server and making sure
that local addresses bypass proxy.

Hope this helps
--
Ray McCoppin

http://www.randsmanagement.com
Project Server 2007 Automation Web Service
Project Server 2007 Archive Tool
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top