Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

OAuth scope changes for migration from REST API v1 to v2?

1.. None v2 APIs have classical OAuth scopes documented? All are granular scopes whereas v1 APIs have classical scopes as recommended scopes. Are classical scopes in plan? What is the plan generally? Any scopes deprecation plan?

2. In regard to, are classic scopes generally the parent scopes that can be used for more than one APIs? Are they the superset scopes and granular scopes the subset? 

3. To move from v1 to v2, can't Atlassian make auto changes for corresponding OAuth scope changes so that clients don't have to reauthenticate? Do you have some suggestions/recommendations on how clients can migrate without the need to re-authenticate or elegantly?

0 answers

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events