Five pieces of information are needed to register an app
principal used by a cloud-hosted SharePoint app. Navigate to http://<SharePointWebsite>/_layouts/15/AppRegNew.aspx on the farm then:
ClientID – identifying GUID for the app. Example: b044e104-7de2-4a05-aacf-63119009c55e
Client Secret – base64 encoded string which encrypts and
decrypts messages between Windows Azure Access Control Service (ACS). Example: xyZpG0AgVIJfch6ldu4dLUlcZyysmGqBRbpFDu6AfJq=.
Title – caption that appears for a registered app principal.
Example: KMO Video Uploader
App URI – base URL used to access the cloud-hosted app. Example:
www.kmo.name
Redirect URL – optional items for a landing page SharePoint
can use for additional requests (example a callback to another site for
information the app was need). Must use https:// Example: https://www.kmo.name/RedirectAccept.aspx
The following are some quick bullet points that review OAuth:
OAuth – Internet protocol for authenticating apps and
authorizing such apps – to access content on behalf of a specific user.
OAuth – allows SharePoint 2013 and greater versions to
typically authenticate a cloud hosted app – which is calling to a SharePoint
site – from across a network and to establish an identity for the app.
SharePoint 2013 and greater use OAuth to authenticate apps
and establish app identity.
Windows Azure Access Control Services (SCS) is a requirement
for using OAuth.
The following are some core
SharePoint root directories – these are common directories on a web front end
and typically what type of files they contain in them:
C:\Programs Files\Common
Files\Microsoft Shared\Web Server Extensions\
Then the last directory will be as
follows – depending on the SharePoint version utilized:
14 = SharePoint 2010
15 = SharePoint 2013
16 = SharePoint 2016
The following are the common
directories then the types of files in them:
/ISAPI – Web Services (*.svc,
*.ashx and *.asmx)
/Resources – Resource files (*.resx)
/TEMPLATE/ADMIN – Application pages
used in central administration
Governing the information architecture is a key to the
successful use of SharePoint Server and requires the participation of business
managers, content managers, information workers, site designers, and IT
professionals.
Defining information-governance plans requires an
understanding of the site topology, the purpose of each offering (example Intranet,
Extranet, OneDrive etc.), and preferably a knowledge of future planned offerings,
such as business intelligence.
Information policies need to be defined for each site within
the SharePoint deployment. A policy needs to be defined per topic area for each
site offering.
