Getting a client ID and configuring your appBefore your app can begin to call the Live Connect APIs, you must configure your app with a unique identifier, which we call a client ID. For some app types, you must also configure your app with an associated password, which we call a client secret, and a redirect domain, which is a domain that the APIs use to exchange tokens, data, and messages with your app. To get a client ID—and to get a client secret and specify a redirect domain, if needed for your app type—here are your options.
| Anzeige |
You get a client ID and a client secret, and you can specify a redirect domain if needed, at the Live Connect app management site (or the Live Connect app management site for Metro style apps).
After you get a client ID, you may want to do one or more of these.
Follow these instructions to do these tasks.
Go to the Live Connect app management site for Metro style apps (https://manage.dev.live.com/build), and follow the on-screen directions.
Note Do not go to the Live Connect app management site at https://manage.dev.live.com. That site is not designed to create client IDs for Metro style apps.
Caution If your app is a Metro style app, don't follow these instructions, or else your client ID won't work. You must follow the instructions in the previous section instead.
You can swap your current client secret for a new client secret if you think your current client secret is compromised. Or, your organization may require you to change your client secret key periodically for security reasons.
Note Both the old and new client secrets will continue to work until you follow the next set of steps.
When you're ready to stop using the old client secret, do this:
Caution After you click Activate, the old client secret won't work anymore. This means that all copies of your app that rely on the old client secret won't work anymore, either.
After users sign in from your app to a service that is compatible with Live Connect, Live Connect displays the Allow access page (also called the consent page), which explains to the user the types of info that your app wants to access. (For more info about the consent page, see Obtaining user consent.) To customize the items in the consent page, you specify these settings for your app in the Live Connect app management site.
| Consent page | Live Connect app management site setting |
|---|---|
| 1. Your app's logo | Basic Information page, Application logo image |
| 2. Your app's domain name, which appears in several places in the consent page | API Settings page, Redirect Domain box |
| 3. Your app's name, which appears in several places in the consent page | Basic Information page, Application name box |
| 4. Your app's terms hyperlink | Basic Information page, Terms of service URL box |
| 5. Your app's privacy statement hyperlink | Basic Information page, Privacy URL box |
Note If the Terms of service URL and Privacy URL settings are not specified, the text | APPLICATION_NAME terms and privacy statement does not appear in the consent page.
The numbered items in the preceding table correspond to the items in the consent page, as shown here. (This page may look a bit different depending on your app type.)
.png)
The numbered items also correspond to the items in the Live Connect app management site as shown here.
.png)