I am playing with the JWT module and with help from support got it to where I can exchange it for a bearer token.
According to documentation, to authenticate on the API I'd send it as "Authorization" header - but so far the API just errors out with an authentication failure.
Have you successfully called the Workfront API with a bearer token?
Solved! Go to Solution.
Views
Replies
Total Likes
Posting this here in case it helps anyone else:
Once you make the exchange via https://example.my.workfront.com/integrations/oauth2/api/v1/jwt/exchange , you use the access_token to make API calls but instead of putting "Authorization: Bearer XXX" add "SessionID" as the header and the access_token for value.
Attached is a sample scenario which shows everything in 3 steps. To get the Client ID, Customer ID, User ID and Client Secret, you will need to create an OAuth2 (Machine to Machine) application here: https://example.my.workfront.com/setup/oauth2-apps .
well heck: Per Authorization code flow for custom OAuth 2 applications | Adobe Workfront i just send a sessionID header with the value of the access_token!
Thanks to my brothers in arms @Christian Handel and @nino Skuflic : D
Posting this here in case it helps anyone else:
Once you make the exchange via https://example.my.workfront.com/integrations/oauth2/api/v1/jwt/exchange , you use the access_token to make API calls but instead of putting "Authorization: Bearer XXX" add "SessionID" as the header and the access_token for value.
Attached is a sample scenario which shows everything in 3 steps. To get the Client ID, Customer ID, User ID and Client Secret, you will need to create an OAuth2 (Machine to Machine) application here: https://example.my.workfront.com/setup/oauth2-apps .
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies