Skip to content

GH-210 aio-lib-java-ims fixed scope parameter typo when calling /ims/token/v3#212

Merged
francoisledroff merged 1 commit intomainfrom
GH-210
Jan 29, 2024
Merged

GH-210 aio-lib-java-ims fixed scope parameter typo when calling /ims/token/v3#212
francoisledroff merged 1 commit intomainfrom
GH-210

Conversation

@francoisledroff
Copy link
Copy Markdown
Collaborator

@francoisledroff francoisledroff commented Jan 29, 2024

Description

All operations which needs a token are failing when using OAuth based workspace
due to a scope parameter typo when calling /ims/token/v3

Related Issue

#210

Motivation and Context

In the actual API call parameter-name is scope but sdk is using scopes

Sample Curl call

curl -X POST 'https://ims-na1-stg1.adobelogin.com/ims/token/v3' -H 'Content-Type: application/x-www-form-urlencoded' -d 'grant_type=client_credentials&client_id=xxxxx&client_secret=xxxxxx&scope=yyyy,zzzzz'

How Has This Been Tested?

see #211

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

  • I have signed the Adobe Open Source CLA.
  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.

@francoisledroff francoisledroff merged commit 06ec44c into main Jan 29, 2024
@francoisledroff francoisledroff changed the title aio-lib-java-ims fixed scope parameter typo when calling /ims/token/v3 GH-210 aio-lib-java-ims fixed scope parameter typo when calling /ims/token/v3 Jan 29, 2024
@shikhartanwar shikhartanwar deleted the GH-210 branch September 16, 2024 07:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants