S
SR
I have built a custom report for Project Server that uses the Project
Data Service (PDS) web service to get its data. The report is
accessible by a custom link in Project Web Access (PWA). PWA and PDS
are one separate servers. My custom report has its own virtual
directory on the same server as PWA. The problem is a matter of
authentication. When a user clicks the link in PWA to get to my
custom report, PDS returns a login error. It appears that the
Identity of the user is lost when accessing PDS when using integrated
security. I believe this is due to the fact that PDS is on a separate
server from my report. The user is authenticated by integrated
security when they access PWA and their identity is established. The
identity is still retained as far as the custom report is concerned.
It is when the custom report accesses PDS that the identity of the
user is lost for purposes of data retrieval from PDS. How can I
retain the identity of the user across machine boundaries so I can
still use integrated security to access PDS? This is particularly
important because PDS uses the identity of the user to filter data
appropriately. I can't really switch to basic authentication just for
accessing PDS because I don't know user passwords and therefore cannot
log in to PDS using their credentials. Naturally, I'm trying to avoid
prompting the user for credentials. This worked fine in my
development environment when every thing was setup on a single
machine. It is the production deployment that is presenting the
problems.
Your help and advice is much appreciated.
S. Robertson
Data Service (PDS) web service to get its data. The report is
accessible by a custom link in Project Web Access (PWA). PWA and PDS
are one separate servers. My custom report has its own virtual
directory on the same server as PWA. The problem is a matter of
authentication. When a user clicks the link in PWA to get to my
custom report, PDS returns a login error. It appears that the
Identity of the user is lost when accessing PDS when using integrated
security. I believe this is due to the fact that PDS is on a separate
server from my report. The user is authenticated by integrated
security when they access PWA and their identity is established. The
identity is still retained as far as the custom report is concerned.
It is when the custom report accesses PDS that the identity of the
user is lost for purposes of data retrieval from PDS. How can I
retain the identity of the user across machine boundaries so I can
still use integrated security to access PDS? This is particularly
important because PDS uses the identity of the user to filter data
appropriately. I can't really switch to basic authentication just for
accessing PDS because I don't know user passwords and therefore cannot
log in to PDS using their credentials. Naturally, I'm trying to avoid
prompting the user for credentials. This worked fine in my
development environment when every thing was setup on a single
machine. It is the production deployment that is presenting the
problems.
Your help and advice is much appreciated.
S. Robertson