ebay 中得到本身的RuName

The RuName will identify your application to eBay when you send users to the user consent flow page. If localization or marketing considerations make it desirable to have multiple display names for a single application, you can specify multiple RuNames for your application, then set a display name for each RuName.

 

Start from the "Customize the eBay User Consent Form," available in the MyAccount page page, "application settings" tab.

 

1. With an environment and a keyset selected, click "Customize the eBay User Consent Form."

 

1. Click "generate runame."

 

The generated RuName appears under Manage Your RuNames.

 

Now you can set other RuName-level settings.

 

1. Under Manage Your RuNames, click "Show Details."

 

 

1. Display Title: Enter the company or application name to display on the consent page (the name is stored per RuName, not per application).

 

1. Display Description: Enter text describing your application to be used on the user consent form.

Token Return Method: Specify how you want eBay to return the token to your application when a user completes the consent flow. Select "FetchToken," and your application will use the FetchToken to retrieve the token. "FetchToken" is the recommended method. Do not use "Redirect"—it is not recommended for security reasons.

 

1. Authorization Type: There are two types: Authorization and IDVerification. If your application needs to access eBay users' data via eBay Web Services, set Authorization Type to Authorization (the default).

 

Set Authorization Type to IDVerification if your application needs only to confirm users' eBay UserIDs, and does not need to access users' private data. Users will be presented with a more casual text on the consent page, and a token is not generated for the application. The application needs to use the ConfirmIdentity API call to complete the final UserID confirmation step. Because there is no token, there is no need to call FetchToken.

 

1. Application Type: Specify whether your application is web-based and has a URL to which you would like your users returned after they consent, or is a desktop application without a URL.

 

1. Accept Redirect URL: The URL to which users will be directed after they consent to the web application authenticating them. This URL must support SSL and must use the HTTPS protocol.

 

If your application is capable of serving web pages, you should provide your own web page and set this URL. If your application cannot serve web pages, this URL defaults to a standard eBay accept-response page (note that the eBay page and URL is subject to change by eBay).

 

1. Reject Redirect URL: The URL to which users are directed when they do not consent.

 

If your application is capable of serving web pages, you should provide your own web page and set this URL. If your application cannot serve web pages, this URL defaults to a standard eBay accept-response page (note that the eBay page and URL is subject to change by eBay).

 

1. PrivacyPolicyURL: The URL at which your privacy policy can be read.