HTTP Connection Request to support Basic type and Token Auth type

Amol B

• August 08, 2023 14:29

We are working on Zuore Revenue (RevPro) Application. As there is no inbuilt connector for it, so we are using HTTP adapter to establish RevPro connection.

1) RevPro follows the Basic type and Token type Authentication.

2) To connect or do any API call with RevPro we need a token to be generated and that token gets expired every 30 mins. There is no refresh token concept in RevPro. 

3) To get the token we need to use Auth type basic. We need to select Auth type as Basic and give Username and Password. And the token will be generated in Response Headers.  

4) We have achieved the following things. 

- We have connected to RevPro using Basic Auth type i.e. Username and Password

https://yourHost/api/integration/v1

- Using the same connection we have generated the Token in a flow (Integration)

https://yourHost/api/integration/v1/authenticate

 

Limitations-

1) We want to achieve the above two steps in a single connection.

2) There is no refresh token in RevPro.

Please provide us with a workaround to generate Token every 30 mins

0

• 

  Tyler Lamparter Principal Product Manager

  • August 24, 2023 14:02

  

  

  

  

  

  Amol B I think you may be confused on how our "refresh token" offering works. In your case, you should be using it. When the endpoint provides us with a 401 error code for unauthorized, we then trigger the refresh token mechanism to fetch a new token. For the values of token and refresh token in this setup, use dummy values. Upon saving, the refresh mechanism will kick in. Here is an example setup:

  

  

  Basic {{{base64Encode connection.http.encrypted.username ":" connection.http.encrypted.password}}}

  

   

  From the docs, I wasn't 100% sure what field the token is returned in. You would just need to modify this to the actual field name that has the token.

  

   

   

  

  {
    "username": "value",
    "password": "value"
  }
  
  {
    "username": "copy this json structure to encrypted field. structure is here so that structure is known in the future after saving this connection",
    "password": "copy this json structure to encrypted field. structure is here so that structure is known in the future after saving this connection"
  }

  0

Please sign in to leave a comment.