Hot answers tagged security
3
Users who are added as Site Collection Administrators are added in one of two ways:
1) They are the Owner or Secondary Owner on the Site Collection. You can set those from Central Administration or PowerShell.
2) They are added by going to the Site Collection Administrators button on the ribbon when viewing the Permissions page on the Root Web of the Site ...
3
You can use Sharepoint Client Object Model for this. Here is how to do it on the current web:
function CheckPermissionOnWeb()
{
context = new SP.ClientContext.get_current();
web = context.get_web();
this._currentUser = web.get_currentUser();
context.load(this._currentUser);
context.load(web,'EffectiveBasePermissions');
...
2
The TechNet article for security hardening is pretty good: http://technet.microsoft.com/en-us/library/cc262849(v=office.14).aspx
You definitely want to make sure that the service accounts are setup properly. Here is the guideance on service accounts: http://technet.microsoft.com/en-us/library/cc263445(v=office.14).aspx
If the system is setup for access ...
2
Your site collection admins will be able to do anything and everything that SharePoint allows, including the creation of SP groups. You can turn this off at the web application level, but it doesn't sound like that's something you want to do to all of your other site collections. I think the basic issue you're running into here is that anything you set at ...
2
The easiest way to check is to pull up the UIL directly, /_catalogs/users/simple.aspx. Editing this view will show you all the data available.
To answer your question, yes it includes Display Name (Name), Login Name (Account), and Email Address (Work Email) fields. SID is only within the User profile service I believe and not the UIL.
2
The right way to grant access is to use the SPWebApplication.GrantAccessToProcessIdentity method. It sets up the database permissions for you, but remember to run it again if you add content databases.
You can do this with the following PowerShell:
$webApp = Get-SPWebApplication TEAM_SITE_URL
$webApp.GrantAccessToProcessIdentity("domain\username of MY SITE ...
1
The issue here is that Sharepoint 2013 uses Claims based authentication, as opposed to 2007.
You would have to first convert your 2007 envirionment to using claims, before migrating to 2013.
Here is a guide from Technet about how to convert a 2010 (yes, not 2007) webapplication to claims, and then migrate to 2013.
The problem I guess is how you should do ...
1
New groups are created in Site Settings and can then be applied to the page.
Permissions inheritance is just that, it inherits from a parent. For a page, that parent is either a folder or the document library itself. Breaking the permissions inheritance means you need custom permissions on something that is different from the parent and therefore will have ...
Only top voted, non community-wiki answers of a minimum length are eligible
