Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: add Role requirements #50

Merged
merged 2 commits into from
Oct 5, 2020
Merged

fix: add Role requirements #50

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f95194b
fix: add Role requirements
shazron Oct 5, 2020
349ccb8
Rephrasing
meryllblanchet Oct 5, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,13 @@ $ npm install

The Adobe Target 1.0 APIs need to set an `Accepts` header for them to work properly. With version `2.x` or greater of this SDK, we set the proper `Accepts` header for the calls as [documented](https://developers.adobetarget.com/api/). Previous versions of this SDK may or may not work since for some Target API calls the `Accepts` header is not enforced consistently.

### User-based OAuth Tokens and Role Requirements

For scenarios in which user-based OAuth tokens are used instead of a JWT technical account ones, the user may require specific roles/permissions to be assigned in Adobe Target in order to successfully perform API calls.
Otherwise, the Adobe Target API calls performed by the API Client will result in 500 errors.

For more detailed information, please read the [Adobe Target Enterprise user permissions documentation](https://docs.adobe.com/content/help/en/target/using/administer/manage-users/enterprise/property-channel.html).

### Usage
1) Initialize the SDK

Expand Down