B
Bay
My system admins set up our Project Server to automatically login
using our Windows credentials, which works great. From the browser, I
can switch to another user who happens to also be a PM, which also
works great.
But, if I am logged into that second user in PWA while still logged in
on the desktop as the first user, and I choose to Edit a project,
Project Pro comes up connected as the first user.
I might have expected PWA to send the logged in credentials to Project
Pro and get some sort of Profile connection dialog that states the two
profiles don't match (since the id/pass would not match). But, it
connects merrily and the second user ends up making changes to the
project under the first user's credentials.
It is an uncommon scenario, but has happened a few times in our labs
where PMs share an open desktop. Any thoughts as to how we might
force Project Pro to challenge for different credentials or simply
fail?
using our Windows credentials, which works great. From the browser, I
can switch to another user who happens to also be a PM, which also
works great.
But, if I am logged into that second user in PWA while still logged in
on the desktop as the first user, and I choose to Edit a project,
Project Pro comes up connected as the first user.
I might have expected PWA to send the logged in credentials to Project
Pro and get some sort of Profile connection dialog that states the two
profiles don't match (since the id/pass would not match). But, it
connects merrily and the second user ends up making changes to the
project under the first user's credentials.
It is an uncommon scenario, but has happened a few times in our labs
where PMs share an open desktop. Any thoughts as to how we might
force Project Pro to challenge for different credentials or simply
fail?