Authentication URL different than Connection Base URI

Comments

3 comments

  • Tyler Lamparter Principal Product Manager
    Awesome Follow-up
    Engaged
    Top Contributor
    Answer Pro
    Celigo University Level 4: Legendary

    Marcelo Borges the field name and relative text underneath is a little misleading, but the relative url field under the refresh token section allows a full url. There is a note in that KB article you linked.

    1
  • Tyler Lamparter Principal Product Manager
    Awesome Follow-up
    Engaged
    Top Contributor
    Answer Pro
    Celigo University Level 4: Legendary

    Marcelo Borges should look something like this. You should put your key and password in the encrypted field and then reference the encrypted field with handlebar expressions in the post body.

     

    Encrypted field:

    {"api_key": "value","api_password": "value"}

     

    Post body:

    {
      "api_key": "{{connection.http.encrypted.api_key}}",
      "api_password": "{{connection.http.encrypted.api_password}}"
    }
    1
  • Marcelo Borges

    Tyler Lamparter thank you so much. This very detailed screenshots helped me through the process now. I was just confused between the Token and the Refresh Token parts of the setup. But understanding that I could include a whole different URL for authentication purposes, that made the difference and I really haven't paid attention to on the article. Tks tons!

    0

Please sign in to leave a comment.