Security in Project Server 2010–What about Custom Permissions?

SharePoint Server 2010 handles user authentication through claims processing, which is a new feature for SharePoint and Project Server. Although SharePoint handles both Windows authentication and Forms authentication for Project Server users, you can use the ReadResourceAuthorization and SetResourceAuthorization methods in the Resource service of the PSI to set authorization. Because you probably don’t often change security authorization settings for users, you would normally go to the Manage Users page in Project Web App to select a user and set the global and category permissions. The Security business object in Project Server (with programmatic access through the PSI Security service) manages security groups, categories, templates, and the global Project Web App permissions. The Security service can add existing permissions or remove permissions from the sets available for Project Server users. However, the Security service does not have a method for creating a custom permission. In Office Project Server 2007, you can create custom global and category permissions by modifying security tables in the Published database. The Walkthrough: Creating and Using Custom Project Server Permissions article is the only SDK example where an exception is made for changing the Published database. In Project Server 2010, that process for creating custom permissions is obsolete. As an alternative, it is possible to create custom permissions by using claims augmentation. For more information, see Claims Provider . NOTE:

Leave a comment!

You must be logged in to post a comment.