IT tutorials
 
Applications Server
 

Distributing Sharepoint 2013 Apps : Publishing Apps in the SharePoint Store (part 1) - Creating a Client ID and Secret

2/28/2014 3:27:54 AM
- Free product key for windows 10
- Free Product Key for Microsoft office 365
- Malwarebytes Premium 3.7.1 Serial Keys (LifeTime) 2019

When you have completed developing your app and are ready to publish the next thing you need to do is to sign up and get access to the Seller Dashboard. The Seller Dashboard is the back-end entry point for developers and ISVs to access the SharePoint Store. It’s where you can submit, publish, and manage your apps.

To apply for access you simply create an account with Microsoft on the website at: http://sellerdashboard.microsoft.com. You must sign in with a Microsoft account and answer some questions about yourself or the company you are registering. After you’re registered you receive access to the Seller Dashboard. However, this access doesn’t let you start publishing applications immediately. Microsoft conducts a verification process to ensure you are who you say you are and that you have completed the information sufficiently. You will be notified when this process is complete via e-mail.

After you successfully log in to the Store, you will see the Seller Dashboard, as shown in Figure 1.

FIGURE 1

image

WARNING At the time of this writing only SharePoint-hosted and Provider-hosted app types are supported in the SharePoint Store. Microsoft has indicated this restriction will be lifted at a later date after the new SharePoint Online is out of preview. This means Autohosted apps are not currently allowed to be submitted to the store for publication.

You are now ready to start submitting apps. The two high-level steps in this process are:

1. Creating a client ID
2. Submitting an app package

Creating a Client ID and Secret

A client ID and client secret form a critical component of how the OAuth authentication and authorization flows work between apps and SharePoint. They are used to secure and verify calls as well as identify apps when calls are made.

For Provider-hosted apps you are required to apply for a client ID and secret prior to submitting the app. This is because you need to both supply them as part of the app package and, more importantly, you need to configure them in your app’s back-end code. The back-end code of your application must be up and running prior to submission so that Microsoft can successfully test the application and verify it.

When you’re creating private apps, you create a client ID and secret through the appregnew.aspx page . For apps you want to distribute through the SharePoint Store, you need to obtain the client ID and secret from the Seller Dashboard. This is a straightforward process (as shown in the following Try It Out) and requires you to supply a friendly name, the domain name on which the app code back end will be hosted, and the period for which the ID/secret should be valid for.


Creating a New Client ID through the Seller Dashboard

In this example you create a new client ID and secret combination using the Seller Dashboard. You first need a Seller Dashboard account to get these items.
1. Log in to the Seller Dashboard on the http://sellerdashboard.microsoft.com website.
2. Click the Client IDs link.
3. Click the Add a new oauth client id link as shown in Figure 2.

FIGURE 2

image

4. Enter a friendly name for the client ID; for example, MyAppKeys.

5. In the App Domain field enter the domain name of where your Provider-hosted application code resides; for example, myapp.contoso.com.

6. In the App Redirect URL field enter the fully qualified domain name and path to the redirect URL page in your app code. This field accepts authorization codes from SharePoint . Note that it must be HTTPS; for example, https://myapp.contoso.com/redirecturi.aspx.

7. Pick the duration you want the client ID and secret to be valid for. The default is one year.

8. After it’s complete, the form should look like the one shown in Figure 3.

FIGURE 3

image
9. Click the Generate Client ID button. A confirmation screen with your client ID and secret appears, as shown in Figure 4.

FIGURE 4

image

10. Make a copy of this page and store these details somewhere safe. This is very important! No way exists to retrieve them again after you have dismissed this screen.

11. After you have made a safe and secure copy of the details shown, click Done.

12. You can now configure your Provider-hosted app with the client ID and secret combination you generated.

How It Works

In this exercise you created a new client ID and secret through the Seller Dashboard. In the background the Seller Dashboard keeps a record of the combination for use when your app code talks to SharePoint. You need to manually create a combination for Provider-hosted apps because you need to manually set them in your app code project. For SharePoint-hosted and Autohosted apps, the client ID and secret are created automatically upon installation and you never need to worry about them.
 
Others
 
- Exchange Server 2013 administration overview : Using Exchange Management Shell
- Exchange Server 2013 administration overview : Using the graphical administration tools
- Exchange Server 2013 administration overview : Exchange Server and Active Directory, Exchange Online and Office 365
- Exchange Server 2013 administration overview : Exchange Server and Windows
- Exchange Server 2013 administration overview : Exchange Server 2013 editions
- Exchange Server 2013 administration overview : Exchange Server 2013 and your hardware
- Exchange Server 2013 administration overview : Getting started with Exchange 2013 and Exchange Online
- Microsoft Lync Server 2013 Monitoring and Archiving : Archiving Configuration (part 2) - Using Cmdlets for Configuration Tasks
- Microsoft Lync Server 2013 Monitoring and Archiving : Archiving Configuration (part 1) - Creating Site and User Policies
- Microsoft Lync Server 2013 Monitoring and Archiving : Monitoring Components Installation (part 2) - Monitoring Administration
 
 
Top 10
 
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 2) - Wireframes,Legends
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 1) - Swimlanes
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Formatting and sizing lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Adding shapes to lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Sizing containers
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 3) - The Other Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 2) - The Data Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 1) - The Format Properties of a Control
- Microsoft Access 2010 : Form Properties and Why Should You Use Them - Working with the Properties Window
- Microsoft Visio 2013 : Using the Organization Chart Wizard with new data
Technology FAQ
- Is possible to just to use a wireless router to extend wireless access to wireless access points?
- Ruby - Insert Struct to MySql
- how to find my Symantec pcAnywhere serial number
- About direct X / Open GL issue
- How to determine eclipse version?
- What SAN cert Exchange 2010 for UM, OA?
- How do I populate a SQL Express table from Excel file?
- code for express check out with Paypal.
- Problem with Templated User Control
- ShellExecute SW_HIDE
programming4us programming4us