When you choose to create a REST Datasource, a new REST Service tab is created that has authentication set to none. You need to adjust the Authentication parameter if you are provided credentials for authentication for security on a REST Service connection, for example OAuth2:

Descriptions and configurations for these parameters are as follows:

  • Basic Authentication—Credentials are used to access the REST service as a configured user associated with the REST Datasource, and then these credentials are used for all calls to the REST endpoint.
    Figure 1. REST Connectivity sample using Basic authentication


    The Username identifies a user value in the REST Datasource, and its Password. The sample Datasource has pwd1 for user1. The credentials are encrypted when they are exported for deployment. When you connect to a URL of a REST API that requires basic authentication, you then add the credentials to the connection definition, as illustrated:
    Figure 2. Datasource Configuration file of REST Connectivity sample using Basic authentication


  • Token Authentication—A static string Token value can be associated with a Corticon REST Datasource. The user obtains an appropriate token from the REST service, and then saves it in the datasource.xml file. It is then used for all calls to the REST endpoint. A Token can be passed inside an HTTP Header or as a parameter on a URL. The REST Service must declare which token authentication mechanism it will use.
    • HTTP Header Token—Set the property that specifies the name of the HTTP header used for authentication. Input as Field Name, typically defaulted to Authorization in the Datasource and its Token (in this example Bearer 12345678901234567890), as shown:
      Figure 3. REST Connectivity sample using Token authentication by header


      The credentials are encrypted when they are exported for deployment, as illustrated:
      Figure 4. Datasource Configuration file of REST Connectivity sample using HTTP Header Token authentication


    • URL Parameter Token—Set the property that specifies the URL parameter that will pass the security token. Requires a Field Name, typically defaulted to Authorization in the Datasource and its Token (in this example Bearer 12345678901234567890), as shown:
      Figure 5. REST Connectivity sample using URL ParameterToken authentication


      The credentials are encrypted when they are exported for deployment, as illustrated:
      Figure 6. Datasource Configuration file of REST Connectivity sample using URL Parameter Token authentication


  • OAuth2 Authentication—Uses authorization tokens to prove an identity without giving away your password. You must specify the Client ID, Token URI, Client Secret, and Refresh Token for the connection.
    Figure 7. REST Connectivity sample using OAuth2 authentication
    The credentials are encrypted when they are exported for deployment. When you connect to a URL of a REST API that requires OAuth2 authentication, you then add the credentials to the connection definition, as illustrated:
    Figure 8. Datasource Configuration file of REST Connectivity sample using OAuth2 authentication