Procedure

1. Create a broker account in the SecureCloud Central Management Console.
   See Creating a Broker Account.
   The broker account information includes the set of IP addresses that will make API requests. API requests made from this IP range bypass the Incoming IP Filter. In addition, the broker account name and digest passphrase are necessary to create a digest authentication process.
2. Create a digest authentication process.
   See Creating a Digest Authentication Process.
   The digest authentication process is required to bypass the Digest Authentication Filter. This section of code will be used in every other part of the API request.
3. Request a SecureCloud public certificate.
   See Creating a Public Certificate Request Function.
   The SecureCloud public certificate is openly available to all requests. Along with the digest passphrase and its corresponding broker account name, the public certificate is required to request a SecureCloud user access token.
4. Request a SecureCloud user access token.
   See Creating a User Access Token Request Function.
   A SecureCloud API request that successfully obtains a user access token is able to bypass the User Access Token Filter, the third and final authentication filter.
5. Call a SecureCloud API.
   See Creating a SecureCloud API Request.
   If the API request successfully bypasses all three authentication filters, SecureCloud resolves the API call. The process is complete.

   Tip After successfully calling a SecureCloud API, do not change your digest passphrase. As long as your broker account information and your source IP address remain the same, you can continuously reuse the same functions and your user access token.