Issue Linking / Welcome Page

[Brian Harris]

Hi all. I've tried searching myself, but I think I'm winding myself in too
many directions. I'm hoping there is a fairly easy answer here, so thanks in
advance for any help!!

I have Project Server 2003 setup and all is working well with the exception
of Project and user specific issues linking and showing up on a user's
Project Welcome page. The sharepoint services work - for example, when a
user clicks on issues it prompts them for the windows authentication and then
takes them to the proper list. I'm guessing it's because security rights are
somehow not being synchronized with windows user accounts? Is there a
document explaining this process in a bit more detail? (I did just downloafd
the 5Mb Admin guide, so I'll start reading that nightly)

Thanks again!!

 

[Gary L. Chefetz [MVP]]

Brian:

If users are receiving a logon challenge from the server when selecting
issues, risks and documents, your system is not setup correctly.

Further, you should understand that users must have access to the issues and
risks to which they are assigned. It's quite possible to assign an issue to
a user who does not have an assignment in the Project, in which case they'll
be assigned to a risk or issue that they don't have access to see. In this
case, the issue or risk will not be visible on the home page. When you
assign a risk or issue to a person who is not already assigned to a task in
a project, you should add a task for that resource to the project plan and
publish it.

 

[Brian Harris]

I was afraid as much. What I guess I need to read up on (and am beginning
to) is the security portion of Project Server. Right now I have everyone
setup using Project Server authentication, but it looks as if I need to
change this to Windows accounts?

The Sharepoint site uses Windows accounts, so is there a way to synchronize
these users with Project Server users - or add them to an appropriate users
group?

Thanks for the help!
--
Brian Harris
IT Director
MHO Solutions, LLC
www.mhosolutions.com

 

[Gary L. Chefetz [MVP]]

Brian:

In order to use any of the features provided by WSS, your users must have
Windows Accounts. Changing accounts from Project Server authentication to
Windows auth in Project Server is as easy as adding the logon information to
the resource record.

 

[Brian Harris]

Gary,

This is helping a lot. Letme give you some background as to what w are
trying to do. We have two partner companies that we are trying to work with
on a project and we have installed this on a non-domain server and created
local accounts for all WSS sites. I was hoping that I would be able to use
these same local accounts for Project Server auth. so that we could have our
external partners use these accounts without having to integrate into our
domain. I was thinking this gives us some flexibility to add/remove external
partners outside of our internal security process.

It looks like I might be wrong, and in order to use Windows accoutn auth, I
actually have to synch or use accounts that the users are logging into their
workstations with?

And if I understand you correctly, if we have to use Project Server
accounts, the users will never have issues/risks from WSS but rather have to
use WSS seperately.

Thanks again for sticking with me!!
--
Brian Harris
IT Director
MHO Solutions, LLC
www.mhosolutions.com

 

[Gary L. Chefetz [MVP]]

Brian:

If implementing this myself, I'd opt for two front ends: 1) internal facing
2) external facing. While I prefer to use domain authentication all the way,
I suppose you could use local Windows logons for your external users, but
best practice dictates domain auth.