SharePoint 2013 앱으로 얼마나 멀리 갈 수 있습니까?

Question

저는 SharePoint 2013의 새로운 것이며 5 년 전에 SharePoint 2007에서 짧은 기간 동안 만 일했습니다.

지금은 이제 익스트라 넷을 계획해야하며 SharePoint 2013을 기반으로 할 것입니다.

이미 새로운 클라우드 앱 모델에 대한 많은 정보를 읽었지 만 나는 앱으로 얼마나 멀리 갈 수 있는지 알아낼 수 없습니다.

응용 프로그램이 서버 측 오브젝트 모델에 액세스 할 수 없다는 것을 이해합니다.그러나 이것은 pratical 조건에서 무엇을 의미합니까?

예를 들어, 우리의 익스트라 넷은 다른 유형의 사용자가 액세스하고 볼 수있는 메뉴에 몇 개의 사용자 정의 섹션을 갖게됩니다.그리고 그의 기관에서의 인물을 결정하는 전력 사용자는 어떤 섹션을 볼 수 있습니다.

이것은 볼 수있는 것처럼 상당히 복잡합니다.이 경우에 앱을 만들 수 있습니까?또는 액세스 할 수없는 사용자 목록에 액세스하고 팜 솔루션이어야합니까?

Answer 1

how long is a pice of string? ;)

only joking, its a vauge question so im going to try to answer without being so vauge!

Your talking about user/group policy:

•User-only policy—This user-only policy is the authorization policy that was always applied in SharePoint 2010. When the user-only policy is used, the authorization checks take into account only the user identity. An example of when this policy is enforced is when the user is accessing resources directly without using the app.

•User + app policy—When the user + app policy is used, the authorization checks take into account both the user identity and the app identity. In particular, when this policy is used, authorization checks succeed only if both the current user and the app have sufficient permissions to perform the action in question.

An example of when this policy is used is when a SharePoint site has an embedded IFRAME that links to a Office Store app, and the app calls back to SharePoint to access SharePoint resources on behalf of the user. That is, when a Office Store app, which does not run in SharePoint Server, wants to act on behalf of the user to get access to the user's resources.

•App-only policy—When the app-only policy is used, the content database authorization checks take into account only the app identity. In particular, when this policy is used, an authorization check succeeds only if the current app has sufficient permissions to perform the action in question, regardless of the permissions of the current user (if any).

An example of when this policy is enforced is when the app is not acting on behalf of the user. An example of an app that might use this app-only policy is an expense submission app.

In the app-only policy app type, the person who installs the app (for example, a human resources manager) has the rights that the app needs, even though users who actually use the app might not have those rights.

For example, the person who installs the app allows the app to approve an expense submission that is equal to or less than $50, even though the users who submit the expense have no rights or authority to approve it. And, if the expense is more than $50, the app routes it to the appropriate manager for approval.

http://msdn.microsoft.com/en-us/library/fp179892.aspx

and also app permissions is i think what your also refering too:

SharePoint 2013 apps provide a wide variety of powerful tools and enhanced functionality that can increase the usefulness of your SharePoint 2013 deployment. When you decide to support the implementation of SharePoint 2013 apps within your deployment, you need to determine who will be installing the apps and who will be using them. You also need to determine the appropriate scope and permission levels for each app, based on how the app is intended to be used.

App permission request scopes

SharePoint 2013 apps use app permission request scopes and permission requests to specify the level at which the app is intended to run, and the permission level that is assigned to the app. The app permission request scope indicates the location within the SharePoint 2013 hierarchy where a permission request will apply. SharePoint 2013 supports the following permission request scopes:

•SPSite Defines the app permission request scope as a SharePoint 2013 site collection.

•SPWeb Defines the app permission request scope as a SharePoint 2013 web site.

•SPList Defines the app permission request scope as a SharePoint 2013 list.

•Tenancy Defines the app permission request scope as a SharePoint 2013 tenancy.

If an app is granted permission to one scope, the permission also applies to the children of that scope. For example, if an app is granted permission to a web site by using the SPWeb scope, the app is also granted permission to each list (SPList scope) that is contained within the SPWeb scope and all list items within each list. Because permission requests are made without information about the topology of the site collection where the app is installed, the scope is expressed as a type rather than as the URL of a specific instance. These scope types are expressed as URIs. Content database related permissions are organized under this URI: http://sharepoint/content. The following table provides an URI example for each app permission request scope.

http://technet.microsoft.com/en-us/library/jj219576.aspx

I highly advise you to glance at:

for full understanding of apps in 2013

http://technet.microsoft.com/en-us/library/fp161230.aspx

and also

planning (stratergy) for apps in 2013

http://technet.microsoft.com/en-us/library/fp161237.aspx

What your refering to as complex is not really complex and is part of sharepoint standard practice, otherwise not many people would develop apps in the first place if there was no security involved!