...

1. Right-click on a test suite and choose Add New > Global Property... 
2. Expand the Authentication list, then choose an authentication method and click Finish.
   
   The authentication method is added to the test suite's Authentications node. If this is the first shared authentication created for this test suite, the Authentications node is created automatically.
3. A configuration tab opens in the workspace. How you complete the configuration depends on which authentication method you selected:
   • Basic
     1. Enter an easily identifiable name in the Name field.
     2. Enter the Username and Password to be used for this authentication.
   • Digest
     1. Enter an easily identifiable name in the Name field.
     2. Enter the Username and Password to be used for this authentication.
   • Kerberos
     1. Enter an easily identifiable name in the Name field.
     2. Enter the Service Principal to be used to authenticate.
        • For more information about Kerberos authentication, see "Security Settings" on the Additional Preference Settings page.
   • NTLM
     1. Enter an easily identifiable name in the Name field.
     2. Enter the Username and Password to be used for this authentication.
   • OAuth 1.0
     1. Enter an easily identifiable name in the Name field.
     2. Enter the Customer Key and Customer Secret to be used for this authentication.
     3. Select the authentication mode from the Mode dropdown. The other fields you will need to complete depend on your selection:
        • Obtain Request Token (requests the Request Token from the server using the Consumer Key and Secret)
          1. Scope: Restricts what information may be accessed. This information in embedded into the Consumer Key.
        • Exchange Request Token for Access Token (exchanges the Request Token plus the verification code for the Access Token)
          1. Request Token: Specifies Temporary Request Token credentials obtained from the server (used to exchange for the Access Token).
          2. Request Token Secret: Specifies Temporary Request Token credentials obtained from the server (used to exchange for the Access Token).
          3. Verification Code: Specifies the verification code provided by the server; this confirms that the resource owner will grant permission.
        • Sign Request for OAuth Authentication (uses the specified Access Token and Access Token Secret to give the client access to the user's private resources)
          1. Access Token: Specifies the Access Token used to give the client access to the user's private resources.
          2. Access Token Secret: Specifies the Access Token Secret used to give the client access to the user's private resources.

     4. Add any additional OAuth parameters (for example, the timestamp and nonce) under Parameters.
        

        For more information about using OAuth 1.0 in functional tests, see OAuth Authentication.

Global Key Stores

Anchor
Global Key Stores_SOA Global Key Stores_SOA

...