Forum Discussion

vaishnavi's avatar
vaishnavi
Expert
10 years ago

facing issue in integrating third party API in endpoint

I am tryign to integrate a third-party API calls in my endpoint using oauth. steps :- 1.  API call to get new access token. I am getting below response >>  {"expires_in":1209600,"refresh_token":"A...
  • vaishnavi's avatar
    vaishnavi
    10 years ago

    PaoloT,

    Thanks for your suggestion.

    I have used the approach and its working now.

PaoloT's avatar
PaoloT
Lithium Alumni (Retired)
10 years ago

Hi vaishnavi

 

what is the error you are getting? 

 

Thanks,

 

  • OlivierS's avatar
    OlivierS
    Lithium Alumni (Retired)
    10 years ago

    vaishnavi have you try to display the value of the 'a_token' variable to see its content?

     

    <#assign a_token = json_response.access_token />

    Or try:

     

    <#assign a_token = json_response.access_token?json_string  />
    • vaishnavi's avatar
      vaishnavi
      Expert
      10 years ago

      When I print ${a_token} it print the correct string value but its not working in API header.

       

      I have tried j_string, js_string, json_string but nothing is working.

      I getting below error :

      error making http request: Unauthorized

       

      Is here any issue due to encoding of API response ?

       

      when I print ${a_token?url} for <#assign a_token = "ASfJllLBFpNPucOl7hMQptwyMQ==" /> 

      output is : ASfJllLBFpNPucOl7hMQptwyMQ%3D%3D

       

      and when I print ${a_token?url} for <#assign a_token = json_response.access_token />

      output is : ASfJllLBFpNPucOl7hMQptwyMQ%26%2361%3B%26%2361%3B

       

      means it takes HTML encoded access_token  as ASfJllLBFpNPucOl7hMQptwyMQ&#61;&#61;

      Note here : &#61; is HTML encoded equivalent of equal sign( = )

      and again encodes it to MQ%26%2361%3B%26%2361%3B

       

      Does anyone know how to decode HTML encoded string in freemarker variable?

       

      • PaoloT's avatar
        PaoloT
        Lithium Alumni (Retired)
        10 years ago

        Hi vaishnavi

         

        I have encountered the behavior once and it is being investigated ( JakeS may be interested in this topic). In the meantime, to overcome these encoding issues in the past, I have used a workaround

         

        <#assign token = jsonResp.access_token?replace("&amp;", "&")?replace("&#61;", "=")?replace("&lt;","<")?replace("&gt;",">")?replace("&amp;quot;","\"") />

         

        This is, of course, just a workaround using string replace but it did the trick for me.

         

        Thanks