Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Kumar1
Kumar1
Offline

Badges

Badges
4

Accepted Solutions

Accepted Solutions
0

Likes Received

Likes Received
0

Posts

Posts
6

Discussions

Discussions
0

Questions

Questions
6

Ideas

Ideas
0

Blog Posts

Blog Posts
0
Expand more
Expand menu
View leaderboards
Profile
Trophy case
Top badges earned by Kumar1
Customize the badges you want to showcase on your profile
Give Back 5
Give Back 3
Give Back
Ignite 1
Re: Getting same refresh token
Kumar1
- Adobe Developer Console 15-06-2022
Hi @tmj , I have raise this issue with Adobe support team and they are looking into this.Meanwhile I will try to implement the (JWT) credential.Thank you for you help

Views

167

Likes

0

Replies

0
Re: Getting same refresh token
Kumar1
- Adobe Developer Console 14-06-2022
@tmj Is there any way to handle this scenario ? Currently we have to manually regenerate the token from postman and feed it into our application after every 14 days.

Views

182

Likes

0

Replies

2
Re: Getting same refresh token
Kumar1
- Adobe Developer Console 14-06-2022
@tmj We are using Adobe Analytics API's and I don't think it support offline_scope.

Views

190

Likes

0

Replies

4
Re: Getting same refresh token
Kumar1
- Adobe Developer Console 09-06-2022
Hi @tmj , I verified the API and the offline access scope is not there.Could you please suggest how can I add offline scope to my API ?

Views

217

Likes

0

Replies

6
Re: Getting same refresh token
Kumar1
- Adobe Developer Console 06-06-2022
Hi Manik, I created the new project and used newly generated OAuth credentials to fetch fresh set of access_token and refresh_token but it is still repeatedly returning the same refresh_token .

Views

233

Likes

0

Replies

8
Getting same refresh token
Kumar1
- Adobe Developer Console 06-06-2022
We are trying to get new refresh_token and access_token using existing refresh_token. Every time it returns the same refresh_token but less validity left. After sometime refresh_token will be not valid anymore.Can someone suggest how to generate new refresh_token with more validity. Note :- We have scheduled job which runs every 12hrs to generate new refresh_token and access_token using existing refresh_token

Views

241

Likes

0

Replies

10
Likes given to
View All