Hi team,
I’m integrating Backlog with a third-party platform using OAuth2. I noticed the documentation doesn’t mention any scope parameter for authorization.
Could you confirm if Backlog’s OAuth2 supports or requires scopes (like read, write, etc.), or should it be left blank?
Thanks!
Hi @lokaesshwar
Thank you for posting on the Nulab Community!
Please note, we are consulting this further with our technical team. I will keep you informed of any updates as soon as I hear back from the team.
In the meantime, please let me know if you have any other questions, we’re always happy to assist.
Hi @lokaesshwar
I’m just following up on the OAuth2 scope parameters post, thank you for your patience!
Our technical tech has checked this further, and advised the below.
Parameter specification: Leave it blank or omit the scope parameter itself from the request.
Please note, the permissions of an access token issued via OAuth2 will be identical to the permissions of the Backlog user who performed the authentication (authorization).
Example: If a user with Administrator permissions authenticates, the token will behave with Administrator permissions.
If the specifications of the third-party platform require the scope parameter (omitting it causes an error), please test whether it works by including a dummy value (for e.g. default or null).
Please let us know if you have any further questions, we’re always happy to assist.