Thread Details
  • State Not Answered
  • Replies 5 replies
  • Subscribers 353 subscribers
  • Views 2134 views
  • Users 0 members are here
Forum Actions
Related

facing Invalid Refresh Token Issue

Paritosh Chandorkar

Hi,

We are accessing sugarcrm application from multiple environment using one demo instance with same client id and client secret.

The scenario is with one demo instance and same client credentials

1. On first environment , if we test connection ,will get access token a1 and refresh token r1

 On Second environment with same demo instance and same credentials if i tried to execute test connection parallely,i will receive new access token  a2 as well as new refresh token r2 

first environment received  access token a1and refresh token r1 will become invalid. 

Is this expected behaviour from sugarcrm application end. Can you please confirm?

Parents
  • 0 in reply to Paritosh Chandorkar

    Hi Jeff,                                                                                                                                                                                            1.Can you help me to understand "use of platform"? is the only reason to avoid above conflict (parallel access)? or adding platform in access token request body is having specific reason?                                                                                                 2.Do we have any API to register custom platform?                                                                                                                    3.I found one observation that if i use "mobile" as platform in access token request body, and hit target with two access token api call one after another, previously(1st from two hits) returned access and refresh token is still remaining valid. but this behaviour i am not seeing with my new custom configured platform or any other platforms.

    Is it the way platform is defined making the difference?

    Can you provide your input to above queries? and some document to refer it

    Thanks

Reply
  • 0 in reply to Paritosh Chandorkar

    Hi Jeff,                                                                                                                                                                                            1.Can you help me to understand "use of platform"? is the only reason to avoid above conflict (parallel access)? or adding platform in access token request body is having specific reason?                                                                                                 2.Do we have any API to register custom platform?                                                                                                                    3.I found one observation that if i use "mobile" as platform in access token request body, and hit target with two access token api call one after another, previously(1st from two hits) returned access and refresh token is still remaining valid. but this behaviour i am not seeing with my new custom configured platform or any other platforms.

    Is it the way platform is defined making the difference?

    Can you provide your input to above queries? and some document to refer it

    Thanks

Children
No Data