Partner Center SDK for .NET Samples

Overview

Console application that demonstrates each scenario the Partner Center SDK for .NET is capable of performing.

Getting Started

Before you build the application, update the values in the App.config file to reflect the Azure AD authentication information you created in Partner Center authentication. Specifically, you should use your integration sandbox account settings during early development or for testing in production.

Under ScenarioSettings in the App.config file, you can set parameters that will be automatically passed into the scenarios that you run.

To modify the list of scenarios that are run, comment out lines in MainScenarios or in an individual Get Scenarios method found in the Program.cs file.

Prerequisites

With previous versions of this sample there were configurations for user credentials. Those configurations have been removed, and now you will be prompted to enter the credentials upon execution. This change was made due to the upcoming requirement to use multi-factor authentication (MFA) when access Partner Center and the Partner Center API using app + user authentication. Please note that the approach used by this application to obtain user credentials is just one way this operation can be performed. It is recommended that you review the Secure App Model sample for more information.

Azure Active Directory

Perform the following task to correctly configure the Azure AD application for use with this sample project.

Sign in to the Partner Center using credentials that have Admin Agent and Global Admin privileges
Click on Dashboard at the top of the page, then click on the cog icon in the upper right, and then click the Partner settings.
Add a new native application if one does not exist already.
Sign in to the Azure management portal using the same credentials from step 1.
Click on the Azure Active Directory icon in the toolbar.
Click App registrations -> Select All apps from the drop down -> Click on the application created in step 3.
Click Authentication from left menu blade and then click Add Platform
In the Right popup blade, Click on Mobile and Desktop Applications
Select https://login.microsoftonline.com/common/oauth2/nativeclient as one of the available Redirect URIs ( You need to add a custom redirectUri too. Add http://localhost but we will be using the one added earlier ).
Click Configure. Your set of redirect Uris will be added under Platform Mobile and Desktop Applications.
Be sure to click the Save button to ensure the changes are saved.

What to Change

PartnerServiceSettings

If you are connecting to one of the sovereign clouds you will need to modify the values below. These values should not be modified if you are connecting to the commercial cloud.

PartnerServiceApiEndpoint
AuthenticationAuthorityEndpoint
GraphEndpoint

All thees settings are necessary for the sample API calls to properly function.

AppAuthentication

The following settings must be modified, so that each scenario functions as excepted

ApplicationId: Your Azure Active Directory application identifier, used for authentication
ApplicationSecret: The application secret, associated with the specified Azure AD application
Domain: The Azure Active Directory domain where the Azure AD application was created

UserAuthentication

The following settings must be updated, so that each scenario functions as expected

ApplicationId: Your Azure Active Directory application identifier, used for authentication
Domain: The Azure Active Directory domain where the Azure AD application was created

Do not change the following configurations

RedirectUrl
ResourceUrl

ScenarioSettings

Do not change the following setting

CustomerDomainSuffix: The domain suffix used when creating a new customer

The following settings can be updated, if left blank information will need to be inputted when running a scenario where it is necessary

CustomerIdToDelete: The ID of the customer used for deletion.
DefaultCustomerId: The customer ID to use in customer-related scenarios.
DefaultInvoiceId: The invoice ID to use in invoice scenarios.
PartnerMpnId: The partner MPN ID to use in indirect partner scenarios.
DefaultServiceRequestId: The service request ID to use in service request scenarios.
DefaultOfferId: The offer ID to use in offer scenarios.
DefaultOrderId: The order ID to use in order scenarios.
DefaultSubscriptionId: The subscription ID to use in subscription scenarios.

Each of the following of settings specify the amount of entries per page when retrieving paged content. These settings can be modified if desired

CustomerPageSize
DefaultOfferPageSize
InvoicePageSize
ServiceRequestPageSize
SubscriptionPageSize

5.2 KiB Исходник Постоянная ссылка Ответственный История